| Interview rounds | Life Story, craft, pair programming, technical leadership. | Technical screen, system design, bug bash or integration, behavioural and writing signal. |
| Frontend depth | Merchant workflows, admin UI, storefronts and product polish. | Dashboard, developer tools and API ergonomics, usually less frontend-only. |
| Backend depth | Commerce primitives, app platform, checkout and scaling merchant traffic. | Payments, ledgers, idempotency, APIs and reliability. |
| Coding style | Pairing on realistic product work and shipped-code discussion. | Practical debugging, correctness and maintainable implementation. |
| System design depth | Product architecture across UI, API, data and commerce workflows. | Payments infrastructure, failure modes and API design under strict correctness. |
| Behavioural framework | Life Story, autonomy, impact and directness. | Written clarity, user empathy and ownership. |
| Take-home | Usually replaced by craft or pairing. | Possible practical exercise, team dependent. |
| Decision speed | Remote and direct, often clear after final. | Deliberate when role fit and written signal are debated. |