Full-Stack Developer
Full-stack developers communicate with more people than any other role — designers, backend specialists, DevOps engineers, PMs, and QA. This demands rapid vocabulary and register switching: you talk about "component rehydration" with the frontend team at 10 AM, discuss "sharding strategy" with the DBA at noon, and explain "deployment risk" to a PM at 3 PM. This path builds the linguistic flexibility to switch contexts fluently — same developer, different English for each conversation.
Topics covered
- API contracts
- Monorepo tools
- SSR vs. CSR
- Cross-layer debugging
- Full-stack architecture
Vocabulary spotlight
4 terms every Full-Stack Developer should know in English:
A formal agreement about data shapes and endpoints between frontend and backend teams
"We should define the API contract before both teams start building."
Code that can run in both browser and Node.js environments
"This validation logic needs to be isomorphic for SSR to work."
Sequential fetches where each depends on the result of the previous one
"We eliminated waterfall requests by parallelising the data loaders."
To place related code (component + styles + tests) together in the same directory
"We colocate tests with the components they cover."
📚 Vocabulary Reference
Key terms organised by category for Full-Stack Developers:
Cross-Stack Concepts
Client / Server Boundary
Frontend (brief)
Backend (brief)
Collaboration Vocabulary
Recommended exercises
Real-world scenarios you'll practise
- Discussing SSR vs CSR trade-offs with a tech lead
- Writing an RFC for a new API contract
- Explaining a cross-layer bug in a post-mortem
- Presenting a monorepo migration plan to the team
- Discussing API design with the backend team: "Does this endpoint exist?", "What does the response schema look like?"
- Explaining a bug that crosses layers: "The frontend is sending the correct payload but the backend is rejecting it with a 422"
- Estimating a full-stack ticket: "The UI will take maybe 3 days, the backend endpoint half a day, but I need to coordinate with DevOps on the environment setup"
- Presenting a feature in sprint review — covering both the UX change and the technical implementation without losing either audience
- Onboarding a new team member — explaining the project's full architecture in plain English
🎯 Interview questions specific to this role
Practise answering these questions out loud — or in writing. Each question targets a real interviewer concern for Full-Stack Developers.
- How do you decide what logic belongs on the client vs. the server?
- Walk me through a full-stack feature you built from scratch.
- How do you handle authentication across the frontend and backend?
- What does your local development workflow look like?
- Tell me about a time a frontend bug turned out to be a backend issue (or vice versa).
Recommended reading
Reference glossaries for Full-Stack Developers
Deep-dive glossaries covering terminology specific to this role: