Informatica Developer Staffing for PowerCenter, IDMC and Data Quality
We staff the Informatica product you actually run, not the one the job title implies.
- Product surfaces staffed
- 7
- PowerCenter 10.5.x
- Past standard support
- Average time to submit
- 17 days
KORE1 staffs Informatica developers across PowerCenter, IDMC, Cloud Data Integration, Data Quality and MDM, on contract, contract-to-hire and direct hire, with a 17-day average time to submit and 92% twelve-month retention on our placements.
Last updated: September 22, 2026
Most Informatica reqs we get say the same six words. Informatica developer, five years. Then the screen starts and it turns out the install is PowerCenter 10.5 with a half-finished cloud pilot, the real pain is a data quality backlog nobody owns, and the person who left was the only one who understood the reference tables. Three different jobs.
That isn’t a search problem. It’s a scoping problem, and it costs about three weeks if nobody catches it.
Informatica stopped being one tool a long time ago. The Intelligent Data Management Cloud spans integration, application integration, data quality, catalog and governance, master data management and a marketplace, and Salesforce closed its acquisition of Informatica on November 18, 2025, which has every enterprise data leader we talk to rethinking a roadmap they had already signed off.
Same vendor. Very different job. A developer who is excellent in one corner of that platform can be genuinely useless in another.
Where this page sits. Some of this belongs elsewhere. Generic pipeline work, ETL versus ELT, dbt and Airflow all belong to ETL developer staffing, and modelling belongs to data architect staffing. This page is about the Informatica product surface itself, and it sits under our IT staffing services practice.
Three more Informatica pages sit alongside it. Our Informatica recruiters page covers how the desk screens a candidate release by release, the 2026 guide to hiring an Informatica developer walks the process end to end, and work in North Texas runs through our Dallas desk.
Informatica Is Not One Tool. The Req Has to Say Which.
Seven surfaces, each with its own objects, its own vocabulary and its own talent pool. The path above each row is the kind an engineer would actually read in a repository folder or an IDMC project, which is the fastest way to tell whether the person in front of you has really worked in that corner. Pool depth is our recruiters’ read of the current market, not a published statistic.
PowerCenter
The on-premises workhorse. Designer, Workflow Manager, Repository Service, sessions that run at 2am and a scheduler somebody wrote in 2014.
- Called on a resume
- Informatica developer, ETL developer, PowerCenter developer
- The req usually forgets
- Oracle PL/SQL depth and the shell scripting that wraps the workflows
Cloud Data Integration
The cloud successor. Same mental model, different objects, and a Secure Agent sitting between the cloud org and whatever is still behind the firewall.
- Called on a resume
- IICS developer, IDMC developer, CDI developer
- The req usually forgets
- Who administers the Secure Agent and the runtime environments
Cloud Data Integration for PowerCenter
The bridge. It imports PowerCenter workflows into the cloud org so they run without a rebuild, and it needs somebody fluent in both dialects at once.
- Called on a resume
- Migration lead, modernization engineer, PowerCenter to IDMC lead
- The req usually forgets
- Regression testing, and who signs off that a converted job matches the old one
Cloud Application Integration
Real-time and API work rather than batch. Processes, guides, service connectors, and a very different debugging temperament.
- Called on a resume
- CAI developer, integration developer, API integration engineer
- The req usually forgets
- That batch ETL people are often miserable doing event-driven work
Data Quality, formerly IDQ
Profiling, rule specifications, address doctor, scorecards. Half the job is data work and half of it is sitting with a business owner deciding what valid even means.
- Called on a resume
- IDQ developer, data quality developer, data quality analyst
- The req usually forgets
- Stakeholder handling, which is the part that actually makes the rules stick
Master Data Management
Customer and product 360, match and merge, survivorship, stewardship consoles. Closer to a business function than to a pipeline, and priced accordingly.
- Called on a resume
- MDM developer, MDM architect, data steward lead
- The req usually forgets
- Whether it’s MDM SaaS or the older on-premises Hub, which are not the same hire
Data Governance and Catalog
Scanning, classification, lineage and glossary. The seat that gets funded right after an audit and defunded about eighteen months later.
- Called on a resume
- CDGC engineer, metadata engineer, data governance analyst
- The req usually forgets
- That cataloguing is worthless without somebody empowered to act on what it finds
Read down the paths. The hiring problem gets obvious fast. The three deepest pools sit at the top, on the oldest product, and the seats most companies are actually trying to fill in 2026 sit at the bottom where the pool is thinnest.
That inversion is the whole Informatica staffing market in one column. Deepest supply, thinnest demand.
One note on credentials. Informatica runs a Foundation level across IDMC, MDM SaaS and Cloud Data Governance and Catalog, plus Professional certifications for working developers, and each one is tied to a single product rather than to the platform as a whole. We read them as a tiebreaker between two close candidates. Never as a screen.
What We Pin Down Before the Search Opens
Four questions, asked in writing, before anybody is sourced. They take about twenty minutes on a call. They’ve also saved more searches than any sourcing trick we know.
- Which products, in order
- Not a list of everything you run. Rank them. The one the person spends Monday morning in, then the second one, then the thing they’ll touch twice a year.
- Version and hosting
- PowerCenter 10.2 on a server under someone’s desk is a different job from 10.5 with a cloud org beside it. Ask which. Write it down.
- The database underneath
- Informatica sits on top of something. Oracle, SQL Server, Teradata, Snowflake, Db2. A developer who has only ever pushed into one of those will be slow against another, and the req almost never mentions it.
- Build or keep running
- New development, a migration, or steady-state support. Three different people. They rarely enjoy each other’s jobs. Ask early.
That third one gets skipped. Constantly. It’s usually the reason a technically strong candidate takes four months to get productive, and by then everyone has quietly decided the hire was a mistake when the truth is that nobody told them they’d be writing Teradata SQL all day. Same discipline we apply on every data engineer search. If you are writing the req from scratch, start from our Informatica developer job description template.
Contract, Contract-to-Hire, or a Permanent Owner
The right shape usually falls out of one question. How long does this live?
- Contract
- A migration wave, a quality remediation, a parallel run. Work with an end date. That’s the tell. Contract staffing is also how most teams get a CDI-PC specialist at all, because the deep ones rarely go permanent.
- Staff augmentation
- You have a roadmap and not enough hands. Staff augmentation puts two or three Informatica developers alongside your team on your sprints, reporting to your lead.
- Contract-to-hire
- You’re fairly sure it’s permanent but the setup is messy enough that both sides want a look first. Contract-to-hire covers it.
- Direct hire
- Somebody has to own the platform on the day the consultants leave. That’s a direct hire. It’s the one worth being slow about.
One pattern worth naming. Teams staff a migration entirely with contractors, the migration lands, everyone goes home, and eight months later nobody inside the company can debug a converted mapping. Hire the owner during the project. Not after it.
Roles We Fill Across the Informatica Stack
Grouped by what the person is accountable for, which is how the work is really divided, rather than by whatever the job board taxonomy calls it.
The people who ship mappings
Day to day development against PowerCenter or CDI, plus the SQL underneath. Always the SQL.
- Informatica PowerCenter Developer
- IICS / IDMC Developer
- Informatica Data Quality Developer
- SQL Developer
The people who replatform
Migration and modernization work, where the hard part is proving the new job matches the old one.
- PowerCenter to IDMC Migration Lead
- Cloud Modernization Engineer
- ERP Data Migration Specialist
- Integration Engineer
The people who answer for the data
Quality, master data and catalog seats. Usually funded by an audit finding.
- Informatica MDM Developer
- MDM Solution Architect
- CDGC / Metadata Engineer
- Data Governance Analyst
The people who keep it up
Administration, platform ownership and the on-call rotation nobody volunteers for.
- Informatica Administrator
- Data Platform Engineer
- Database Administrator
- Data Architect
Pay follows that list, roughly. BLS puts the May 2025 mean for database architects at $144,440 across 67,140 people, and O*NET reports a $139,500 median for the same occupation, with growth above 7% and around 4,000 openings a year. O*NET also flags Informatica software as a Hot Technology for the role, which is a polite way of saying employers keep naming it in postings.
Informatica splits around those numbers rather than sitting on them. Legacy-only PowerCenter maintenance prices at the bottom. People who can hold the on-premises side and a cloud org at the same time price at the top, and that gap has widened since the support date passed.
We quote current bands by product lane on the call, because they move, and our Informatica developer salary guide breaks the same split down lane by lane. Pricing a 2026 offer off 2023 comp is the surest way to lose someone in the final round.
How a KORE1 Informatica Search Runs
-
1
Scope the products, not the title
We ask which products, which versions, which database, and whether the work is build, move or run. Twenty minutes, in writing. It happens before a single profile goes out.
-
2
Search on objects, not buzzwords
A resume that says Informatica tells us nothing. Everyone writes that. We look for the object vocabulary, so mapplets and worklets and reusable transformations on the PowerCenter side, taskflows and Secure Agents and runtime environments on the cloud side.
-
3
Screen on what they personally built
Not what the team delivered. Which mappings they wrote, which ones broke, and how they found out. People who have genuinely owned a nightly load will tell you about a failure without being asked twice. The questions we use to get there are written up separately.
-
4
Submit a short slate with the gaps stated
Three or four people, each with the mismatch written out. Strong CDI, light on quality. We would rather tell you that up front than have you find it in a second interview.
-
5
Agree the number before the offer goes out
Informatica people with cloud experience are usually talking to somebody else. We settle base, start date and any counteroffer conversation with the candidate before an offer is drafted, because a counteroffer landing mid-process is how these searches die. Every time.
Common Questions About Informatica Developer Staffing
What should an Informatica developer job description actually specify?
Name the product, the version and the database underneath it. All three. Informatica spans PowerCenter, Cloud Data Integration, Cloud Application Integration, Data Quality, MDM and the catalog, and those are different hires. A req that says Informatica developer with five years gets you a pile of resumes that all look identical and none of which you can rank.
Is PowerCenter experience still worth anything, or should we only hire cloud people?
More than it was two years ago, oddly enough. Informatica moved PowerCenter 10.4 from general support to premium-priced extended support on March 31, 2024, and its published product lifecycle put 10.5.x past standard support on March 31, 2026, which means a large installed base is now running production on a version it pays extra to keep supported. Somebody has to keep that running while the cloud work happens. Cloud-only hires can’t read a twelve-year-old mapping.
How long does it take to fill an Informatica role?
17 days is our average from first conversation to a submitted shortlist, measured across our IT and data searches. Informatica splits hard around it though. A PowerCenter developer in a deep market beats it easily, while an MDM or CDI-PC specialist can take three to five weeks, and a role that needs both PowerCenter and cloud fluency in one person is the slowest search on this page.
Do we need an Informatica certification as a screening requirement?
No. Use it as a tiebreaker. A certification tells you somebody sat an exam on one Informatica product, which is genuinely useful for separating two close candidates and useless as a filter, and we have placed excellent IDQ developers who never sat one while plenty of certified candidates have never owned a production rule specification end to end. Ask what they shipped instead.
Should Informatica work be contract or permanent?
Ask how long the work lives, then match the shape to the answer. Migrations, quality remediations and parallel runs have end dates and suit contract staffing or staff augmentation. Platform ownership doesn’t. That one’s a direct hire. The common mistake is staffing a whole migration on contract and leaving nobody behind who can debug it.
What does the Salesforce acquisition mean for Informatica hiring?
Salesforce completed the acquisition on November 18, 2025, and the practical effect on hiring so far is hesitation rather than movement. Teams are asking us whether to keep investing in Informatica skills. Our read is simple. The installed base is enormous, those systems are not going anywhere quickly, and the people who can run both the legacy and the cloud side have gotten harder to find, not easier.
Can you staff Informatica alongside a broader data team build?
Yes, and that is most of what we do here. Informatica seats rarely come alone. It usually comes attached to a warehouse project, so the same search often picks up a data engineer, a data architect or a reporting analyst, and we run those as one engagement with one point of contact rather than four separate reqs with four recruiters.
Tell Us What’s Running
No req written yet? Fine. Send the product, the version and the database underneath, and a KORE1 recruiter will tell you how deep that pool is and what the search realistically takes.
Let’s Connect →