Candidates describe the Coforge Software Engineer interview as centered on Java, OOP, SQL and DBMS fundamentals, with close questioning on resume projects and an HR conversation. Format and outcomes vary by report.
$105K
Avg. Base Comp
$125K
Avg. Total Comp
2-7 rounds
Typical Rounds
Not reported
Process Length
Reports for the Coforge Software Engineer role point to an interview that rewards solid fundamentals and the ability to explain your own work more than hard algorithm puzzles. Java comes up most often: OOP concepts, newer Java features, writing code with Java 8 features, and core Java and Spring Boot basics. One candidate was asked to design a truly immutable class with defensive copies of reference-type fields, and another to solve a problem using Java Streams. Experienced candidates also mention Docker, REST Assured, APIs, microservices and some Angular. SQL queries, DBMS, operating systems and networking fundamentals appear as well.
Coding is usually modest. One candidate had a sorting problem and recommended practicing string and array code aloud. Another said the difficulty came from detailed Java knowledge rather than advanced algorithms.
Your resume gets real attention. Candidates were asked about the technologies they listed, how they had used Spring Boot in actual work, and specific tools such as Postman for API testing. Every technology you list should be something you can explain in detail.
The format differs by route:
One HR and managerial discussion lasted about an hour and still included technical and banking-domain questions. One candidate who was told verbally they were selected never heard back, so ask HR for a written timeline and a named contact.
Synthesized from 41 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 Coforge process.
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 query to return duplicate rows
| Question | |
|---|---|
| Sort Strings | |
| Swap Variables | |
| Data Pipelines and Aggregation | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top 3 Users | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Subscription Overlap | |
| Find the Missing Number | |
| Top 5 Turnover Risk | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Largest Salary by Department | |
| Size of Joins | |
| Prime to N | |
| Scrambled Tickets | |
| Find Bigrams | |
| Last Transaction | |
| Upsell Transactions | |
| Longest Streak Users | |
| Payments Received | |
| Bagging vs Boosting | |
| String Shift | |
| Customer Orders | |
| Repeated Category Purchase | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
Two candidates, one through campus recruitment, began with an online assessment, and one notes it included coding. Its sections were not described in detail, so prepare for basic coding alongside CS fundamentals.
One candidate put the technical interview at about 45 minutes. Questions center on Java and OOP, Java 8 features, Spring Boot, SQL queries, DBMS, and sometimes operating systems or networking. Coding prompts tend to be modest, such as a sorting problem or a Java Streams exercise. One campus candidate was unexpectedly asked to write Arduino code.
Interviewers dig into resume items. Candidates were asked about technologies on their resume, API work using Postman, and how Spring Boot had been used in real work. Prepare a concise walkthrough of each listed project, including your own contribution and the decisions behind it.
Some candidates describe longer paths. One lists three technical interviews and two client rounds that mixed technical and behavioral questions across Java, Spring Boot, microservices, Docker and API testing. Another had a second round that went deeper into Spring Boot and project-level discussion. These are individual reports, not a fixed format.
HR conversations cover background, skills and projects, and one campus candidate was asked directly to sell themselves to the company. Another described an HR and managerial discussion of about an hour that included technical and banking-domain questions. One candidate was told verbally they were selected but got no follow-up, so confirm the timeline in writing.
