What Fullstack Engineers Do
What They Build
Collaborative Editor
Real-time document editing with blocks, databases, and sync.
Deploy Platform
Git-based deployments with serverless functions and edge runtime.
Issue Tracker
Fast, keyboard-driven project management with offline sync.
Internal Tools
Low-code platform for building internal applications.
When to Hire Fullstack vs. Specialists
Fullstack Works Best When:
- Small teams (< 10 engineers): Everyone needs to wear multiple hats
- Feature-focused work: End-to-end ownership reduces handoffs
- Rapid iteration: Context-switching costs less than communication overhead
- Startups and MVPs: Versatility over deep specialization
- Product engineering: Understanding full context matters
Specialists Work Best When:
- Complex frontend requirements: Advanced animations, accessibility, performance
- Scale challenges: Distributed systems, high-throughput backends
- Large teams: Specialization enables deeper expertise
- Platform work: Infrastructure, data engineering, security
- Distinct skill requirements: Very different frontend vs backend needs
The Fullstack Skill Tradeoff
Depth vs. Breadth
Fullstack engineers know more things less deeply than specialists:
| Area | Specialist | Fullstack |
|---|---|---|
| Frontend | Expert-level React, advanced CSS | Solid React, good CSS |
| Backend | Distributed systems, complex APIs | Standard APIs, basic scaling |
| Database | Query optimization, architecture | CRUD operations, basic optimization |
| DevOps | Infrastructure as code, Kubernetes | Basic Docker, deployment |
The hiring implication: Don't expect fullstack engineers to match specialists in any single area. Evaluate breadth and the ability to learn, not maximum depth.
Assessing Fullstack Skills
Technical Evaluation
Frontend Assessment (30-40%):
- Build a simple component
- Discuss state management approaches
- Basic CSS and responsive design
Backend Assessment (30-40%):
- Design a simple API
- Database schema discussion
- Authentication and basic security
Integration (20-30%):
- How would you connect frontend to backend?
- Discuss deployment and monitoring
- Error handling across the stack
Key Differentiators
Strong fullstack candidates:
- Can work in unfamiliar areas with minimal ramp-up
- Understand how frontend and backend interact
- Make pragmatic technology choices
- Own problems end-to-end
Weak fullstack candidates:
- Only comfortable on one side
- Can't explain the other side's constraints
- Struggle with context-switching
- Need handoffs for anything outside comfort zone
Fullstack Interview Questions
Cross-Stack Understanding
Q: "A user reports the page is slow. Walk me through how you'd diagnose it."
Good answer covers both sides:
- Network tab, load times (frontend)
- API response times (backend)
- Database query performance
- Caching opportunities
Red flag: Only investigates one side
Integration Skills
Q: "How would you implement user authentication for this application?"
Look for:
- Frontend: login forms, token storage, protected routes
- Backend: authentication endpoints, session management
- Security: HTTPS, password hashing, token security
Common Hiring Mistakes
1. Expecting Specialist Depth
Fullstack means breadth. If you need someone to optimize GraphQL at scale, hire a backend specialist. Fullstack engineers are generalists by design.
2. Testing Only One Side
If you only do frontend interviews, you'll hire frontend-leaning developers calling themselves fullstack. Test both sides appropriately.
3. Ignoring Integration Skills
The value of fullstack is seamless integration. Ask about connecting frontend to backend, debugging across the stack, and end-to-end feature ownership.
4. Conflating Junior and Fullstack
Junior developers often learn one stack first. True fullstack requires experience on both sides. Junior "fullstack" usually means "full-stack exposed" rather than "full-stack proficient."
Recruiter's Cheat Sheet
Resume Green Flags
- Projects showing both frontend and backend work
- End-to-end feature ownership mentioned
- Multiple languages/frameworks across the stack
- Experience with deployment and DevOps basics
- Product-focused companies in history
- Side projects demonstrating full-stack work
Resume Yellow Flags
- "Fullstack" title but only one-sided projects
- Heavy specialization in just one area
- No mention of database or API work
- Only large enterprise roles (often siloed)
Conversation Starters
- "Tell me about a feature you built from start to finish"
- "What's your typical frontend/backend split day-to-day?"
- "How do you decide where to put logic—frontend or backend?"
- "What do you enjoy more—frontend or backend?"
Technical Terms to Know
| Term | What It Means |
|---|---|
| Full-stack | Works across frontend (UI) and backend (server) |
| REST API | How frontend and backend communicate |
| ORM | Object-Relational Mapping—database abstraction |
| SSR | Server-Side Rendering—server generates HTML |
| SPA | Single-Page Application—client-side rendering |
| CRUD | Create, Read, Update, Delete—basic operations |
| API | Application Programming Interface—how frontend and backend communicate |
| Docker | Containerization platform for consistent deployments |