Full Stack Developer Interview
Questions & Answers

Client: UI state, user interactions, presentation logic. Server: business rules, data validation, sensitive operations, anything touching a database or external API. Security is the hard line — never trust client-side validation alone. Performance is the nuance — server-side rendering for SEO-critical pages, client-side rendering for highly interactive dashboards. Default to server for anything that involves data access.

JWT or session-based auth with HttpOnly cookies (not localStorage — XSS accessible). Refresh token rotation. CSRF protection for state-changing endpoints. On the server, validate the token on every protected request — do not trust client state. Use an established auth library rather than rolling your own. Show you understand the OWASP Auth Cheat Sheet at a practical level.

Shared types package imported by both frontend and backend eliminates the most common source of client-server contract bugs. Turborepo or Nx for build orchestration and caching. Separate deployable units even if the code lives together. The key benefit of a monorepo is type-safe contracts and atomic commits across the stack — if you are not leveraging those, a monorepo is just overhead.

Interviewers want the diagnostic process: how you identified where the time was being spent (network tab, server logs, APM), what you found on each layer (N+1 query on the server, large uncompressed payload, blocking render on the client), and what you changed at each layer. Show you can profile end-to-end rather than assuming the bottleneck is one place.

Unit tests for business logic in isolation. Integration tests for the API layer that hit a real test database. E2E tests (Playwright/Cypress) for the critical user flows only — they are slow and brittle when overused. Contract tests if you have multiple consumers of the API. The right coverage depends on the feature risk — a payment flow gets more test coverage than a profile picture upload.

Structure your answer as a 60-second professional narrative: where you have been (your background), what you have done (your strongest achievement), and where you are going (why this role). Lead with your most relevant experience, not your entire career history. End with why you are excited about this specific opportunity.

Choose a genuine weakness that you have actively worked to improve. The structure is: name the weakness → show self-awareness of its impact → describe the concrete step you took to address it → show the improvement. Never say "I work too hard" — interviewers recognise this as evasion and it damages your credibility.

Use the STAR method (Situation, Task, Action, Result) but add a fifth element: what you learned. Choose a real failure, not a disguised success. Show you can take responsibility without making excuses, and demonstrate that the lesson changed your behaviour in a specific, verifiable way.

Be honest but constructive. Acceptable reasons: seeking greater scope, new challenge, skills you can not develop in the current role, or company-level changes (restructuring, direction shift). Never speak negatively about your current employer or manager — it signals you will do the same to the prospective employer in future conversations.

Describe the conflict specifically, show that you sought to understand the other person's perspective, and explain the resolution approach you took. Interviewers are assessing your emotional intelligence and whether you escalate or resolve. Avoid stories where you were right and they were wrong — choose a story where both parties grew.

Describe your specific prioritisation system: impact × urgency matrix, stakeholder alignment, or a specific tool or process you use. Then give an example where you applied it under real pressure. Show that your system is systematic rather than reactive, and that you communicate proactively when priorities change.

Choose an achievement that is specific, measurable, and relevant to the role. Lead with the result ("I reduced our error rate by 40% in 90 days"), then explain the context, challenge, and what you specifically did that drove the result. Show your ownership and impact, not just your team's work.

Be honest about your ambitions while showing that this role is a genuine step in that direction — not a stopgap. Hiring managers want to invest in people who will grow with the organisation. Show that your 5-year goal requires the specific skills and experience this role provides, making your ambition an asset for both sides.

Research before the interview and make the answer specific: cite their product, a recent company development, something about their culture or team, or a professional aspect of this particular role that matches your goals. Generic answers ("I love your values") signal you did not do the research. Specific answers signal genuine interest.

Always have 3–5 questions prepared. Ask about the biggest challenge in this role, what success looks like in the first 90 days, how the team operates, and the interviewer's own experience at the company. Never ask about salary, benefits, or holidays in a first interview. Questions show interest, strategic thinking, and that you care enough to have done research.