Informatica Developer Job Description Template 2026

Last updated: September 22, 2026

By Robert Ardell, Co-Founder and Strategic Advisor, KORE1

An Informatica developer job description works when it names which Informatica product the person will actually open, how far along the move off PowerCenter is, whether data quality is part of the job, and the pay. Most name none of those. They say “Informatica” and stop there, which is a little like advertising for a Microsoft developer and hoping the right one shows up.

There is something about this title that makes it stranger than the others we write about, and it’s worth knowing before you post anything. “Informatica Developer” is not only a job title. Somebody at Informatica gave that exact name to a piece of software, which is where the trouble starts.

A regional health plan outside Harrisburg, Pennsylvania learned that the expensive way last year. Eleven hundred employees, a claims warehouse that had been running since the Bush administration, and a req that read “Informatica Developer, 5+ years of Informatica, strong SQL, data warehousing experience, healthcare a plus.” They filled it in six weeks. Everybody was pleased.

The woman they hired came from a mid-size bank in Wilmington. Six years of Informatica on her resume. All of it real.

What she had spent those years doing was profiling customer records, writing address validation rules, and tuning the match logic that decides whether two rows are the same human being. Serious work. She was good at it. She had done all of it inside a program called Informatica Developer, which is the Eclipse-based client that ships with Informatica Data Quality, and she had never in six years opened PowerCenter.

Week three, a nightly load for the claims warehouse failed and somebody asked her to read the session log. She had never seen a session log. She had never seen Workflow Manager, or Designer, or the Repository Manager, because none of those things are part of the product she had been hired away from. The hiring manager told me later, and I’m quoting him almost exactly: “It said Informatica on her resume. It says Informatica on my req.”

Nobody had misrepresented anything. Both true. Both useless.

One disclosure before we go further. KORE1 gets paid by employers, only after somebody we sent gets hired, and that includes every search our Informatica developer staffing desk runs, which sits inside the wider ETL developer staffing practice. A req written clearly enough that the right person applies on their own costs us a placement. Write yours that well anyway. The teams that do tend to call us for the search that really is hard, and those searches are more interesting than this one.

Five Products Wear the Same Word

Informatica sells a platform, not a tool. The pieces of it have almost nothing to do with each other day to day, and somebody fluent in one can be genuinely lost in another. It happens constantly. Your job description has to settle which one. First two lines.

Read the fourth row again. The product literally named Informatica Developer is the Data Quality client, which means the most literal reading of your job title points at the one thing you probably didn’t mean. That’s the whole Harrisburg story in one line.

None of this is a candidate problem. Resumes say “Informatica” because the vendor’s marketing says Informatica, and because six years in one corner of a platform feels, reasonably, like six years of the platform. It isn’t a lie. It’s a category error, and the fix is on the posting side. Ninety seconds, maybe.

The Support Date Already Went By

Standard support for PowerCenter 10.5.x ended on March 31, 2026, per Informatica’s own product lifecycle guide. Paid extended support runs a year past that. Sustaining support comes after it, which is a polite way of saying the phone still works and nobody is writing you new fixes.

It is now September. That date is behind us. Hiring a PowerCenter developer today means hiring into a countdown, whether your req admits it or not.

Which changes who wants it. This is the part hiring managers tend to underrate, so I’ll be blunt about it: a strong mid-career engineer reading “PowerCenter maintenance” in late 2026 hears “three years of keeping a dying thing alive, then back on the market with a skill nobody is posting for.” Some of them will take it anyway, for the money or the commute. The good ones want to know what happens after.

So say what happens after. Informatica’s PowerCenter modernization program is the documented path to Intelligent Data Management Cloud, and it markets heavy asset reuse, with a conversion utility that carries existing mappings across. If you’re running that program, or you plan to, or your CFO hasn’t signed off and the whole thing is a 2028 problem, each of those is a different job and each attracts a different person. Write down which one is true.

Two sentences is plenty:

We run PowerCenter 10.5 on-premises with about 400 mappings feeding a claims warehouse. Migration to IDMC is funded and starts in Q2, and this engineer will be on it.

Or, if that’s not your situation:

We run PowerCenter 10.5 and there is no funded migration. This role is steady-state support of the existing load, and we are being straight with you about that.

The second one filters harder. It also finds the person who genuinely wants it, and there is such a person, usually someone who has done two cutovers already and has had enough excitement for a while.

Candidates will ask about Salesforce, so have an answer ready. Salesforce completed its acquisition of Informatica on November 18, 2025, and the announcement said Informatica keeps supporting and integrating its data management products across its partner ecosystem. That is the official position. Read it as such. Nobody senior is going to accept it uncritically, and you don’t have to pretend otherwise.

The Data Quality Line at the Bottom of the Req

Roughly a third of the Informatica reqs that reach us end with some version of “and data quality experience a plus.” As a line in a posting it’s close to worthless, and it’s worth understanding what it costs you.

A data integration developer moves data from one place to another and is judged on whether it arrived, on time, unchanged. A data quality developer decides what the data means. Whether these two rows are the same patient. Whether a suite number belongs in line one or line two. What to do with the four hundred records that failed the rule, which go into an exception queue that a human being in the business, not in IT, has to work through.

Different skill. Different temperament, honestly. The integration people I place are builders and the quality people are closer to auditors, and the overlap between those two personalities is real but it isn’t the majority. A line at the bottom of a req asks candidates to self-assess against a job you haven’t described.

So either delete the line or promote it. Deleting it costs nothing. Promoting it means writing the actual split into the body of the posting, as a share of the week: quality is 70% of this job and integration is the other 30%, here is what the quality half involves, and here is who works the exception queue when a rule rejects four hundred records.

Candidates self-select accurately when you give them a percentage. Give them a bullet instead and they guess, which is how you end up three weeks into a search reading resumes from two different professions.

The Lines Worth Cutting

Most Informatica reqs are too long, and the length is doing damage rather than nothing. Every line that doesn’t filter still costs you a reader. Five, usually. Here is what we take out first.

“5+ years of Informatica.” Cut it, or split it. A count of Informatica years cannot tell six years of PowerCenter from six years of the Developer tool, which is the whole reason the Harrisburg search went sideways. Ask for production data pipeline experience by years, then name the product separately. Once the req reads correctly, the matching interview questions for this role are the next thing to get right.

The nine-tool list. PowerCenter, IICS, IDQ, MDM, SSIS, Talend, DataStage, Snowflake, Oracle, Python. Nobody has all of it. A list that long reads as a wish rather than a requirement, and the good candidates who match six of the nine quietly decide the posting isn’t about them. Name what actually runs in production. Put the rest under nice to have. Or nowhere.

“Informatica Certified Professional required.” Keep it as a preference if you like it, but not as a gate. Informatica pins those exams to a specific product release, so the credential records when somebody studied rather than what they can do now, and requiring it removes strong PowerCenter engineers who never bothered to sit one.

“Bachelor’s degree in Computer Science or a related field.” This field is full of people who came in through a data warehouse team at an insurer and learned the platform on the job. If a federal contract or an actual legal requirement forces the degree, say so plainly. Otherwise it is filtering on the wrong thing.

“Fast-paced environment,” “wears many hats,” “excellent communication skills.” These appear on almost every posting we see, which is exactly why they no longer signal anything. If communication genuinely matters here, say the real version: this person will have to defend a match rule to somebody in claims who is convinced the system is wrong. That sentence does work. The stock phrase does not.

Cutting all five usually takes a posting from about 800 words to 500. Shorter reqs get read to the end. That’s most of the benefit.

The Range You Have to Publish

A growing list of states now requires a pay range in the posting itself, so at some point you have to write a number down and stand behind it. The published sources will not pick it for you. Here they are.

Roughly $50,000 between the highest and lowest reading of one job title, which is why an aggregator average is a bad thing to paste into a req. Two things are behind the spread.

The first is that “Informatica developer” is a legacy title and it collects legacy work, so the trackers scoop up a lot of maintenance seats at large established employers. The second is subtler and it matters more for your req. The person doing this exact job on IDMC, today, very often has “data engineer” or “cloud data engineer” printed on their badge, and their salary gets counted in an entirely different bucket. The title is quietly sorting people by how old their stack is.

The federal numbers are worth thirty seconds because they cut against the doom narrative. BLS projects 4% growth for database administrators and architects from 2025 to 2035, with about 7,300 openings a year. Four percent is ordinary. This isn’t a collapsing field and it isn’t a booming one, so anyone quoting you a scarcity premium should be asked to show their work.

Our own desk sits above the aggregators, which is normal, because agencies work the searches companies couldn’t fill themselves. The bands our ETL practice quotes hold for Informatica work. Mid-level on a modern stack, $118,000 to $142,000. A senior who owns orchestration and carries the pager, $145,000 to $185,000. Migration leads with a real cutover behind them clear $195,000 in California, New York and Boston. Contract is $85 to $135 an hour at the senior end.

The Informatica-specific adjustment is one I’ll give you as an opinion rather than a number, because it’s a read and not a dataset. PowerCenter-only maintenance experience sits at the bottom of that mid band and tends to stay there. Someone who has actually stood up CDI, moved live workflows, and been on the call the night of a cutover prices at the top of senior or above, and they know it. You can check a band against your own metro with our salary benchmark assistant.

Informatica Developer Job Description Template

Fill the square brackets with your team’s real answers. The parenthetical notes are for you. Strip them before you publish. A blank you can’t fill is a message to whoever owns the platform, because a candidate is going to ask it on the first call anyway.

Job Title

[PowerCenter Developer / Cloud Data Integration Developer (IDMC) / ETL Developer, PowerCenter to IDMC Migration / Data Quality Developer (IDQ) / MDM Developer] (Pick one. The product word does the filtering. Keep “Informatica” in the body so keyword searches still land, and keep it out of the title on its own, where it means five things.)

About the Role

[Company] is a [what you do] serving [who]. This engineer owns [the claims warehouse load / the customer master / the API layer between (system) and (system)] on a data team of [N], reporting to [role]. The people they work with most are [the analytics team / the business stewards who work the exception queue / the DBAs].

The Informatica You Have

• [PowerCenter 10.5.x on-premises / IDMC Cloud Data Integration / both, during a migration], and [the version, the pod, or the year you landed on it]
• Roughly [N] mappings and [N] workflows in production, feeding [target systems]
• [Migration status: funded and starting (date) / in flight, (N)% converted / not funded, steady state, and we will say so]
• [Also in scope: Cloud Data Quality or IDQ for (profiling / matching / address standardization) / Cloud Application Integration for (real-time interfaces) / MDM for (customer or product master)]
• Sources and targets are [Oracle / SQL Server / DB2 / Snowflake / Redshift / Databricks / flat files off SFTP], orchestrated by [native scheduling / Control-M / Autosys / Airflow]
• [Regulatory context that changes the work: HIPAA, SOX, GxP validation, PCI]
• Deployments go out [weekly / monthly / whenever the change board meets], through [process]

What You’ll Own

• [Named subject area] end to end, from source analysis through production support
• [Migration seats: converting (area) to IDMC, including the mappings the utility hands back unconverted, roughly (X) days a week alongside the run-the-business work]
• [Steady-state seats: the nightly load, the failures it throws, and the tuning nobody has had time for since (year)]
• [Quality seats: profiling, rule design, and the exception queue that (business team) works in the Analyst tool]
• Code review for a team of [N], plus whatever documentation exists for [the area], which is [honest assessment]
• [On-call: one week in (N), and about (N) pages a rotation / none, we have a run team]

What You Bring

• [Three / five / seven] years building and supporting production data pipelines, at least [two] of them in [the product you named above]
• SQL you write rather than generate. Window functions, execution plans, and an opinion about when to push logic into the database instead of the mapping.
• [Migration seats: a PowerCenter to IDMC conversion you worked on, and what surprised you]
• [Quality seats: match rule design where you had to defend a false-positive rate to someone in the business]
• One pipeline you inherited and had to keep running before you understood it. What you did first. (Leave this in. The answers sort candidates faster than a years count ever has.)

Nice to Have

• [Industry] experience, where the domain takes months rather than weeks to pick up, like claims adjudication or GxP-validated manufacturing data
• Informatica Certified Professional on [Cloud Data Integration / Cloud Data Quality] (Genuinely nice to have. Don’t require it, and read the release it was earned against.)
• [Python or shell for the glue around the platform, if your team writes any]
• [Exposure to (Snowflake / Databricks / dbt), if that’s where the warehouse is heading]

Base Pay, Benefits, and Location

Base salary of [$low] to [$high], plus [bonus of about N% / equity / nothing further], with [health, retirement and time off in one sentence]. You would work [remotely from anywhere in the U.S. / from the (city) office (N) days a week / on site in (city)]. [If there is an on-call rotation, say how often it comes around and how noisy it is.] (Take the range from the table above. A growing list of states now requires one in the posting, and candidates skip the ones without it.)

Before You Post It

Is “Informatica Developer” even the right title?

Usually not on its own, because Informatica ships five product families and the title that names the specific one, like PowerCenter Developer or Cloud Data Integration Developer, reaches the right people without reaching four other groups.

Keep the word Informatica in the body of the posting so the keyword searches still find you. Just don’t let it carry the title alone.

We’re still on PowerCenter. Does saying so scare people off?

It thins the pile and improves it, since the candidates who leave were going to ask in the screen anyway and walk then, having cost you two calls instead of none.

What actually damages a search is the posting that stays vague, pulls a hundred applicants, and loses the good ones at the offer stage when the situation finally comes out. Hiding an old stack doesn’t make it newer. It just moves the discovery to the most expensive possible moment.

Can one person cover PowerCenter and IDMC?

Yes, and during a migration you want exactly that person, because someone who only knows the destination can’t read the twelve-year-old mapping they’re supposed to be replacing.

They are the scarcest profile in this market. They know it, too. Expect the top of your senior band, be ready to move in days rather than weeks, and understand that the same profile is being chased by every consultancy running a migration practice right now.

Do we need somebody certified?

Put it under nice to have rather than requirements, because a required Informatica certification screens out strong PowerCenter engineers before a human ever reads them.

Two words. Very different outcomes. Applicant tracking systems act on the requirements block, candidates read it as a wall, and plenty of the best people in this stack learned the platform on somebody’s warehouse team and never sat an exam. Under nice to have it still tells you something when it shows up. As a gate it mostly tells you who had a training budget.

$120K, is that the number?

$121,351 is where ZipRecruiter’s posting-derived average landed in September 2026, which makes it a fair midpoint for steady-state work and thin for anything with a migration attached.

For a cutover seat you’re competing with consultancies billing that work out, not with other health plans. Price against who you’re actually bidding against. Our own senior band runs $145,000 to $185,000 and migration leads clear $195,000 in the expensive metros.

Should the posting say anything about Salesforce owning Informatica now?

Leave it out of the posting and have an answer ready for the first call, because every candidate above mid-level has already thought about it and will ask you directly.

The honest version works fine. You’re on the platform. The roadmap isn’t yours to control, and here’s what you’re doing in the meantime. Candidates don’t need certainty from you. They need to hear that you’ve thought about it, which is a much lower bar and one that a surprising number of hiring managers fail.

Write Down Which Informatica You Have

Before the req, before the title, before anyone argues about years of experience, write one paragraph: which product, what version, how many mappings, who consumes the output, and whether a migration is funded. Five facts. Most teams can produce four of them in ten minutes and the fifth turns out to be a question for someone above them, which is itself useful to learn now rather than in week three.

That paragraph is also the entire brief we’d ask you for. When an Informatica req comes to our desk it is the first thing we want, ahead of the job description, because the job description is usually a description of a title and the paragraph is a description of a job.

Some of this work has an end date. A conversion is a project, and projects are what contract staffing is for. The person who owns the platform after the cutover is a different hire, usually a direct hire, and running both searches at once is normal rather than indecisive. If the seat leans toward modeling and standards rather than pipelines, that is a data architect search, and if it leans toward the warehouse itself our data engineering recruiters run it off their own bench. The adjacent ETL developer hiring guide covers the wider market if your stack isn’t only Informatica. For the rest of this one: what the role pays by level is in the Informatica developer salary guide, how we run the search is in the 2026 hiring guide.

Two numbers from our side, since I have asked for five of yours. Searches on our data desk average 17 days from req to hire, and when we check back twelve months after a placement, 92% of the people we placed are still in the seat. If you have an Informatica req in draft, send it to our team with that paragraph attached. Harrisburg would have cost about ninety seconds to avoid.