Design a workflow state machine library
PremiumMachine codingMedium
- Finite state machine
- Transition guards
- Lifecycle hooks
Quick answer
This machine coding interview question asks you to design a workflow state machine library. Aim for a design that meets its requirements at the stated scale, then explain its main components, data flow and trade-offs. Interviewers want to see how you scope the problem, size it and defend each choice.
The problem
Build a workflow state machine library, like the ones teams use to move orders, tickets or loan applications through fixed steps. A developer defines states, events and allowed transitions once, and many workflow instances then move through them. The hard parts are guards, hook order, safe rejections and concurrent events on one instance.
What must a workflow state machine library do?
- Define: A builder declares states, the initial state, final states and transitions from --event--> to with optional guards and actions; build() returns an immutable definition.
- Fire: create(id, context) starts an instance in the initial state; fire(id, event, payload?) moves it, or returns REJECTED with a reason: no such transition, guard failed, or final state.
How well must it do it?
- Safe concurrency: Two events fired at once on one instance are applied one after the other, never interleaved; different instances run in parallel.
- Shared definitions: One immutable definition serves up to 100,000 instances.
What scale should you design for?
Use these numbers in your estimates.
The scale numbers unlock with this questionUnlock
Key concepts
- Finite state machine
- Transition guards
- Lifecycle hooks
- Builder pattern
- Per instance locking
- Audit trail
How you’ll practise
- Requirements
- Entities and interfaces
- Core implementation
- Edge cases and tests
- Extensions
- Wrap-up
Lala, personalized to you, gives a hint when you ask and reviews your design when you are ready.
What do interviewers look for?
In any machine coding design round.
- Clarifies the requirements before drawing anything
- Uses a few numbers that actually change the design
- Draws a clear path from the client to storage
- Picks storage and caching with reasons, not by habit
- Explains what breaks first under load and how to fix it
- States trade-offs openly instead of claiming a perfect design
Questions people ask about this interview question
- Which design type is this question?
- It is a machine coding question. You design a workflow state machine library and explain your choices the way you would in an interview.
- Is this question asked at entry level?
- It is marked Medium. Entry-level engineers can practise it, but it expects you to reason about requirements and trade-offs, not only list components.
- What should I cover first?
- Start with the requirements: what the system must do, how well it must do it and which numbers change the design. Agree on scope with the interviewer before you design anything.
- Can I practise it for free?
- It is a premium question. Sign up and unlock it once for 10 credits; it then stays unlocked. When you finish, Lala, your personalized AI mentor, can review your design for 30 credits.
Related questions
Updated · Written by the SevyDevy team