Coforge Data Analyst interview typically runs 4-6 rounds: virtual screening, technical round, client technical round, techno-managerial round, and HR discussion. The process usually takes several weeks and is notably slow, with long gaps and extra follow-ups.
$550K
Avg. Base Comp
$561K
Avg. Total Comp
5-6
Typical Rounds
3-6 weeks
Process Length
We've seen Coforge care less about polished theory and more about whether you can speak credibly from real delivery work. Across candidate experiences, the strongest signal was hands-on front-end depth: one candidate was pressed on Angular interceptors, pipes, RxJS, HTML, and JavaScript, while another was asked highly specific questions about past work, current responsibilities, and what they would do in the role. That tells us they want people who can connect concepts to actual project decisions, not just recite definitions.
A recurring theme is that the company also tests how you operate in a client-facing environment. Our candidates report questions about estimating work, handling conflict, managing a team, and explaining project flow in plain language. Even the coding prompts skewed practical rather than algorithm-heavy, with simple tasks like swapping variables and sorting strings appearing alongside framework-specific discussion. The non-obvious part here is that clarity matters as much as correctness: candidates who could explain their choices and tie them back to delivery seemed to move more smoothly.
We also see a pattern of ambiguity in the process itself, which makes patience and follow-through important. Multiple candidates described long gaps, repeated calls, and shifting expectations even after they were told they were close to an offer. In that environment, the people who stay composed, keep their story consistent, and can re-enter a conversation without sounding rattled tend to leave the best impression.
Synthetized from 2 candidates 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 Coforge process.
The process felt almost done several times, and then it just stopped. It started with two rounds, a technical round followed by a client technical round. After I cleared the first technical round, there was a week-long delay because the HR was on vacation, and then I was told I had moved on to the client technical round. That round went well too, and after that I was told I was basically 90 percent selected and only needed to complete an HackerRank test as a formality. I gave that test, cleared it, and then the project manager started discussing CTC with me over the call because I already had another offer. At that point I was told I had a techno-managerial round, which I also cleared.
After that, the conversation became more about joining details, benefits, and perks, and I was told the offer letter would come in 2–3 days. Two days later, I got another call saying I just needed to have an interaction with the client team lead and that it would be a normal discussion after joining. It turned out to be another interview-style round, and the questions were pretty specific to my past work, what I currently do, and what I would be doing in the role. That was the last conversation I had. I never got any call back, and there was no clear update on whether I was selected or rejected. It honestly felt like a lot of back-and-forth for something that never got closed properly.
Prep tip from this candidate
Be ready for a client-facing discussion that digs into your past projects, current responsibilities, and what you would do in the role, even if earlier rounds make it sound like the offer is already decided. Also expect the process to stretch with follow-up calls after the main technical rounds, so don’t treat the later interactions as purely formal.
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 Coforge
Write a function `sorting` from scratch to sort a list of strings in ascending alphabetical order
| Question | |
|---|---|
| Data Pipelines and Aggregation | |
| Swap Variables | |
| Empty Neighborhoods | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Closest SAT Scores | |
| Monthly Customer Report | |
| First Touch Attribution | |
| Experiment Validity | |
| Prime to N | |
| First to Six | |
| Top 3 Users | |
| Last Transaction | |
| Compute Deviation | |
| Download Facts | |
| Button AB Test | |
| 500 Cards | |
| Random SQL Sample | |
| Largest Salary by Department | |
| Bagging vs Boosting | |
| Subscription Overlap | |
| Month Over Month | |
| Minimum Change | |
| Paired Products | |
| Upsell Transactions | |
| Find the Missing Number |
Synthesized from candidate reports. Individual experiences may vary.
Coforge HR reaches out about an open Data Analyst role and outlines the expected interview flow. In the shared experiences, the recruiter also mentioned whether the process would start virtually or move to an in-office round.
The first interview focuses on practical technical skills and relevant project experience. Candidates were asked about their current work, what they would do in the role, and role-specific technical topics rather than heavy algorithmic problems.
After the initial technical round, candidates may interview with the client side. This round was described as more specific to past work, current responsibilities, and how the candidate would contribute in the new role.
Some candidates are asked to complete a HackerRank test after clearing earlier rounds. In one experience, it was presented as a formality after the candidate had already been told they were close to selection.
This round combines technical discussion with managerial evaluation. Questions covered team handling, conflict resolution, estimation, delivery flow, and how the candidate works in a project setting.
In some cases, there is an additional follow-up discussion with the client team lead or a final HR step before the offer. The conversation may shift to joining details, benefits, CTC, and background verification paperwork, but the process can also stall here without a clear closure.