Updated recently
Last updated:
Quick Answer: Domain full stack developer interview questions come in three blocks: standard full-stack coding, a design or integration round, and the walkthrough round — “walk me through how an order becomes an invoice” — which is where the offer is actually decided. The walkthrough tests whether you can model the business, not whether you know React. Below are the real questions Indian employers ask in 2026, what a strong answer must contain, and where candidates lose the room.
Domain Full Stack Developer Interview Questions: How the Loop Runs
Most hiring loops for this role run four to six rounds over two or three weeks. Knowing which round carries which weight stops you from over-preparing the wrong half.
| Round | Questions you will actually be asked | What it tests | Where candidates fail |
|---|---|---|---|
| Coding | One data-structures problem or a take-home feature with tests | Fundamentals still gate the process in India, whatever the role says | Not testing edge cases — ironically the exact skill this job pays for |
| Full-stack design | Design a returns portal; design a webhook receiver that survives retries | Schema, APIs, auth, caching, failure modes | Skipping idempotency and audit logging entirely |
| Domain walkthrough | How does an order become an invoice? An appointment become a claim? | Whether you know the business or only its vocabulary | Describing the happy path and stopping at partials and reversals |
| Domain modelling | Model partial shipments. Where does a refund live in your schema? | Documents, states, invariants, who owns the truth | Storing derived values (totals) instead of deriving them |
| Integration and data | How do you sync master data with an ERP and handle its outage? | Retries, ordering, reconciliation, anti-corruption layers | Assuming the other system will always answer |
| Behavioural | Tell me about a time a business rule turned out to be wrong | Judgement, and whether you have ever argued with a stakeholder | Answering with a technical story when they asked for a business one |
The Walkthrough Questions, and What a Strong Answer Sounds Like
“Walk me through how an order becomes an invoice.” The default Indian answer goes: customer places order, we ship, we invoice. That is correct for a business with no complexity and gets you a neutral reaction. The answer that moves the room goes: the order is confirmed, lines are allocated against stock — reserved, not deleted — the warehouse picks and ships, and the shipment document, not the order, becomes the trigger for invoicing; invoice lines reference what actually moved, tax is determined per line by place of supply, and payment lands against the invoice with a settlement that finance reconciles against a gateway file. Then, unprompted, you name the three places it breaks: partial shipment, short close after a backorder, and a return that needs a credit note rather than an invoice edit. The panel’s silence after that third point is usually a good sign.
“How does a payment become a settlement?” Authorisation captures intent; capture moves money; the gateway batches captures into a settlement file on a cycle; fees and MDR are deducted; the ledger records gross, fee and net as separate facts; reconciliation matches our records against the file, and anything unmatched becomes an exception queue with an owner. Mentioning chargebacks and refunds as events that post new entries — not as edits to old ones — separates someone who has seen a settlement file from someone who has only read documentation.
“How does an appointment become a claim?” Appointment to encounter to service lines with codes, codes priced, claim assembled and scrubbed against payer rules, submitted, then adjudicated — paid, partially paid or denied line by line — with a patient responsibility that becomes the invoice. Interviewers in healthtech listen for one word: denials. A model with no denial and resubmission path is a textbook model, not one built for a hospital.
“How does a shipment become a receipt?” Goods leave against a delivery note, arrive at the receiving dock, get counted against the purchase order, and the goods receipt posts inventory and a GR/IR liability. Mentioning three-way match — PO, receipt, invoice — and what happens on over- or short-receipt gets you into the ERP conversation that many of these interviews are really conducting.
Modelling Questions: The Part You Cannot bluff
These arrive with a shared editor or a whiteboard. The interviewer is watching whether you reach for states and invariants before endpoints.
-- "Model partial shipment and partial invoicing."
-- The schema is easy; the questions behind it are the interview.
order_line (
order_line_id BIGINT PRIMARY KEY,
sku TEXT NOT NULL,
qty_ordered NUMERIC NOT NULL CHECK (qty_ordered > 0),
qty_shipped NUMERIC NOT NULL DEFAULT 0
CHECK (qty_shipped <= qty_ordered),
qty_invoiced NUMERIC NOT NULL DEFAULT 0
CHECK (qty_invoiced <= qty_shipped), -- ask before you assume:
-- does this business ever invoice BEFORE shipping (advance bill)?
unit_price NUMERIC NOT NULL,
tax_rate NUMERIC NOT NULL
);
-- Interviewer's follow-up: which document owns the truth?
-- Answer: the shipment does. The invoice follows what moved, not what was ordered.
-- Second follow-up: what happens when the customer returns 3 of the 10 shipped?
-- Answer: a credit note referencing the invoice line -- never an UPDATE on it.
Notice the two ask before you assume moments. Advance billing, bill-and-ship, and drop-shipment all exist in Indian commerce, and a candidate who states their constraint as universal invites the counterexample. Saying “this holds unless you invoice ahead of shipping — do you?” is the single most reliable way to signal that you have done this before. Related traps: money stored as floats (never — minor units only), business dates taken from server timezones (ask for the customer’s business day), and statuses stored as booleans instead of a state machine with permitted transitions.
Integration Questions That Come Up Every Time
“The ERP is down for four hours. What does your service do?” Queue the work, retry with backoff, keep serving reads from a local copy, mark records as pending sync, and reconcile when it returns — never block the customer-facing path on a partner’s availability.
“Your webhook arrives twice with the same event. What breaks?” Everything you did not make idempotent. Strong answers name the mechanism: an idempotency key derived from the provider’s event ID, a unique constraint that makes the second insert fail, and a handler that treats “already processed” as success.
“How do you update master data safely?” One direction of truth, soft deletes rather than hard ones, effective-dated changes where the business cares about history, and a reconciliation report rather than an assumption of perfect sync. This question is where ERP-experienced candidates pull ahead of product-only candidates — and where our domain expertise guide shows the study path for people who have not had that exposure yet.
What Actually Happens at Work: The Interview That Reversed
A Pune manufacturing-SaaS panel interviewed a developer with four years of generic full-stack work and no ERP background. The coding round went well. In the design round he was asked to model stock movements, and he drew a single stock_qty column and updated it on every event. He was three minutes from rejection.
Then he stopped and asked a question instead of defending the design: “Does stock ever get blocked — quality hold, or reserved for a customer who has not paid?” The panelling lead said yes to both. He redrew it as a state machine over quantities — on hand, blocked, reserved, allocated, in transit — and the next twenty minutes were the strongest part of his loop, because the panel could now teach him the remaining rules and watch how quickly he absorbed them. He was hired at ₹18 LPA, above the band they had opened with, on the strength of that recovery.
The reverse also happens, and it is worth hearing. Another candidate claimed ERP knowledge, listed SAP on the CV and then could not say what a movement type does when asked directly. The claim collapsed the credibility of everything else they said, and the loop ended early. Interviewers forgive missing knowledge; they do not forgive invented experience, because the job is built on knowing which facts are true.
How to Prepare in Four Weeks
- Week 1: pick your domain flow and write the walkthrough by hand. One page: order-to-invoice, encounter-to-claim or payment-to-settlement. Revise it until the partials and reversals are in it unprompted.
- Week 2: build the schema and the state machine. Constraints, statuses, transitions, and a written note on which document owns the truth in each dispute.
- Week 3: integration drills. Duplicate webhooks, partner outages, master-data sync. Implement one idempotent handler for real — you will be asked to describe it.
- Week 4: rehearse out loud with a practitioner. Twenty minutes with anyone who has worked in that business will find more gaps than ten mock interviews. Then run the behavioural answers: one story each about a wrong rule, a stakeholder disagreement and a production incident with business impact.
One honest warning: you cannot memorise your way through the walkthrough round. If you have no domain experience, the route in is the capstone project and the specific story of what you got wrong while building it — the same conversion path set out in the domain full stack developer career guide. Panels in this market can hear recited vocabulary in under a minute.
Training Resources
SkilBrill Domain Full Stack Developer Training drills exactly these rounds: order-to-cash, payment and refund lifecycles, healthcare and ERP modelling, integrations with retries and idempotency, plus interview practice where you defend your capstone model to someone playing the finance or operations stakeholder.
FAQ
What questions are asked in a domain full stack developer interview?
Four blocks: standard coding, full-stack system design, domain modelling (states, documents, invariants) and walkthroughs such as how an order becomes an invoice or a payment becomes a settlement, plus behavioural questions about rules you got wrong in production.
How do you answer “walk me through how an order becomes an invoice”?
Follow the documents, not the happy path: confirm the order, allocate stock, ship, invoice from what actually moved with tax determined per line, then settle and reconcile — and name the partials (partial shipment, short close, return) with their credit notes before the interviewer has to ask.
Do domain questions matter more than coding rounds in India?
Coding still gates you through the first round in most Indian loops, but the domain round decides the level and the offer. Strong coding gets you considered; a defensible domain model gets you the senior band.
How do I answer domain questions if I have no domain experience?
Use a project you actually built and be precise about its limits: describe the model, then say which rules you assumed and where you would need a practitioner. Claiming experience you do not have ends the interview quickly.
Which domain flow should I prepare for interviews?
Prepare the one your target employers run — but order-to-cash is the safest default, because it appears in ERP, e-commerce and fintech loops alike. The ranking in our best domains guide shows where the interviews are concentrated in India.
