There are three numbers on Itentio’s homepage that carry the weight of our entire commercial proposition: a 99% candidate retention rate, an average time to fill of 3–4 weeks, and a candidate database of 30,000+ IT professionals. We have already published the full methodology behind the first two. This article does the same for the third, and updates it. The honest figure today is not 30,000. It is over 37,000 potential candidates. The homepage will catch up. But more importantly, this article explains where that number comes from, what it actually means in practice, what it does not mean, and why the breadth and depth of that database is the engine behind every other claim we make.
Why a Candidate Database Claim Deserves Scrutiny
Every recruitment agency in the market has a candidate database. Most of them will tell you it is large. Very few of them will tell you what is actually in it, how it was built, how it is maintained, or what proportion of it is genuinely relevant to the roles they are trying to fill.
A candidate database of 100,000 profiles built from mass LinkedIn scraping is not the same thing as a candidate database of 37,000 professionals built through eight years of direct engagement, active sourcing, and genuine relationship maintenance. The number is meaningless without the methodology. So here is ours.
What We Mean by “Candidate Database” and What We Do Not
A candidate database, as we define it, is a structured record of IT professionals with whom Itentio has had a direct point of contact – reached out to (sourced), screened, interviewed, placed, or actively engaged as part of a live recruitment process or community relationship.
It is not a list of LinkedIn profiles scraped in bulk. It is not a CV repository purchased from a third-party vendor. It is not a pool of people who submitted their details speculatively through a web form and were never heard from again.
Every professional in our database has been reached through one of three routes: active sourcing by our recruiters for a specific client brief, inbound application to a live role we were managing, or ongoing community engagement through the IT professional network we have cultivated in Poland and the broader Central and Eastern European market.
Most profiles in the database include a recruitment conversation record, notes from an initial screening, assessed skills and tech stack, salary expectations at time of contact, availability status, preferred engagement model (employment contract vs. B2B), and in many cases the outcome of previous application processes we managed for them with other clients. This is the difference between a candidate database and a contacts list.
How 37,000+ Profiles Are Built Over Eight Years
The database did not happen. It was constructed – systematically, role by role, client by client, year by year – as a direct output of doing real recruitment work across a genuinely wide range of requirements. Here is what produces a database of that depth.
Eight years of continuous sourcing across live roles. Itentio has been operating since early May 2018. Every recruitment engagement – and we have served over 70 client companies – generates sourcing activity. For each role, our team identifies, contacts, and screens a pool of candidates significantly larger than the shortlist eventually presented to the client. Every professional who is sourced and engages with us enters the database, whether or not they are placed on that particular search. Eight years of this, compounded across hundreds of roles (some of which was repeated), produces a database of genuine scale.
Over 70 client companies across more than 20 industries. This is the dimension that most distinguishes our candidate database from those of agencies with narrower mandates. A recruitment agency that only fills software engineering roles for SaaS companies accumulates a database that reflects exactly that – developers in SaaS environments. Our client base has required us to build candidate relationships across a substantially broader spectrum. We have recruited for FinTech, MedTech, AdTech, Gaming, E-commerce, Data, Infrastructure, Cloud platforms, Digital Marketing, Logistics, IoT, Blockchain, Media, Entertainment, and more. Each industry vertical brings different professional communities, different technology stacks, and different candidate pools, all of which now sit inside our database.
A role scope far wider than most agencies cover. This is perhaps the most underappreciated aspect of what makes our candidate database genuinely useful. When clients search for recruitment agencies in Poland, they often assume the available pool covers engineers – and specifically backend and frontend developers. Our database does cover those profiles, deeply. But it also reflects eight years of filling roles that most engineering-only focused agencies do not regularly work on.
The professionals in our database include:
- Software engineers across the full stack – backend, frontend, full-stack – in Java, Kotlin, Python, .NET, C++, Go, Node.js, TypeScript, PHP, Ruby, and many more. Engineers working on web, desktop, mobile, cloud-native, and on-premises systems.
- Quality Assurance professionals, both manual and automation QA engineers, across a wide range of testing frameworks, environments, and industry contexts including regulated sectors such as MedTech and FinTech.
- DevOps, DevSecOps, and Cloud Engineers – professionals who design, build, and maintain CI/CD pipelines, cloud infrastructure on AWS, Azure, and GCP, and increasingly security-integrated engineering workflows.
- Security Engineers and Systems Administrators – a candidate segment that sits at the intersection of infrastructure, compliance, and engineering, and one that most standard recruitment agencies do not source consistently.
- Software Architects and Solutions Architects – senior professionals responsible for system design decisions, technology strategy, and cross-team technical standards, both at startup scale and in enterprise SaaS environments.
- Data Engineers, AI Engineers, and Data Scientists – a fast-growing segment of our database that reflects the market’s dramatic shift toward AI-integrated product development over the past three years.
- Systems Engineers and Systems Analysts – professionals operating at the boundary of software and infrastructure, often in complex enterprise or embedded technology environments.
- Product Managers, Project Managers, and Product Owners – digital product leadership roles that sit at the intersection of business, technology, and user experience, and that require a different sourcing approach than engineering roles.
- UX/UI Designers and Product Designers – creative technologists who design digital products, user flows, interfaces, and experience systems across mobile, web, and emerging platforms including gaming and immersive environments.
- Animators, 2D and 3D Artists – creative professionals for gaming studios, AdTech platforms, simulation environments, and digital content companies.
- Business Analysts, Data Analysts, and Systems Analysts – professionals who translate business requirements into technical specifications, analyse data to drive product decisions, or assess and document systems at an architectural level.
- Operations Managers, Sales/Business development professionals, Marketing specialists, Customer Support and Technical Support professionals across multiple lines – roles that many IT-focused agencies decline to work on, but that technology companies consistently need to fill alongside their engineering teams. We decide to help with different roles verticals if we can.
- C-level executives – CTOs, COOs, CEOs, Directors of Engineering, VPs of Product – placed through our executive search practice, each of which requires a distinct sourcing methodology and candidate relationship approach.
This breadth is not incidental. It is the direct result of eight years of saying yes to the full range of roles that technology companies need filled, not just the ones that are easiest to source.
What the Candidate Database Actually Enables: Speed With Precision
A candidate database only has commercial value if it produces faster, better outcomes for clients. The question is not how many profiles are in the database, it is what proportion of them are findable, relevant, and reachable when a specific brief arrives.
This is where the way our database is structured matters as much as its size.
Our database is segmented by technology stack, seniority, industry experience, preferred engagement model, location, language skills, and last point of contact. When a brief arrives, we are not performing a keyword search across a static archive. We are running a structured query against a live intelligence asset, identifying profiles that match the specific requirement, cross-referencing with notes from previous interactions, and prioritising candidates whose availability and motivation make them genuinely likely to engage.
This is what allows us to move from brief confirmation to first candidate presentation within 24 hours on some roles – a timeline documented across multiple published case studies. It is not speed for its own sake. It is speed produced by preparation: years of relationship-building compressed into the moment when a client needs a result.
For a client evaluating whether our 3–4 week average time to fill is credible, the candidate database is the explanation. A recruiter without a pre-built database starts every search from zero. A recruiter with 37,000 relationship-backed profiles starts every search weeks ahead.
What the Candidate Database Does Not Claim to Be
Intellectual honesty requires the same transparency here as it did in the retention rate and time to fill articles.
Our candidate database of 37,000+ professionals does not mean that every profile in the database is currently available for a new job appeared. Professionals change jobs, change countries, change career direction, or become unreachable over time. Timing is extremely important in tech recruitment.
We maintain the database actively, updating candidate statuses and details when we speak with them during live engagements, and continuously adding new professionals through ongoing sourcing activity. But we will not claim that every record is equally current or that 37,000 professionals are simultaneously available and immediately placeable. That would be a different claim, and it would not be honest.
What we claim is this: a candidate database built over eight years, through genuine recruitment work across a wide range of roles and industries, contains a substantially higher proportion of relevant, reachable, relationship-backed profiles than a database built through bulk scraping or passive inbound collection. And that difference is what produces the outcomes our clients experience, as candidates can be presented within 24 hours, roles filled in days or weeks rather than months, placements that hold.
Why Database Depth Matters More Than Database Size
Any agency can publish a large number. What a client actually needs to know is whether the database contains the specific professional they are looking for, and whether that professional can be reached and motivated to engage when contacted.
Depth means having genuine representation across role types, seniority levels, technology stacks, industry backgrounds, and engagement preferences. A database of 37,000 that skews heavily toward mid-level JavaScript developers in Warsaw tells a very different story than a database of 37,000 that includes security engineers with MedTech compliance experience, Kotlin specialists who have worked in hyper-growth startups, senior Golang engineers in data infrastructure, Polish and English-speaking CTOs with FinTech backgrounds, and UX designers with gamification portfolios.
Our database reflects the latter. Not because we planned it that way in 2018, but because our clients’ requirements over eight years demanded it.
Every unusual brief we have accepted – the German-speaking engineer in Poland for a legacy e-commerce system, the Engineering Lead for an AI MedTech startup that needed to be placed within a week, the CTO with both FinTech depth and startup mentality for a FinTech company that could not afford to wait months – added profiles to our database that a narrower agency would never have sourced. The breadth of our client history is the breadth of our candidate database.
The Database in the Context of Polish IT Talent
Poland’s tech market has grown substantially over the past decade and is now recognised as one of Europe’s primary software development hubs, with over 650,000 IT professionals across the country. Major tech centres in Warsaw, Kraków, Wrocław, and Gdańsk/Tricity anchor a market characterised by strong technical education, high English proficiency, and a professional culture well-aligned with international company working norms.
Our database of 37,000+ professionals represents a meaningful, relationship-backed slice of that market – concentrated in the roles and seniority levels that international companies most frequently need to hire, and built through the kind of direct, human sourcing that produces candidates who are genuinely engaged rather than merely identified.
For international companies, particularly those headquartered in the US, Canada, UK, or Western Europe, considering building or expanding engineering teams in Poland, the database is the answer to the most common first question: are there enough qualified people available? The answer is yes, and our database is the evidence.
Our tech recruitment services in Poland are built on this foundation. The database is not a supporting feature of those services, it is their operating basis.
How the Database Connects to Our Other Headline Claims
Our three homepage metrics are not independent. They describe the same operating model from three different angles.
The 99% candidate retention rate – documented in full in our methodology article, is partly a function of database depth. When we match a candidate to a role, we are matching against a relationship record that includes motivations, working style preferences, cultural considerations, and historical fit signals. That information exists because we have been building and maintaining the database for eight years, not because we got lucky on individual placements.
The 3–4 week average time to fill – documented in our time to fill methodology article, is also partially produced by the database. A recruiter starting a search from zero spends the first one to two weeks of any engagement simply identifying a candidate pool. We start that search from a pre-built, tagged, relationship-backed asset. The time difference is not marginal.
The database is the infrastructure that makes the other two claims possible. It is what allows us to source the right candidate, present them with genuine depth of assessment, and place them with a confidence that results in both placement quality and placement longevity.
The Number Will Keep Growing
At the current rate of client engagements, sourcing activity, and community growth, our candidate database grows continuously. The 37,000+ figure documented in this article reflects the position as of 2026. By the time a new client reads this, the number will be larger.
What will not change is the methodology behind it: every profile added through direct recruitment work, every relationship maintained through genuine engagement, every database entry representing a professional who has chosen to engage with Itentio rather than simply appearing in a search result. That methodology is what the 30,000 figure, and the honest update to 37,000+, actually means.
Explore What Our Candidate Database Can Do for Your Hiring
If you are evaluating Itentio for a specific role or a broader team-building engagement, the database is the starting point of every conversation. The most useful thing you can do before reaching out is to understand what kind of need you have – the role, the seniority, the technology stack, the industry context, and your timeline.
We will tell you honestly whether your requirement sits comfortably inside our database, where the candidate supply is most concentrated, what realistic timelines look like, and what salary benchmarks apply in the current Polish market.
