Conduent software engineer interviews, as candidates describe them, center on SQL, database performance, and object-oriented fundamentals, plus project walkthroughs and behavioral questions. Format varies by level.
$104K
Avg. Base Comp
$120K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Candidates who interviewed for software engineering roles at Conduent describe a process that varies by level, but SQL and database fundamentals appear in every account.
An associate-level candidate reports a single session with a friendly technical panel. It covered project experience, test cases, Python object-oriented concepts, lists versus tuples, joins and self-joins, and a request to sketch a project's architecture and walk through code. There was no separate coding assignment, and the candidate felt the expectations went beyond the job description.
An applications engineer candidate describes a longer path: an aptitude test, a round on understanding the job description, an hour-long video call with a programmer and a project manager, then an on-site conversation with a manager. The technical call covered referential integrity, query optimization through indexing, query plans and join efficiency, polymorphism, and DBMS basics tied to the resume.
A senior candidate reports three rounds: a virtual screen on Angular child-to-parent communication and SQL, an in-person round on Salesforce integration procedures, named credentials, and deduplicating account records safely, and an HR conversation about compensation and expectations. Those Salesforce topics were reported by only one candidate, so treat them as role-specific rather than standard.
All three of these candidates reported no offer. For preparation, practice explaining why you chose a design in your own projects, and be ready to reason about query performance out loud. Also prepare a clear answer for why you want to work at Conduent, since motivation questions came up in the associate-level account.
Synthesized from 4 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 Conduent 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 Conduent
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Employee Salaries | |
| Prime to N | |
| Largest Salary by Department | |
| Top 3 Users | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Raining in Seattle | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| Size of Joins | |
| Retailer Data Warehouse | |
| P-value to a Layman | |
| Maximum Profit | |
| Find the First Non-Repeating Character in a String | |
| Over-Budget Projects | |
| Hurdles In Data Projects | |
| Real-Time Transaction Streaming | |
| The Brackets Problem | |
| Employee Project Budgets | |
| Repeated Category Purchase | |
| SELECTive Wine Connoisseur | |
| Google Maps Improvement | |
| Cyclic Detection | |
| Get Top N Frequent Words | |
| Find Duplicate Numbers in a List | |
| Resumable Fact Table Load |
Synthesized from candidate reports. Individual experiences may vary.
One applications engineer candidate reports an aptitude test of basic problem-solving, followed by a round about understanding the job description. Other candidates did not describe this step, so it may depend on the role or team. Read the posting closely and be ready to explain what it asks for.
Candidates report video technical conversations. The applications engineer candidate spoke with a programmer and a project manager for about an hour about referential integrity, query speed, OOP, and SQL. The senior candidate's screen covered Angular component communication and practical SQL. Expect resume-linked fundamentals.
The associate-level candidate describes a single session in which the interviewers asked detailed questions about projects, test cases, and reasoning, then asked for an architecture sketch and a code walkthrough. Python OOP, list versus tuple differences, and SQL joins including self-joins also came up. No separate coding challenge was reported.
Two candidates describe in-person conversations. The applications engineer candidate met a manager in a round weighted toward behavioral questions, though technical topics were still fair game. The senior candidate's in-person round was technical, covering Salesforce integration, named credentials, and data deduplication, so content likely varies by team.
The senior candidate describes a final HR round on current compensation, expected pay, reasons for leaving, and deployment process. It was more conversational than technical. Others did not report a separate HR stage, so applicants may encounter this only at some levels.
