>
ACV Auctions
ACV Auctions Software Engineer Interview Guide 2026
Complete ACV Auctions Software Engineer interview guide. Prepare for practical coding rounds, marketplace and real-time auction system design, Python and Go backend questions, and behavioral interviews at a digital wholesale auto marketplace.
5 min read
Updated Sep 2026
5
Rounds6
Categories5 min
ReadTL;DR
ACV Auctions runs digital wholesale vehicle auctions for dealers, twenty-minute live auctions, condition inspections with rich data, transportation, and financing, and its Software Engineer loop is a practical marketplace-tech interview. Expect a recruiter screen, a technical screen with coding at LeetCode easy-medium, then a virtual onsite of a coding round, a system design round often built around real-time auctions or marketplace flows, and behavioral conversations with the manager and team. The backend leans Python and Go on AWS with event-driven patterns, and design questions reward reasoning about bid consistency, WebSocket fan-out, and mobile-first experiences for dealers. Buffalo-headquartered with distributed teams, the culture is scrappy and delivery-focused, and loops close in 3 to 5 weeks.
3-5 weeks
Sample Questions
Design a live auction system with concurrent bidding
Bid serialization and atomicity, ordering guarantees, idempotent submissions, close-time semantics, and real-time fan-out to watching dealers.
Push bid updates to 5,000 watchers within a second
WebSocket fan-out through pub/sub, connection management on mobile networks, resync after reconnect, and fallback strategies.
A dealer was charged twice for one vehicle. Investigate and prevent
Payment idempotency forensics, retry paths, missing keys, race windows, plus reconciliation and the guardrails you add.
Process a stream of bid events and maintain auction state
Event-sourced state machine handling out-of-order and duplicate events, coded cleanly with clear invariants, the round's typical flavor.
Design the schema for vehicles, auctions, and bids
Relational modeling with integrity constraints, querying current high bids efficiently, and the index strategy for hot auction reads.
Tell me about shipping a feature fast that you later had to harden
The growth-company trade-off made personal, judgment about acceptable debt, honest follow-through, and lessons applied since.
About the Interview Process
ACV's interviews are run by the hiring team and stay close to the company's real problems. Coding rounds check fundamentals and practical fluency; the design round typically explores a live auction system, bid integrity under concurrency, real-time updates at fan-out scale, or a marketplace flow like vehicle listing and settlement; behavioral rounds gauge ownership and pace fit for a growth-stage public company. Interviewers are candid about their stack and welcome questions, treating the loop as mutual evaluation.
Recruiter Screen
Background, team routing across marketplace, auctions, inspections, transport, and data teams, plus logistics and compensation range.
Technical Screen
One or two practical problems in a shared editor at easy-medium difficulty, graded on correctness, edge cases, and communication.
Onsite: Coding
A deeper problem, often data-processing or state-machine flavored, processing bid events, deduplicating updates, with follow-ups on testing and extension.
Onsite: System Design
Design a live auction service, bid handling under concurrency, WebSocket updates to watchers, auction close semantics, or an adjacent marketplace system like title and payment settlement.
Onsite: Hiring Manager & Behavioral
Ownership stories, pace and ambiguity comfort, cross-functional collaboration, and motivation, plus an honest overview of the team's roadmap.
Timeline
3 to 5 weeks with efficient scheduling and quick post-onsite decisions.
Tips
In the auction design, nail bid correctness first, ordering, atomic compare-and-set on high bid, and no lost updates, before scaling the fan-out.
Name idempotency for bid submissions and payments, retried requests must not double-bid or double-charge.
Reason mobile-first, dealers bid from phones in noisy lots, so latency, reconnection, and offline grace matter and mentioning them lands.
Ask about the inspection data side, condition reports with photos and diagnostics feed ML and pricing, and interest in it reads well.
The auction design round
ACV's home-turf design question is the twenty-minute live auction. A strong answer secures correctness first, bids serialized per auction through atomic conditional updates or a single-writer event log, strict ordering with server timestamps, idempotency keys so retries never double-bid, and clean auction-close semantics including last-second bid handling. Interviewers push on races, two dealers bid the same amount simultaneously, a bid arrives as the clock expires, and expect precise answers.
Then comes distribution, thousands of dealers watching an auction need sub-second bid updates, which means WebSocket connections fanned out through a pub/sub layer, reconnection with state resync for flaky mobile networks, and graceful degradation to polling. Closing the loop with observability, bid latency percentiles, dropped-connection rates, auction-close audit trails, completes an answer that matches how ACV actually thinks.
The platform beyond the gavel
ACV is more than the auction moment. Condition inspections generate rich structured data, photos, audio of engine sounds analyzed by ML, OBD codes, and undercarriage imaging, that powers trust in sight-unseen wholesale purchases plus pricing products and guarantees. Transportation, floor-plan financing, and title workflows extend the marketplace into logistics and fintech territory, giving design interviews plenty of adjacent material, settlement flows, document pipelines, and pricing services.
Engineering culture is delivery-oriented and pragmatic, Python and Go services on AWS, event-driven backbones, React and native mobile clients, with teams sized small enough that individual ownership is real. Buffalo headquarters anchors the company, but engineering hires broadly remote in the US, and behavioral rounds calibrate for engineers who thrive with autonomy and direct customer proximity.
Leveling & Compensation
| Level | Title | YoE | Total Comp (USD/yr) |
|---|---|---|---|
SE | Software Engineer | 1-4 yrs | $110k - $165k |
Sr SE | Senior Software Engineer | 4-8 yrs | $140k - $210k |
Staff SE | Staff Software Engineer | 8+ yrs | $170k - $255k |
Software Engineer
Ships features across a service and its clients, participates in on-call, and grows ownership of marketplace flows.
Senior Software Engineer
Owns systems end to end, leads designs for real-time and event-driven services, and mentors while delivering at pace.
Staff Software Engineer
Drives architecture across teams, owns the hardest consistency and scale problems, and raises standards platform-wide.
How to Stand Out
Behavioral Focus Areas
Ownership: lean teams where engineers carry features end to end
Trust and transparency: the marketplace's value is honest vehicle data
Bias for action: a growth company that ships and iterates
Customer empathy: dealers run their businesses on these tools
Collaboration: product, inspections, and operations work tightly with engineering
1.
Practice easy-medium coding with clean execution, hash maps, intervals, and queue problems are representative.
2.
Prepare an auction design answer, a live auction with concurrent bids is ACV's signature system, get comfortable with bid ordering, race conditions, and real-time fan-out.
3.
Review event-driven patterns, queues, pub/sub, idempotent consumers, and outbox-style consistency fit the platform's architecture.
4.
Refresh SQL and data modeling, vehicles, auctions, bids, and transactions make natural schema-design questions.
5.
Know WebSocket basics, pushing bid updates to thousands of watching dealers is a core flow worth being fluent about.
6.
Bring stories of shipping quickly and owning outcomes, the culture rewards scrappy delivery with quality judgment.
Related Courses
Recommended Resources
FAQ
Do I need auction or automotive experience?
No. General backend and distributed-systems skills transfer directly, and the domain is learnable quickly. Thinking through bid concurrency and real-time fan-out before your loop is the highest-value domain preparation available.
What languages are used in interviews?
Any mainstream language for coding rounds, Python is the most common choice and matches much of the backend, with Go significant in newer services. Design rounds are language-agnostic.
How stable is ACV as an employer?
ACV is public, a category leader in digital wholesale auctions, and has grown steadily while the wholesale market digitizes. Like all growth companies it manages spend cycles, ask hiring managers about the team's roadmap directly, they answer candidly.
Is the role remote?
Many engineering roles are US-remote with Buffalo as the headquarters hub and periodic team gatherings. Confirm per posting, and expect a distributed-team working style regardless of your location.
Comments
