What is Tamara's coding round like?

Distinctively, it is an assignment-based live build rather than a timed multiple-choice test: you get about 30 minutes to set up your IDE, then roughly an hour to build a real feature (for example SplitPayment) from a provided UI, plus a system-design question on integrating with the legacy monolith.

What language does Tamara use?

Tamara is Java-primary (Spring / microservices, Kafka, distributed systems, AWS/OCI); it also runs services in PHP, Go and Python. The feature-build round expects clean, tested, production-quality Java.

Does Tamara have a culture-fit gate?

Yes — two dedicated culture-fit rounds, one with HR and a distinctive one with a C-level leader, explicitly test the three values (Owners not Spectators, Resilient Builders, Curious Problem-Solvers). It is a genuine gate.

Does Tamara hire new graduates?

Yes — via a "Builders Program" track for early-career Backend Engineer I, alongside experienced Backend Engineer I/II roles and an APM program for product. Hiring is distributed but centred on Riyadh.

Tamara Software Engineer (SDE) Interview

A live Java feature-build, legacy-integration and payments design, and a C-level culture gate.

Financial / fintech Middle East Web-verified 2026-08

Start the Tamara mock interview → See all boards

A free AI panel interview that questions you in Tamara’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 Tamara interview, in brief

Tamara is Saudi Arabia's leading BNPL / fintech platform, headquartered in Riyadh and a KSA unicorn, operating across KSA and the UAE with tech hubs in Germany, Vietnam, India and Egypt. Engineers build a high-consistency payments/BNPL platform — checkout, ledgers, split payments — at national scale, with a strong ownership culture and early responsibility.

A typical funnel is a recruiter/foundational screen, a technical interview with the hiring manager (experience deep-dive plus technical questions), a distinctive assignment-based live-coding round (build a real feature such as SplitPayment from a provided UI, plus a system-design question on integrating with the legacy monolith), an HR culture-fit interview, and a distinctive culture-fit interview with a C-level leader. Backend and Product tracks are rated the hardest.

Interview rounds

1. Recruiter / foundational screen 15–30 min

Background and motivation; sometimes framed as a "foundational interview", occasionally with the hiring manager.
2. Technical interview (HM) ~45–60 min

Experience deep-dive plus technical questions.
3. Feature-build assignment ~30 min setup + ~1 hr build

A distinctive live build: implement a feature (e.g. SplitPayment) from a provided UI in your own IDE, plus a system-design question on integrating a new module with the legacy monolith.
4. Culture fit (HR) Values-based behavioural

Ownership, resilience and curiosity, mapped to the three values.
5. Culture fit (C-level) Leadership values gate

A distinctive culture-fit interview with a C-level leader — a genuine gate, not a formality.

Coding & DSA topics

Applied feature build (Java)OOP & SOLIDDesign patternsTest-driven developmentData structuresDatabases & transactionsDistributed systems basicsKafka / eventing

System design

System design appears even at IC technical rounds, flavoured by Tamara's real architecture: how to structure a new project/module so it integrates with the old monolithic codebase (strangler-fig / anti-corruption layer), plus payments concerns — split payments, ledgers, transactions and consistency, idempotency, and Kafka-based eventing at BNPL checkout scale. Depth scales with level (Engineer II and above).

Behavioural round

Tamara's three hiring values are Owners, not Spectators (take responsibility, move with intent); Resilient Builders (steady under pressure, learn fast); and Curious Problem-Solvers (ask better questions, challenge patterns). Operating principles include Customer Obsessed, Seek Truth Not Comfort, and Decide with Conviction. Two dedicated culture-fit rounds (HR and C-level) explicitly test these — a values gate.

Representative question categories

Patterns in Tamara’s style — not verbatim proprietary questions.

Feature build — Implement a SplitPayment flow from a given UI in Java in about an hour.
OOP & SOLID — Reason about class responsibilities, SOLID and design patterns for clean, testable code.
Legacy integration — Integrate a new module with a legacy monolith without breaking it.
Ledger design — Design a ledger / split-payment system that never double-charges.
Eventing — Kafka event flows, retries and eventual consistency.
Ownership & resilience — A time you delivered under pressure or owned an outcome.

How to prepare

Do

Be ready to code a real feature live in your IDE — set up your environment fast and write clean, tested Java.
Prepare monolith-to-microservice migration talking points: strangler-fig and anti-corruption layer.
Speak the payments/ledger language: split payments, idempotency and transactional consistency.
Internalise the three values — the C-level culture round is a genuine gate, not a formality.

Avoid

Optimising for LeetCode instead of practising building a clean, working feature end-to-end.
Ignoring tests and SOLID and shipping messy code in the assignment.
Hand-waving the legacy-integration / system-design question.
Underweighting the culture-fit / C-level round or failing to show ownership and resilience.

Who can apply

The public ladder includes Backend Engineer I and II, with a "Builders Program" track for early-career/new-grad Backend Engineer I and an APM (Associate Product Manager) program for product. A typical backend requirement is roughly three to eight years (Java, microservices, TDD, Kafka). Hiring is distributed across KSA, UAE, Germany, Vietnam, India and Egypt, centred on Riyadh.

Tamara interview FAQ

What is Tamara's coding round like?: Distinctively, it is an assignment-based live build rather than a timed multiple-choice test: you get about 30 minutes to set up your IDE, then roughly an hour to build a real feature (for example SplitPayment) from a provided UI, plus a system-design question on integrating with the legacy monolith.
What language does Tamara use?: Tamara is Java-primary (Spring / microservices, Kafka, distributed systems, AWS/OCI); it also runs services in PHP, Go and Python. The feature-build round expects clean, tested, production-quality Java.
Does Tamara have a culture-fit gate?: Yes — two dedicated culture-fit rounds, one with HR and a distinctive one with a C-level leader, explicitly test the three values (Owners not Spectators, Resilient Builders, Curious Problem-Solvers). It is a genuine gate.
Does Tamara hire new graduates?: Yes — via a "Builders Program" track for early-career Backend Engineer I, alongside experienced Backend Engineer I/II roles and an APM program for product. Hiring is distributed but centred on Riyadh.

Practise now

Rehearse the full loop with an AI panel modelled on Tamara’s process, in text, voice, or video.

Start the Tamara mock interview →

Other company interviews

Verified from

Wrexa Edge is an independent exam-prep platform and is not affiliated with, authorised by, or endorsed by Tamara. 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.