About Full Stack Developer interviews in India
Indian tech interviews typically run across multiple rounds — a technical screen, one or two deep-dive rounds, a system/design or practical round, and an HR and managerial discussion. Interviewers care as much about how you reason as the final answer, so think aloud, state assumptions, and use real examples from your own work.
🎯 Interview Success Tips
STAR MethodSituation → Task → Action → Result. Use for every behavioural question. Quantify the Result.
Research FirstRead company news, LinkedIn page, Glassdoor reviews and the interviewer's profile before the interview.
Salary TipNever give a number first. Ask: "What is the budgeted range for this role?" — always.
Virtual InterviewsTest camera + mic 30 min before. Good lighting, neutral background. Join 5 min early.
🔧 Technical Questions
Technical Question 1
How does a request travel from the browser to the database and back?
💡 How to answer: DNS → load balancer → web server → application/API → database, then response back through the stack. Mention caching layers, CDNs, and where you'd optimise. Shows end-to-end understanding.
Technical Question 2
How do you decide what logic belongs on the frontend vs backend?
💡 How to answer: Never trust the client — validation, auth, and business rules belong on the backend. Frontend handles UX, presentation, and optimistic updates. Sensitive logic and secrets stay server-side.
Technical Question 3
Explain REST API design and status codes you commonly use.
💡 How to answer: Resource-based URLs, HTTP verbs, and meaningful codes: 200 OK, 201 Created, 400 Bad Request, 401/403 auth, 404 Not Found, 429 Rate Limited, 500 Server Error. Consistency matters.
Technical Question 4
What is CORS and why does it block requests?
💡 How to answer: Cross-Origin Resource Sharing — the browser blocks requests to a different origin unless the server returns the right Access-Control headers. Fix it on the server, not by disabling browser security.
Technical Question 5
How do you implement authentication across frontend and backend?
💡 How to answer: Backend issues a JWT or session on login; frontend stores it (httpOnly cookie preferred over localStorage for XSS safety) and sends it with each request. Backend validates and enforces RBAC.
Technical Question 6
What database would you choose for a new app and why?
💡 How to answer: Depends on data shape and access patterns — Postgres for relational/transactional, MongoDB for flexible documents, Redis for caching. Justify with the actual requirements, not preference.
Technical Question 7
How do you handle state management in a React app?
💡 How to answer: Local state with useState, shared state with Context or a store (Redux/Zustand), and server state with React Query/SWR. Avoid putting server data in global client state.
Technical Question 8
How do you secure a full-stack web application?
💡 How to answer: HTTPS everywhere, input validation and parameterised queries (prevent SQL injection), escape output (prevent XSS), CSRF tokens, rate limiting, secure auth, and never expose secrets to the client.
Technical Question 9
Explain server-side rendering vs client-side rendering.
💡 How to answer: SSR renders HTML on the server (better SEO and first paint — Next.js). CSR renders in the browser (richer interactivity, heavier initial load). Many apps use a hybrid with hydration.
Technical Question 10
How do you optimise application performance end to end?
💡 How to answer: Frontend: code-split, lazy-load, optimise assets. Backend: cache, index queries, use a CDN. Measure first with Lighthouse and APM, then fix the actual bottleneck.
🧠 Behavioural Questions
Behavioural Question 1
Tell me about a full-stack feature you built end to end.
💡 How to answer: Use STAR. Cover the user need, your data model, API, UI, testing, deployment, and the measurable outcome. Highlight tradeoffs you made under time pressure.
Behavioural Question 2
How do you keep both frontend and backend skills sharp?
💡 How to answer: Show deliberate practice — side projects, reading both frontend and backend changelogs, and learning depth in one area while staying broad. Honesty about your stronger side is fine.
💡 Situational Questions
Situational Question 1
A bug spans frontend and backend and each team blames the other. How do you resolve it?
💡 How to answer: Trace the request end to end with logs, reproduce, and isolate where data first goes wrong. Lead with facts not blame, and fix the layer that's actually responsible.
Situational Question 2
You're the only developer and the deadline is tight. How do you prioritise?
💡 How to answer: Ship the core user value first, use proven libraries over building from scratch, cut non-essential scope, communicate tradeoffs, and avoid shortcuts on security and data integrity.
Situational Question 3
Production is down and you can't tell if it's frontend, API, or DB. Where do you start?
💡 How to answer: Check status dashboards and error rates per layer, confirm the DB and API health first (frontend depends on them), roll back the last deploy, then narrow down with logs.
💰 Salary Questions
Salary Question 1
What salary are you expecting as a full-stack developer?
💡 How to answer: Anchor on market: fresher ₹5–10 LPA, mid ₹12–25 LPA, senior ₹30 LPA+ in India. Full-stack breadth is leverage — ask for the band first.
Salary Question 2
Your expectation is above our range. Can you adjust?
💡 How to answer: Quantify the value of covering both ends (fewer hires needed), cite market data, and if base is fixed negotiate ESOPs, learning budget, or an early review.
🎤 Ask Interviewer Questions
Ask Interviewer Question 1
What does the tech stack look like and how is the codebase structured?
💡 How to answer: Reveals whether it's clean and modern or legacy you'll be maintaining.
Ask Interviewer Question 2
How small or large is the team, and who owns what?
💡 How to answer: Tells you how much breadth you'll really need and how you'll grow.
Ask Interviewer Question 3
What is the deployment and testing workflow?
💡 How to answer: Shows engineering maturity — CI/CD and tests, or manual deploys and firefighting.