
Informatica software engineer candidates report an online or coding screen, technical rounds on Java, data structures and resume projects, then manager and HR conversations. Here is how to prepare for each stage.
$147K
Avg. Base Comp
$165K
Avg. Total Comp
3-7 rounds
Typical Rounds
Not reported
Process Length
Candidates describe the Informatica software engineer interview as a fundamentals-first process. Several reports begin with an online assessment or coding test. One describes a mix of DBMS, Java, programming and logical reasoning questions, and another a multiple-choice paper with Java output, DSA, aptitude and database sections.
The technical rounds that follow lean on classic problems. Reported examples include an LRU cache, sorting an array of 0s, 1s and 2s, rotating a matrix, implementing a stack with a linked list, printing a matrix in spiral form, and writing mergesort and bubble sort with their complexity. One candidate in a full stack interview was asked about linked list loops and a master/slave threading exercise. Core Java topics such as OOP, collections, exception handling and multithreading come up repeatedly, and SQL and DBMS normalization appear in a couple of accounts.
Resume depth matters too. One candidate was pressed on exactly how they had used Redis and RabbitMQ, and others were asked to defend project design choices. Manager, director and HR rounds are described as conversations about fit and communication, and one candidate called the HR round a test of composure. Outcomes in the reports are mixed, with two offers and several rejections. Round counts vary widely between accounts, so confirm the format with your recruiter.
Synthesized from 11 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Informatica process.
The process felt pretty standard for an SDE intern role at Informatica, but it was still useful to know what they were looking for going in. It started with an online assessment made up of multiple-choice questions, and the topics were broad: data structures, programming languages like C/C++, DBMS, operating systems, and networking. After that, the technical interview was more about judging how I think through problems than throwing anything overly exotic at me. The main questions I got were to introduce myself and walk through my projects, so I spent a good amount of time explaining what I built, why I built it, and what I learned from it.
What stood out to me was that the interview leaned heavily on fundamentals and communication. It wasn’t a super deep coding round based on my experience, but they did want to see whether I could explain my work clearly and connect it back to core CS concepts. I’d recommend being ready to talk comfortably about every project on your resume, especially the design choices and any technical tradeoffs. Also, don’t ignore the MCQ-style basics, because that first screen covered a wide spread of subjects rather than just algorithms. I didn’t get an offer in the end, but the process itself was straightforward and pretty representative of a classic campus-style interview flow.
Prep tip from this candidate
Be ready to defend every project on your resume in detail, including why you made specific design choices and what you learned. Also review the broad MCQ fundamentals they screened on: DBMS, OS, networking, C/C++, and core data structures.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Informatica
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Subscription Overlap | |
| Random SQL Sample | |
| Raining in Seattle | |
| Top 5 Turnover Risk | |
| Monthly Customer Report | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Upsell Transactions | |
| Longest Streak Users | |
| Top 3 Users | |
| String Shift | |
| Scrambled Tickets | |
| Find the First Non-Repeating Character in a String | |
| Find Bigrams | |
| Size of Joins | |
| Comments Histogram | |
| N-gram Dictionary | |
| Customer Orders | |
| Rolling Bank Transactions | |
| Prime to N | |
| Minimum Change | |
| P-value to a Layman | |
| Get Top N Frequent Words | |
| Last Transaction | |
| Rectangle Overlap |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial screen that is typically online or proctored. Descriptions include multiple-choice questions on Java, DSA, DBMS, aptitude and logical reasoning, and a separate coding test. One report said only a small group advanced. Expect breadth across fundamentals rather than one deep algorithm.
One candidate reports an early conversation with the hiring manager that was conversational and behavioral, covering their background, the role and past work. Have concise examples of your projects ready, since this stage may not be heavily technical.
Candidates report medium-difficulty problems such as LRU cache, array sorting, matrix rotation or spiral printing, and stack or linked list tasks. Core Java, OOP, multithreading, SQL and DBMS normalization are also reported. Round counts differ between candidates, and some mention puzzles. Explaining your reasoning and complexity appears to matter.
Several candidates report interviewers probing the technologies and projects on their resume, including how a tool such as Redis or RabbitMQ was actually used. You may be asked about design choices and tradeoffs, so prepare to explain each listed project in detail rather than naming technologies.
Later rounds are reported as more conversational. Candidates mention discussion of prior work, system design fundamentals such as CAP theorem, culture fit and HR logistics. One candidate described the HR round as testing patience and composure. One reported receiving an offer about a week after the final round.