Tabby interview, and the code you will be asked to review.

Tabby does not publish its engineering loop. The rounds below come from candidate reports on Glassdoor, seen in search snippets, and from Tabby's own job ads and recruiting posts. Glassdoor's average across 74 reports is about three weeks, and candidates who reach team matching describe it running longer.

Candidates on Glassdoor, seen in search snippets, describe Tabby's first technical interview as some standard Go questions followed by a choice: review a piece of Go code, or do live coding in another language. Senior backend candidates list database transactions, Go project structure, and money stored as floating-point numbers among their interview topics. Nobody has shared the review code itself, so the list below is a checklist built from those topics and from what a payments codebase tends to get wrong. Work through the code in roughly this order.

• Read the whole thing before you comment: Spend the first few minutes working out what the code is meant to do and saying it back to the interviewer. A review that starts with naming nits on line 3 and misses a lost payment on line 40 is the classic way to do badly here.
• Check how money is stored: Look for float64 amounts, arithmetic on them, and comparisons with ==. Say what goes wrong (0.1 + 0.2 is not 0.3, and rounding drifts across installments) and propose integer minor units or a decimal type, with the currency kept next to the amount.
• Follow every database transaction: Look for a read and a write that should be atomic but are not, a transaction with no defer tx.Rollback(), an ignored Commit error, and a call to an outside service while the transaction is open. Say which isolation or locking you would use and why.
• Ask what happens when a request is retried: Payment code gets called twice: by a client retry, a queue redelivery or a timeout. Look for a charge or a write with no idempotency key or unique constraint, and suggest one.
• Look at errors and context: Find ignored errors, errors logged and then swallowed, errors returned without wrapping (%w), and a context.Context that is not passed down to the database or HTTP calls, so timeouts never reach them.
• Look for concurrency problems: Check for a map written from several goroutines without a lock, goroutines that can block forever on a channel, and work started in a goroutine whose error nobody reads.
• Comment on structure last: Once correctness is covered, say how you would organise it: business logic out of the handler, storage behind a small interface defined where it is used, and how that makes the code testable. Senior backend candidates list project structure as a topic, so keep a few minutes for it.
• Rank what you found: Finish by sorting your comments into what you would block the merge for, what you would fix soon, and what is style. It shows the judgment the round is really about, and it is the summary the interviewer will remember.

If you pick a language other than Go, candidates report live coding instead of the review. Ask your recruiter which one you will get and how long you have.

Tabby publishes six values on its careers page. A talent partner's post on how they were written says they came from a staff survey, business needs and the traits of top performers, so expect the team-fit round to look for them.

• Own it: act as owners and hold yourself accountable for the whole of Tabby, beyond your own team
• Lead with empathy and assume positive intent
• Move with urgency: Tabby says it wants to set a new standard in pace
• Stay humble, stay hungry, and never get complacent
• Sweat the big stuff: meaningful impact over small incremental changes
• Be honest and direct: thoughtful when giving feedback, mindful when receiving it

Candidates share few behavioural questions for Tabby. The ones here follow its six values and its recruiters' own advice, and the technical half follows the topics candidates name for the code review.

Tabby's engineering ads do not publish pay, so there are no reliable salary bands to show here. The October 2026 remote Staff Engineer ads list a B2B contract, a tax allowance of up to 20%, 22 paid leave days and stock options; the only salaries Tabby publishes are for customer service roles. A Tabby talent partner wrote that it shares its range on the first call, so ask then. Calibrd benchmarks the pay on any posting you scan against its level and location.

1. Decide before the recruiter call whether you will take the Go code review or live coding in another language, and ask which applies to your role.
2. Have a salary number ready for the first call. Tabby says it shares its range then and does not go above its budget.
3. Practise reviewing Go out loud: take a small service, plant a float money bug, a missing rollback and an ignored error, and time yourself finding and ranking them.
4. Revise database transactions in Go: defer tx.Rollback(), row locking, isolation levels, and keeping outside calls out of an open transaction.
5. Prepare one 90-minute payments design end to end, covering idempotency, retries, scheduling and reconciliation.
6. Prepare stories with numbers for Tabby's values, especially owning an outcome after launch and moving fast without breaking payments.
7. Ask early which team the role is for and what happens if team matching takes longer, since candidates report extra team rounds and delays at this stage.
8. Check the ad's location line. Remote roles are B2B contracts with relocation to the hubs; Riyadh roles are on-site and some ask for Arabic.

This guide covers Tabby's software engineering hiring, its Riyadh-based infrastructure roles and internships, and what data science candidates report. For management and leadership roles the loop is similar but the bar shifts to people, delivery and strategy, so pair it with the leadership interview prep hub. The bar for your exact role comes from the role-by-role guides, and the prep that actually transfers is spoken, so run a mock interview before the real one.

Also interviewing at G42, N26 or Trade Republic? Their guides follow the same format, from the first screen to the offer.

• 01Tabby Careersthe six values, offices in Riyadh, Dubai and Cairo, about 1,000 employees, and the annual allowance (read 16 October 2026)
• 02Tabby, Building Saudi engineering excellencethe stack, the internship steps (apply, base knowledge check, technical challenge interview, offer), the Fall 2026 tracks and the winter intake (read 16 October 2026)
• 03Tabby job board41 open roles; the remote Staff Engineer ads with the B2B contract, tax allowance, stock options and hub relocation; the Riyadh DevOps and security roles (read 16 October 2026)
• 04Tabby, Staff Engineer, RemoteGo, distributed systems, a remote team across 20+ countries, and relocation to Armenia, Georgia, Serbia, Portugal and Spain (read 16 October 2026)
• 05Tabby, Senior DevOps Engineer, Riyadhon-site in Saudi Arabia, work with the Saudi Central Bank, spoken and written Arabic, and CVs in English (read 16 October 2026)
• 06Tabby Insights, How to Prepare for an Interviewa talent partner's advice: numbers in every story, salary discussed on the first call, Tabby's range and fixed budgets (30 July 2024)
• 07Tabby Insights, What is corporate culture and why it matters?how the values were written and what each means (30 July 2024)
• 08Tabby Insights, Scaling Product Teams: from 7 to 280 engineers and PMsproduct and tech growing from 7 people in 2019 to 280 in 2023 (20 February 2024)
• 09Arab News, Tabby raises $233Mthe Series F at a $6.5 billion valuation led by Blue Pool Capital, 25 million users, 70,000 partners, $18 billion+ in yearly volume (14 September 2026)
• 10ME Retail News, Tabby to relocate its headquarters to Saudi Arabiathe move to Riyadh, the MoU with the Ministry of Investment, and 80% of customers in Saudi Arabia (3 October 2023)
• 11Glassdoor, Tabby interviewsan average of about 21 days across 74 reports; the choice of a Go code review or live coding in another language; senior backend topics including database transactions, Go project structure and money as floats; the Go questions and code review, the 90-minute system design, the team-fit round with a hiring manager and PM, extra team interviews, and no reply after team matching; seen in search snippets
• 12Glassdoor, Tabby Software Engineer interviewssoftware engineer interview reports for Tabby; seen in search snippets
• 13Glassdoor, Tabby Data Scientist interviewsa skills test and group panel, advanced Python, probability and statistics, and the three-people probability question; seen in search snippets

Interview processes change. This reflects widely-reported and sourced conditions as of 2026 — confirm specifics with your recruiter, and treat it as a map rather than a guarantee.