>
Ad Hoc
Ad Hoc Software Engineer Interview Guide 2026
Complete Ad Hoc Software Engineer interview guide. Prepare for the fully remote civic-tech hiring process, practical coding exercises, accessibility and government platform questions, and structured behavioral rounds.
5 min read
Updated Sep 2026
5
Rounds6
Categories5 min
ReadTL;DR
Ad Hoc is a fully remote civic-tech company building digital services for the US government, VA.gov, HealthCare.gov, Medicare tools, and CMS platforms, and its Software Engineer process reflects both government contracting and modern engineering culture. Expect a recruiter screen, a structured technical interview built around practical exercises, code reading, small implementations, API design, rather than LeetCode puzzles, and behavioral rounds using consistent rubric-scored questions about collaboration and remote work. US citizenship or residency requirements and a federal background check apply to most roles. The company values accessibility, plain communication, and shipping incrementally inside government constraints. Interviews are humane and well-organized, and the process runs 3 to 6 weeks including contract-assignment logistics.
3-6 weeks
Sample Questions
Add a validated field to this form, end to end
The practical-exercise archetype, frontend markup with accessibility, API validation, persistence, and tests, narrated while pairing.
A nightly batch from an upstream agency arrived malformed. Handle it
Defensive parsing, per-record error isolation, alerting, and idempotent reprocessing, the daily texture of government data integration.
Design an API fronting a legacy eligibility system
Modern JSON API over a slow, batch-oriented backend, caching, timeouts, graceful degradation, and honest error surfaces for users.
What makes this form inaccessible, and how do you fix it?
Labels, semantic structure, keyboard navigation, and error messaging, WCAG fundamentals applied to a realistic government form.
How do you keep a distributed team aligned without meetings?
Remote-maturity evaluation, decision documents, async review, and over-communication habits, answered with concrete practices.
Why does government technology work matter to you?
Mission sincerity check, a genuine connection to public service outcomes reads clearly against rehearsed enthusiasm.
About the Interview Process
Ad Hoc runs deliberately structured, bias-aware interviews, consistent questions, rubrics, and practical exercises over whiteboard hazing. Technical rounds simulate the job, working with existing code, building small well-tested features, and discussing API and integration design for systems that talk to legacy government backends. Behavioral rounds probe remote-work maturity and mission alignment with the same structure. After an offer, contract assignment and background-check logistics add calendar time before starting.
Recruiter Screen
Background, eligibility for federal work, salary bands, which are published transparently, and program routing across VA, CMS, and other contracts.
Technical Interview
Structured technical conversation, walking through code, discussing how you build and test services, and applied questions from the team's stack.
Practical / Pairing Exercise
A hands-on session, implementing a small feature, extending an API, or debugging with tests, done collaboratively with think-aloud narration.
Behavioral Round
Rubric-scored questions on collaboration, remote work, feedback, and inclusion, consistent across candidates by design.
Contract Assignment & Clearance
Post-offer program matching and federal public-trust background check paperwork before your start date.
Timeline
3 to 6 weeks for the interview itself, with background checks adding weeks before onboarding.
Tips
Think aloud through practical exercises, the rubrics reward communication and process, not just working code.
Mention accessibility proactively when designing anything user-facing, it is a first-class requirement here, not a nice-to-have.
Show comfort with legacy integration, government systems mean SOAP services, batch files, and decades-old databases behind modern APIs, and pragmatic patience with that reality fits.
Write follow-ups clearly, every written interaction demonstrates the async communication the company runs on.
What they test
Ad Hoc's technical evaluation mirrors civic-tech work. Exercises favor realism, read this route handler and explain what it does, add a validated field to this form end to end, design the API that fronts a legacy eligibility system, in mainstream stacks like JavaScript and TypeScript, Ruby, Python, and Go. Testing habits, error handling for unreliable upstreams, and clear naming score heavily, raw algorithmic speed does not.
Accessibility is genuinely evaluated. Government digital services must serve users with disabilities, on old devices, and on slow connections, so semantic markup, form design, and progressive enhancement come up in frontend-flavored rounds, and empathy for constrained users comes up everywhere. A candidate who has never thought about screen readers can close the gap with a focused evening on WCAG basics, and should.
Working in civic tech
Ad Hoc emerged from the HealthCare.gov rescue and now runs major modernization programs, veteran-facing services on VA.gov, Medicare enrollment tools, and CMS platform APIs. The work means shipping modern software inside federal reality, ATO security processes, legacy system integration, procurement cycles, and stakeholders measured in agencies, delivered by small empowered teams practicing continuous delivery where the environment allows.
The company is fully remote since founding, with mature async practices, published salary bands, and structured career ladders. Compensation is transparent and solid, generally below big-tech totals, with the offsets of mission, work-life balance, and remote-first sanity. The strongest fit is engineers who find meaning in the fact that their deploy helps a veteran file a disability claim, interviews screen for that sincerity.
Leveling & Compensation
| Level | Title | YoE | Total Comp (USD/yr) |
|---|---|---|---|
SE II | Software Engineer II | 2-5 yrs | $100k - $140k |
Sr SE | Senior Software Engineer | 5-9 yrs | $125k - $170k |
Staff SE | Staff Software Engineer | 9+ yrs | $150k - $205k |
Software Engineer II
Ships tested features on a program team, integrates with government systems, and communicates effectively async.
Senior Software Engineer
Owns services and technical decisions on a program, mentors, and navigates federal constraints while shipping continuously.
Staff Software Engineer
Drives architecture across program teams, leads technical strategy with agency stakeholders, and raises engineering standards.
How to Stand Out
Behavioral Focus Areas
Mission: improving government services for veterans and patients is the point
Remote maturity: async writing and self-direction in a fully distributed team
Inclusivity: accessible software and inclusive teams are core values
Pragmatism: shipping incrementally inside federal constraints
Collaboration: pairing, review, and blameless improvement
1.
Practice practical exercises, reading unfamiliar code and explaining it, implementing a small feature with tests, and designing a JSON API cover the technical formats.
2.
Learn accessibility fundamentals, semantic HTML, ARIA basics, and why WCAG matters, Ad Hoc builds for everyone by federal mandate and conviction.
3.
Refresh web platform knowledge, HTTP, REST conventions, forms, and browser behavior, government services are web services.
4.
Prepare remote-work stories, async communication, documenting decisions, and collaborating across time zones are rubric-scored.
5.
Read about the products, VA.gov and HealthCare.gov modernization stories show what the work actually is, and referencing them signals real interest.
6.
Check eligibility, most roles require US residency and passing a federal public-trust background check.
Related Courses
Recommended Resources
FAQ
Do I need a security clearance?
Most roles require a federal public-trust background check rather than a security clearance, plus US citizenship or residency depending on the contract. The check reviews criminal, financial, and employment history and takes weeks, honesty on the paperwork is essential and most engineers pass without issue.
Is the interview LeetCode-style?
No. Ad Hoc deliberately uses practical exercises, code reading, small implementations, API design, with structured rubrics, because they predict job performance better and reduce bias. Prepare by building and explaining real things, not by grinding puzzles.
What is compensation like?
Transparent, salary bands are published on job postings, solid, and below big-tech totals, with strong benefits and genuine work-life balance. There is no equity upside; the mission and sustainability are the differentiators.
How does contract work affect job stability?
Ad Hoc holds large multi-year federal contracts, and engineers move across programs as contracts evolve. Government demand for digital modernization has proven durable, but recompetes are real, asking about a program's contract timeline is reasonable diligence.
Comments
