Tabby Software Engineer (SDE) Interview
Pragmatic Go coding, payments system design, a real-world case study, and six values — remote-first.
Start the Tabby mock interview → See all boards
A free AI panel interview that questions you in Tabby’s style, follows up when an answer is thin, and returns a scored, evidence-backed report — seeded from your own practice history on Wrexa Edge.
The Tabby interview, in brief
Tabby is MENA's leading Buy-Now-Pay-Later and shopping/payments app and the region's first fintech unicorn, with offices in Riyadh, Dubai and Cairo and a distributed workforce across 20+ countries. Used by tens of thousands of brands, it puts engineers on real payments infrastructure at scale — and is notably remote-friendly, advertising many engineering roles fully remote.
A typical funnel is a recruiter/phone screen, a technical interview (live coding plus some system-design discussion; data/risk roles skew to Python, probability and statistics), a distinctive case-study exercise with a short presentation, a behavioural/values interview, and a hiring-manager team-fit round. Backend is Go microservices; the org is relatively small, so exact ordering and counts are approximate.
Interview rounds
-
1. Recruiter / phone screen 15–30 min
-
2. Technical interview 30–60 min · live coding + design
-
3. Case study Scenario exercise + short presentation
-
4. Behavioural / values STAR
-
5. Hiring manager Team fit
Coding & DSA topics
System design
Expected from mid-level up, and payments-native: designing a checkout/payment flow, an idempotent payment API that never double-charges, a ledger with consistency guarantees, or a risk/fraud/credit-decisioning service. Expect trade-off discussion on reliability, consistency, retries and latency rather than pure algorithms. A roughly 90-minute system-design round appears in candidate reports.
Behavioural round
Tabby publishes six values: act as owners and hold ourselves accountable; lead with empathy and assume positive intent; move with urgency; stay humble, stay hungry; sweat the big stuff and drive meaningful impact; and be honest — thoughtful when giving feedback, mindful when receiving it. Behavioural rounds probe ownership, bias-to-action and feedback culture with STAR questions.
Representative question categories
Patterns in Tabby’s style — not verbatim proprietary questions.
- Hashmaps & two pointers — Easy-to-medium array/string problems.
- Practical coding — An API / data-manipulation task tied to a payments scenario.
- Idempotent payments — Design a payment/checkout API that never double-charges.
- Risk service design — Design a risk/fraud or credit-decisioning service with consistency and latency trade-offs.
- Case study — Frame a real-world scenario, choose a pragmatic solution and present the trade-offs.
- Tabby values — A time you shipped under ambiguity or drove urgent, high-impact work.
How to prepare
Do
- Prepare the case study and presentation, not just LeetCode — clear written and verbal communication is weighted in a distributed org.
- Frame system design in payments terms: idempotency, exactly-once, ledger consistency and retries.
- Practise Go idioms for backend roles; Python plus statistics for data/risk roles.
- Map your stories to the six values — ownership, urgency and honest feedback.
Avoid
- Treating it as a pure algorithm gauntlet and under-preparing the case study and presentation.
- Ignoring payments-domain concerns — double-charge, idempotency, consistency — in the design round.
- Weak async or written communication in a remote-first context.
- Not demonstrating ownership and bias-to-action in behavioural answers.
Who can apply
The ladder spans entry/graduate through junior, mid, senior and expert/staff, with roles skewing mid-to-senior and experienced. Hiring is strongly remote across 20+ countries; new-grad pipelines are less prominent than experienced hiring. Some level titles beyond senior are not publicly documented.
Tabby interview FAQ
- Does Tabby have a coding online assessment?
- No standardised public timed OA platform is documented. Instead Tabby uses a case-study / scenario exercise with a short presentation as a distinctive stage, alongside a live technical interview. The exact format is confirmed with the recruiter.
- What language does Tabby use?
- Tabby's backend is primarily Go in a microservices architecture (Docker/Kubernetes, cloud). Data- and risk-oriented roles also use Python with probability and statistics.
- What does Tabby's system-design round focus on?
- Payments-native design: checkout/payment flows, idempotent APIs that never double-charge, ledger consistency, and risk/fraud services — with trade-offs on reliability, consistency and latency. A roughly 90-minute design round is reported.
- Is Tabby remote?
- Yes — Tabby is notably remote-friendly, with a distributed workforce across 20+ countries and many engineering roles advertised fully remote. Clear written and verbal communication is weighted accordingly.
Practise now
Rehearse the full loop with an AI panel modelled on Tabby’s process, in text, voice, or video.
Other company interviews
Verified from
Wrexa Edge is an independent exam-prep platform and is not affiliated with, authorised by, or endorsed by Tabby. This guide is based on publicly documented interview practice; it does not reproduce any employer’s internal rubric or question bank, and it does not predict a hiring outcome.