Software Engineer
Coinbase · Senior
Next: your first full round
Do the Online practical assessment round.
One full round, as long as theirs, shows where you stand before you work on anything specific.
The rounds
Pick a round to see what it asks of you and where you stand on it.
Online practical assessment
Assess practical implementation across staged requirements before the live loop.
Coding · 90 minSet up this round
Not tried yetNo attempt yet.
What strong sounds like
- Defines simple data structures and interfaces that support each stated operation and later requirement.
- Writes coherent code that preserves behavior across incremental requirements and explains the intended control flow.
- Identifies empty, missing, repeated, expired, and boundary inputs and handles them deliberately.
- Performs a focused verbal dry-run on representative and edge cases using the code as written.
Expect to be pushed on
Add a requirement that changes state lifetime or lookup semantics.
Ask how the design behaves with missing, repeated, or expired records.
Shapes of problem you may get
- Stateful key-value or file-system operations with later feature additions
- Time-based lookup, expiration, filtering, or pagination
- Small service model with nested records and updates
How to prepare
- 01
Select one stateful implementation task
Choose one practice task involving key-value state, expiration, filtering, or pagination. Define the data model, interfaces, invariants, and the smallest required operation set before adding later requirements.
The supplied reports describe different assessment formats, and Coinbase does not publish a stable Senior-specific assessment. Use a practical stateful task as a format-specific recommendation.
Company research
Your first try takes the full 90 minutes, like the real one.
What they look for
Coinbase’s official guide supports pair programming, engineering-manager, and system-design stages, with 60-minute interviews and later 60- or 90-minute coding rounds. Recent Senior Software Engineer reports add pre-recruiter assessments and practical stateful coding. The target-specific order, assessment set, round count, and senior-level architecture bar remain uncertain.
They reward
- Practical, production-like engineering
- Explicit assumptions and honest reasoning
- Ownership through ambiguity and change
What to avoid
- Over-engineer before the required operations work.
- Assume tests or execution will reveal defects; inspect the code manually instead.
- Treat the task as a trick or rush into abstraction.
- Ignore hints or claim correctness without tracing important paths manually.
- Add components without explaining their role or failure behavior.
How sure we are
Worth redoing if you hear something from the recruiter that contradicts this.
Confirmed · 20
Attempts
Every round you’ve done for this job, newest first.
Online practical assessment, Pair programming, System design, and Engineering manager interview have no attempts yet.