Three candidates describe a practical DOAS software engineer interview: a brief screen, conversations about past work, a hands-on technical session, and a final manager or executive conversation.
$88K
Avg. Base Comp
$125K
Avg. Total Comp
4 rounds
Typical Rounds
14 days
Process Length
Candidates describe the DOAS software engineer interview as practical and conversational rather than puzzle-driven. Two of the three report four rounds, and the third does not give a round count. One candidate for a Software Engineer III role describes a quick nontechnical screen, a deeper discussion of work history and challenges, a two-interviewer technical round, and a final conversation with executives about career goals. Another reports a phone screen, a technical round, and a final conversation with engineering managers that mixed culture and technical topics.
The technical portion is where the reports are most specific. A Sr. Software Engineer candidate was sent an unfinished Ruby on Rails project ahead of time and added features to it during the interview, with five minutes at the end for questions. Other candidates describe technical work that mirrors day-to-day tasks instead of abstract algorithm drills, and one says there was no take-home project. If you are preparing, get comfortable adding features to an unfamiliar codebase and explaining your choices as you go.
Expect behavioral depth too. One candidate says interviewers restated what they heard to confirm understanding, so concrete stories about technical and interpersonal challenges should serve you well. Outcomes varied: one candidate received no offer, one received an offer, and one declined an offer. The evidence is limited to three reports, so treat the details as individual experiences rather than a fixed process.
Synthesized from 3 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 Department of Administrative Services (DOAS) process.
The interview process at the Department of Administrative Services was genuinely well-organized and thoughtful. It spanned four separate rounds where I met with different team members, and the whole thing felt structured without being rigid. They gave me plenty of prep materials upfront, clear instructions, and realistic expectations—not the vague "just code something" scenario that catches people off guard.
The screening was quick and nontechnical, focused on fit and background. Then there was a deeper conversation with two people about my work experience, what I'd learned, and challenges I'd overcome. The technical round had two interviewers and felt surprisingly conversational—not a gauntlet of gotchas. They designed it to actually mirror the kind of work I'd be doing on the job, which made it feel relevant rather than abstract. I could ask questions, look things up, and engage naturally. The final round was with executives and focused on career goals and high-level experience.
What really stood out was how intentional they were about listening. Multiple times they'd say something like, "So what I'm hearing is x, y, and z—does that sound right?" It forced them to actually process what I was saying and gave me a chance to clarify if they'd misunderstood. They mentioned they review notes individually before discussing to reduce bias, which I believed based on how thoughtfully they engaged. The whole team was kind and professional without being stiff. Ultimately I declined the offer for personal reasons, but this was a best-in-class interview experience.
Prep tip from this candidate
Prepare specific examples of technical and interpersonal challenges you've overcome—they use a structured approach with follow-ups, so detailed, honest stories will stand out. Also pay attention to confirmation questions; they'll rephrase what they heard, giving you a chance to catch miscommunications early.
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 Department of Administrative Services (DOAS)
What metrics would you use to track accuracy and validity of the model
| Question | |
|---|---|
| 85% vs 82% | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Closest SAT Scores | |
| Employee Salaries | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Random SQL Sample | |
| Weighted Keys | |
| Flight Records | |
| Prime to N | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Top 3 Users | |
| Raining in Seattle | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| First Touch Attribution | |
| Job Recommendation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a short phone or introductory screen focused on background and fit rather than coding. One describes it as straightforward and brief. Be ready to summarize your experience and why you want a government engineering role.
One Software Engineer III candidate describes a deeper conversation with two people about work experience, lessons learned, and challenges overcome. Interviewers reportedly restated what they heard to confirm it, so prepare specific, honest examples and clarify any misunderstanding.
Candidates report technical sessions that mirror real work and feel collaborative. One Sr. Software Engineer candidate was sent an unfinished Ruby on Rails project beforehand and added features to it live. Another reports two interviewers and being able to look things up. Review the stack and existing-code workflows.
Final rounds are reported as casual conversations. One candidate met engineering managers who mixed culture-fit questions with technical discussion and asked about past decisions. Another met executives and discussed career goals and high-level experience. Prepare to talk about how you make decisions.
