Incedo Inc. Software Engineer interviews typically start with an online or written screening test, move through one or two technical rounds on SQL, DSA, OOP, and CS fundamentals, and close with HR; one candidate reported about six weeks end to end.
$103K
Avg. Base Comp
$130K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Incedo Inc.'s Software Engineer interviews follow a fairly consistent shape across candidate reports: a screening test, one or two technical rounds built around core computer science fundamentals, and a closing HR conversation. The screening stage has run on AMCAT or the Mercer Metti platform, and one candidate instead faced a written test of code snippets and multiple-choice questions. Expect aptitude and core-concept questions rather than trick problems; this stage acts as a gate before the interviews.
Technical rounds lean on SQL joins and queries, easy-to-medium data structures and algorithms on arrays and strings, and object-oriented programming concepts. One candidate was asked to code merge sort from scratch. Another got a Java coding question focused on Java 8 streams alongside a SQL query. Interviewers repeatedly push you to explain your own resume projects, the tech stack, and why you made certain choices, so be ready to articulate impact rather than list technologies. OS and DBMS concepts came up naturally in conversation for one candidate. Another reported deep probing on multithreading, virtual destructors, and dynamic memory allocation, plus operating systems and computer networks.
The second round sometimes adds a different angle. One candidate's included a leadership component testing analytical thinking and quick decisions under pressure, another described scenario-based problems, and one process added a client-facing round. A senior candidate who expected an HR discussion at the office was given an additional technical round first.
On timing, one candidate described the process spanning about six weeks with long gaps between rounds. After an offer, two candidates reported friction, including compensation that didn't match earlier conversations and a stalled offer after an early-release request, so confirm every detail in writing before resigning from a current job.
Synthesized from 14 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 Incedo Inc. process.
My experience interviewing at Incedo Inc. for a Software Engineer position was disappointing, though not for the technical reasons you might expect. The process itself felt chaotic. I started with a written test containing code snippets and multiple-choice questions. If you pass that, you move to two technical rounds followed by HR. The technical interviews asked about projects I'd worked on and expected me to solve some scenario-based problems they posed. But the bigger issue was what came after receiving the offer. The scheduling was completely disorganized—I received several last-minute calls asking me to join interviews immediately with no advance notice, making it nearly impossible to prepare properly. When the offer finally came through, the compensation didn't match what had been discussed in earlier conversations. I had to follow up multiple times to get that corrected, and even then there was no clear explanation for the discrepancy. The joining date kept being listed as tentative. I asked for an updated offer letter and a concrete timeline, but those requests went unaddressed. Meanwhile, they were asking me to start onboarding documentation without confirming basic details. The whole thing felt poorly coordinated and unprofessional. Ultimately, I decided to decline the offer because the lack of clear communication made me concerned about how the actual employment experience would be.
Prep tip from this candidate
If you get an offer from Incedo, nail down compensation, joining date, and location details in writing before accepting—don't rely on verbal agreements or assume tentative communications will be formalized later.
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 Incedo Inc.
Find the longest increasing subsequence in a list of integers.
| Question | |
|---|---|
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Employee Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| Find the Missing Number | |
| Largest Salary by Department | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Size of Joins | |
| Comments Histogram | |
| Raining in Seattle | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Retailer Data Warehouse | |
| Minimum Change | |
| Flight Records | |
| Upsell Transactions | |
| Lowest Paid | |
| Level Of Rain Water In 2D Terrain | |
| P-value to a Layman | |
| Download Facts |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a screening test. Reported formats include AMCAT covering aptitude, behavioral, and technical content; the Mercer Metti platform at an easy level focused on core concepts; and a written test with code snippets and multiple-choice questions. This stage acts as a gate before technical interviews begin.
The first technical round typically covers SQL joins and queries, easy-to-medium DSA on arrays and strings, and OOP concepts. One candidate faced a Java 8 streams coding question. Interviewers commonly ask candidates to walk through resume projects and explain their tech stack and design choices, and difficulty is generally described as moderate.
A second round appears in several reports and varies by candidate. One candidate coded merge sort and discussed Agile, OS, and DBMS. Another's round included a leadership component on analytical thinking and quick decision-making, and others described scenario-based problems. One process probed multithreading, virtual destructors, and dynamic memory allocation and added a client-facing round. A senior candidate faced a surprise in-office technical round before HR.
The process usually closes with an HR round covering culture fit, motivation, and career goals, which candidates describe as relaxed. Two candidates reported friction around the offer: a stalled offer after an early-release request, compensation that didn't match earlier discussions, and last-minute scheduling calls. Get offer terms and start dates confirmed in writing before making employment decisions.
