
What candidates for DTCC engineering-track roles report: recorded HireVue screens, foundational Java, SQL and OOP questions, and resume-focused panels. Experiences differ a lot by team.
$115K
Avg. Base Comp
$130K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
DTCC's interview experiences for engineering-track roles are not uniform. The reports here come from different titles, including a Senior Associate, an Automation Engineer, a Lead Test Engineer, a Principal Unified Messaging Engineer and two internship candidates, so treat them as a picture of the range rather than a single script.
The most common opener is a recorded HireVue-style screen. Intern candidates described behavioral prompts: why the role, why DTCC, a time they overcame an obstacle, and how they work in teams. The Principal candidate was contacted by a recruiter the day after applying and then asked to complete a recorded pre-screen.
Technical questions skew foundational. The Senior Associate candidate, who received an offer, reported Java constructor overloading, HashMap and ArrayList behavior, SQL queries and a practical OOP problem. An internship candidate faced SQL joins with the USING keyword and object-oriented questions. The Automation Engineer was asked about reading and parsing CSV files, and the Principal candidate about storing test cases in a map with conditional logic.
Later rounds lean on conversation. One intern described a panel that walked through the resume and favorite and least favorite projects, and another had a closing HR interview about fit.
Quality varies by team. Several candidates described disjointed calls, vague questions, or an interviewer who ended a Selenium-focused call after about eight minutes. Ask early what the conversation will cover, say your assumptions out loud, and bring a specific reason for choosing DTCC. One intern reported roughly two months from the first HireVue to the final panel.
Synthesized from 8 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 The Depository Trust & Clearing Corporation (Dtcc) process.
I had a single technical interview scheduled as a Lead Test Engineer. The interviewer didn't turn on his camera, gave no introduction, and skipped explaining the role or what we'd be discussing. He jumped straight into questions about Selenium locators and XPath syntax, asking me to write parent-child locator expressions for HTML tags. The problem was that he kept asking about the same scenario without providing an actual working example, and my background is primarily JavaScript—I mentioned this repeatedly, but he seemed either uninterested or not listening.
He insisted I write Java syntax anyway, as if to test my adaptability. I did my best to answer despite the misalignment, trying to show I could work across languages, but it was clear he wasn't engaged. After about 8 minutes, he said he was done and not interested. No feedback, no discussion of my actual experience, no real conversation about the role or what I could bring. It felt like he was just checking a box, or possibly had already made up his mind before the call even started.
The whole thing was incredibly frustrating and disrespectful of my time. I left feeling like I hadn't been given a fair shot because the interview was never set up for me to succeed—the technical questions were intentionally misaligned with my stated background, and the interviewer showed no interest in finding out if I was actually a fit for the team.
Prep tip from this candidate
Insist early on establishing what you'll be discussing and push back on irrelevant technical questions—clarify your actual background and the gap between what's being asked and your expertise before spending time on answers the interviewer may not even be listening to.
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 The Depository Trust & Clearing Corporation (Dtcc)
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Rectangle Overlap | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Sum to N | |
| Over 100 Dollars |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates began with a recorded video screen. Interns reported prompts about why the role, why DTCC, overcoming an obstacle, and teamwork and leadership. The Principal candidate heard from a recruiter the day after applying and found some question wording hard to follow. The Automation Engineer also started with HireVue.
Both internship candidates described a step after the video screen. One had three days to finish an assessment of about ten questions, roughly five of them video responses with two attempts each. The other reported an online test covering SQL queries, basic coding and aptitude questions.
Reports include Java collections and constructor overloading with a practical OOP problem (Senior Associate), SQL joins using USING plus OOP concepts (internship), CSV parsing (Automation Engineer), a map holding test cases (Principal) and Selenium XPath locators (Lead Test Engineer). Formats ranged from structured to loose.
One intern's final panel focused on a resume walkthrough, favorite and least favorite projects, and motivation. Another intern had an HR interview about fit. The Senior Associate candidate spoke with three people from the hiring department and finished with a recorded video. The Principal candidate got a generic rejection email the next day.