All roadmaps

Full Stack Developer

One request, traced end to end - and you built every hop.

The complete full-stack path: web fundamentals, frontend with React, Node APIs, SQL and NoSQL databases, auth, security, testing, deployment and system-design basics - with free resources at every step.

Your progress0/56 topics · 0%

Progress is saved in this browser.

9 stages56 topics₹0 to follow

Filled nodes are the focus for this track; outlined ones can wait. Tap a topic to open it and mark it done, learning or skipped.

Full Stack Developer in 2026Related roadmapsFrontend roadmapBackend roadmapNode.js roadmapSystem Design roadmapProve it as you goReading is half of it. This roadmap isbacked by a free, scored Full StackDeveloper certification with a publicverification link and a Full-StackEngineer job simulation on real tickets -evidence a recruiter can check, not aclaim. Mark topics done, learning orskipped as you go; your progress carriesinto the classic view.Get certified - freeJob simulationClassic viewKnow the job before the toolsThe Full Stack Developer job in2026Which skills to learnFrontend plusbackendData, auth anddeployAI-assisted shippingWhich role to prepare forFull stack vsspecialistFresher vsswitcherSectors, cities and payWhat companies expectThe hiring barWhat interviewstestProof they verifyWhat gets you hiredA 90-day planProjects thatget readCertification and proofKnow what actually happensbetween browser and server.Web FundamentalsHTTP, DNS & the requestlifecycleHTML & CSS working knowledgeGit & GitHubOne language, both sides of thewire - typed.JavaScript & TypeScriptJavaScript coreAsync patternsTypeScript essentialsShip the screens users touch.Frontend with ReactComponents, props & stateRouting & layoutsTalking to your APIForms & validationDesign and build the API yourfrontend calls.Backend with NodeNode.js runtimeExpress fundamentalsREST API designAuthenticationFile uploads & backgroundjobsPersist data you can query withconfidence.DatabasesRelational modelling & SQLIndexes & query performanceMongoDB & document modellingORMs & migrationsCaching with RedisShip code you'd let strangersattack.Security & QualityOWASP top risksCORS & headersTesting the stackEnv & configPut the whole stack on theinternet, safely.Deploy & OperateDeploymentDocker basicsCI/CDLogs & debugging productionConvert skills into offers.Interview ReadySystem design, junioreditionDSA warm-upProve itFresher or experienced?Both tracks hold every topic. On the Fresher track thefoundations are filled and the later stages are outlined - dothem when a project needs them. On the Experienced track thefoundations are outlined and the later stages are filled. The2026 section at the top applies to both.Prefer a list?The classic view shows the same 8 stages as a sequentialchecklist with time estimates. Your marks are shared betweenthe two views.Open the classic view

Everything on this roadmap

Every stage and topic on the map, in reading order. Click any topic to open it.

2.Know what actually happens between browser and server.

3.One language, both sides of the wire - typed.

7.Ship code you'd let strangers attack.

8.Put the whole stack on the internet, safely.

The Full Stack Developer roadmap, topic by topic

Every topic on the map in reading order, with what to learn and the resources we recommend. Main topics are open; open any subtopic to read it. Select a topic name to open it in the topic panel, where you can track your progress.

  1. 1. Know the job before the tools

    The Full Stack Developer job in 2026

    2026

    Full stack is the title most companies actually hire for: one engineer who can build the interface, the API and the database behind it, deploy the lot and keep it running. In 2026 the job widened again, because AI tools draft the boilerplate on both ends and employers expect the one person to ship a whole feature with them. These four nodes answer which skills to learn, which role to prepare for, what companies expect and what gets you hired, with figures from the Stack Overflow 2025 survey, GitHub's Octoverse 2025, HackerRank's 2025 Developer Skills Report, the Work Trend Index and India's Naukri JobSpeak.

    Which skills to learn

    One language across the stack is the 2026 default: TypeScript on the front with React and Next.js, TypeScript or Python on the back with Node or a Python framework, Postgres underneath, and the glue - authentication, payments, email, storage, deployment - from managed services. The Stack Overflow 2025 survey has Node.js at 49 percent and React at 44 percent of developers, PostgreSQL at 58 percent as the most used database, and Octoverse 2025 crowns TypeScript the most used language on GitHub. The sub-nodes split the front, the back and the AI-assisted way of shipping both.

    Frontend plus backend

    The front half is the Frontend roadmap compressed: HTML, CSS, JavaScript as a language, then TypeScript and React with Next.js. The back half is a server that exposes an API, talks to a database and handles authentication: Node with Express or Nest, or Python with FastAPI or Django, on Postgres. The Stack Overflow 2025 survey puts Node.js at 49 percent, React at 44 percent and PostgreSQL at 58 percent of developers - the stack the AI builders and most job descriptions assume. Learn one of each layer deeply rather than three of each shallowly; the second framework is a weekend once the first is understood.

    Data, auth and deploy

    What makes a full stack developer useful is the glue most tutorials skip: data modelling and migrations, authentication and sessions done with a provider rather than by hand, file storage, background jobs, email, payments, environment variables and secrets, deployment on Vercel or a container, logging and error tracking. The Postman 2025 State of the API report found 83 percent of organisations working API-first, so the contract between your front and back ends - typed, documented, versioned - is a skill employers name. Ship one application with all of these once and every later project is faster.

    AI-assisted shipping

    AI

    In 2026 a full stack developer with an agentic coding tool ships what a small team shipped in 2023, and employers price that in. GitHub reports 80 percent of new developers use Copilot within their first week; the Stack Overflow 2025 survey finds 80 percent of developers using AI tools, 52 percent reporting a productivity gain and 46 percent distrusting the output. The skill is the loop the AI Engineer roadmap teaches: specify the feature and its tests, let the agent draft across the stack, read the diff, run it, own it. Candidates who can show that loop on a real repository are hired over those who can only paste.

    Which role to prepare for

    Full stack developer is the single most common developer type in the Stack Overflow 2025 survey, and in India it is the title startups, agencies and global capability centres post most. The sub-nodes compare it with specialising, lay out the fresher and switcher routes, and say where the demand and the pay are by sector and city.

    Full stack vs specialist

    Full stack pays for breadth: you are hired to own features, which startups, agencies and most mid-sized companies need from everyone. Specialists - frontend, backend, data, infrastructure - are hired by larger product companies with teams per layer, and their ladders go deeper. The Stack Overflow 2025 survey's most common role is full stack, and the common career shape is full stack first, then a specialism chosen from the layer you enjoyed and the market you want. Neither is a lesser path; the mistake is calling yourself full stack with no deployed proof of both halves.

    Fresher vs switcher

    A fresher should build one complete application before applying anywhere, because the title is judged on proof: HackerRank's 2025 report found junior hiring lagging as companies prioritise experienced talent, with 74 percent of developers saying landing a job is a struggle. A switcher from support, QA, data or operations should build in their old domain, where the requirements are already in their head. On this map, freshers get the foundations filled and the later stages outlined; experienced learners get the reverse. Naukri's JobSpeak reported fresher hiring up 17 percent year on year in February 2026, so the door is open to those with evidence.

    Sectors, cities and pay

    Startups, SaaS companies, e-commerce, fintech and the global capability centres doing product work from India hire the most full stack developers; Nasscom's 2026 strategic review puts the industry at 315 billion dollars with 59.5 lakh employees, and Indian hiring analyses through 2026 list full stack developers with AI integration skills among the most demanded roles. Bengaluru, Hyderabad, Pune, Chennai and Gurugram lead; remote roles for foreign companies pay in dollars and ask for TypeScript, communication and ownership. Pay tracks proof of shipping, not years.

    What companies expect

    Companies expect a full stack engineer to own a feature end to end: the schema, the API, the interface, the tests, the deployment and the monitoring, with AI tools used and reviewed. HackerRank's 2025 report says practical, real-world assessments are now standard and that 66 percent of developers prefer them. The sub-nodes cover the bar, the interview and what gets verified.

    The hiring bar

    The bar is ownership: given a feature, you design the data, build the API and the interface, write the tests that matter, deploy it, watch it and fix it. The Work Trend Index found 71 percent of leaders would rather hire a less experienced candidate with AI skills than a more experienced one without, and that is how full stack hiring reads in 2026: the tools let one person own more, and the interview checks that you can. Clean commits, environment handling, error states and a monitoring tab are what separates a shipped feature from a demo.

    What interviews test

    Expect a take-home or live build of a small end-to-end feature, questions on data modelling, API design, authentication and the React rendering model, a system design conversation sized to the company, and a walkthrough of your deployed project. HackerRank's 2025 report says real-world coding assessments are now the standard; large product companies still add an algorithms round. Explaining why you chose Postgres over a document store, or a server component over a client one, is worth more than any single answer.

    Proof they verify

    Hiring teams open the live URL, read the repository and check the credential. A full application with sign-in, a database and one real integration beats five tutorial clones; a readable readme with the decisions beats a long one; OneRoadmap's free Full Stack certification with its public verification link beats a platform badge. Show the AI workflow too: a short note on what the tools drafted and what you changed is now part of the proof.

    What gets you hired

    A deployed application with a database, authentication and one real integration, a readable repository, a verified certification and a clear account of how AI tools were used - that is the full stack hiring packet in 2026. The sub-nodes give the ninety-day plan, the projects that get read and the proof that counts.

    A 90-day plan

    Month one: the frontend fundamentals and one deployed interface. Month two: a Node or Python API on Postgres with authentication, connected to that interface, deployed. Month three: one real integration - payments, email, a third-party API - plus tests, error tracking, a readme with the decisions, the Full Stack certification and twenty targeted applications a week. Use an agentic coding tool from month two onward and keep a log of what it drafted and what you fixed; that log is interview material.

    Projects that get read

    Projects that get read are complete: a booking or inventory app with roles and permissions; a marketplace with search, payments and email; an internal tool for a real small business you know. Each has a live link, sign-in, a database, one integration, tests on the critical path and a readme. The World Economic Forum's Future of Jobs 2025 report names software and application developers among the fastest-growing roles and says 39 percent of skills will change by 2030; a project built on the 2026 stack with AI tools, and explained, is the evidence that you keep up.

    Certification and proof

    Proof is verifiable: OneRoadmap's free Full Stack certification with a public link, a GitHub profile with real commit history, a deployed application and a written account of your AI tool workflow. With more than 180 million developers on GitHub and India the largest source of new ones in Octoverse 2025, a profile is only as good as what a reviewer can check in a minute - make that minute count.

  2. 2. Know what actually happens between browser and server.

    Web Fundamentals

    Know what actually happens between browser and server.

    Time: about 1-2 weeks. Topics: HTTP, DNS & the request lifecycle · HTML & CSS working knowledge · Git & GitHub.

    HTTP, DNS & the request lifecycle

    Optional on the Experienced track

    URL to response: DNS, TCP/TLS, request/response anatomy, status codes and cookies - the vocabulary of every debugging session.

    HTML & CSS working knowledge

    Optional on the Experienced track

    Semantic structure, Flexbox and Grid - every full-stack feature still ends at a screen someone has to use.

    Git & GitHub

    Optional on the Experienced track

    Branches, PRs and review flow - the collaboration substrate for literally everything that follows.

  3. 3. One language, both sides of the wire - typed.

    JavaScript & TypeScript

    One language, both sides of the wire - typed.

    Time: about 3-4 weeks. Topics: JavaScript core · Async patterns · TypeScript essentials.

    JavaScript core

    Optional on the Experienced track

    Closures, prototypes, this and the event loop - the depth that separates users of frameworks from engineers.

    Async patterns

    Optional on the Experienced track

    Promises, async/await, error propagation and parallelism with Promise.all - backend code is async code.

    TypeScript essentials

    Optional on the Experienced track

    Interfaces, unions, generics and strict mode - shared types between client and server are full-stack's superpower.

  4. 4. Ship the screens users touch.

    Frontend with React

    Ship the screens users touch.

    Time: about 3-4 weeks. Topics: Components, props & state · Routing & layouts · Talking to your API · Forms & validation.

    Components, props & state

    Composition, controlled forms and lifting state - thinking in React rather than fighting it.

    Routing & layouts

    Multi-page apps with React Router or Next.js: params, nested layouts, redirects and protected routes.

    Talking to your API

    fetch/React Query patterns: caching, loading and error states, optimistic updates and auth headers.

    Forms & validation

    Client-side validation that mirrors server rules - one schema, two enforcement points.

  5. 5. Design and build the API your frontend calls.

    Backend with Node

    Design and build the API your frontend calls.

    Time: about 4-5 weeks. Topics: Node.js runtime · Express fundamentals · REST API design · Authentication · File uploads & background jobs.

    Build: REST API with auth. A documented CRUD API with registration, login, protected routes and validation - tested with an HTTP client.

    Node.js runtime

    Event loop, modules and npm - why Node handles thousands of concurrent connections on one thread, and when it can't.

    Express fundamentals

    Routing, middleware chains, request validation and centralised error handling as one coherent pipeline.

    REST API design

    Resources, verbs, status codes, pagination and versioning - APIs another developer can guess correctly.

    Authentication

    Password hashing with bcrypt, sessions vs JWTs, refresh flows and protecting routes - without inventing your own crypto.

    File uploads & background jobs

    Multipart handling, object storage and queues at concept level - the features that separate CRUD demos from products.

  6. 6. Persist data you can query with confidence.

    Databases

    Persist data you can query with confidence.

    Time: about 3-4 weeks. Topics: Relational modelling & SQL · Indexes & query performance · MongoDB & document modelling · ORMs & migrations · Caching with Redis.

    Relational modelling & SQL

    Tables, keys, normalisation and joins with Postgres - relational literacy is a career-long asset.

    Indexes & query performance

    Why one query is instant and another isn't: indexes, EXPLAIN and the N+1 problem.

    MongoDB & document modelling

    Documents, embedding vs referencing and aggregation pipelines - and honest criteria for choosing documents over tables.

    ORMs & migrations

    Prisma/Mongoose for productivity, migrations for schema history, and the escape hatch to raw queries.

    Caching with Redis

    Cache-aside for hot reads, TTLs and invalidation - the first tool you reach for when the DB gets hot.

  7. 7. Ship code you'd let strangers attack.

    Security & Quality

    Ship code you'd let strangers attack.

    Time: about 2-3 weeks. Topics: OWASP top risks · CORS & headers · Testing the stack · Env & config.

    OWASP top risks

    Injection, XSS, CSRF, broken auth and misconfiguration - recognising the classic holes before attackers do.

    CORS & headers

    Same-origin policy, CORS configuration and security headers - the browser-side contract of your API.

    Testing the stack

    Unit tests for logic, integration tests for APIs (supertest), one E2E happy path - confidence to refactor.

    Env & config

    Secrets, env vars and the twelve-factor mindset that keeps dev, staging and production sane.

  8. 8. Put the whole stack on the internet, safely.

    Deploy & Operate

    Put the whole stack on the internet, safely.

    Time: about 2-3 weeks. Topics: Deployment · Docker basics · CI/CD · Logs & debugging production.

    Build: Full-stack capstone. A deployed app with auth, database, and one non-trivial feature (payments, uploads or realtime) - README and CI included.

    Deployment

    Optional on the Fresher track

    Frontend to a CDN, API to a host (Render/Fly/Railway/VPS), managed Postgres, custom domain and HTTPS.

    Docker basics

    Optional on the Fresher track

    Dockerfiles and Compose - the same app everywhere, and the lingua franca of modern deployment.

    CI/CD

    Optional on the Fresher track

    GitHub Actions running tests on every PR and deploying on merge - shipping as a routine, not an event.

    Logs & debugging production

    Optional on the Fresher track

    Structured logs, health checks and reading a stack trace under pressure - the on-call survival kit.

  9. 9. Convert skills into offers.

    Interview Ready

    Convert skills into offers.

    Time: about 2 weeks. Topics: System design, junior edition · DSA warm-up · Prove it.

    System design, junior edition

    Explaining your own app's architecture: request flow, data model, caching and how you'd scale it 10×.

    DSA warm-up

    Arrays, hashmaps, strings and two-pointer problems - the screening bar most product companies still use.

    Prove it

    Take the OneRoadmap Full Stack certification so the resume line is verifiable, not just claimable.

Prove it as you go

Reading is half of it. This roadmap is backed by a free, scored Full Stack Developer certification with a public verification link and a Full-Stack Engineer job simulation on real tickets - evidence a recruiter can check, not a claim. Mark topics done, learning or skipped as you go; your progress carries into the classic view.

Fresher or experienced?

Both tracks hold every topic. On the Fresher track the foundations are filled and the later stages are outlined - do them when a project needs them. On the Experienced track the foundations are outlined and the later stages are filled. The 2026 section at the top applies to both.

Prefer a list?

The classic view shows the same 8 stages as a sequential checklist with time estimates. Your marks are shared between the two views.

Frequently asked questions

What does a full stack developer actually do?

A full stack developer owns a feature end to end: the data model, the API, the interface, the tests, the deployment and the monitoring. In small companies and startups it is the most common engineering title because one person can ship a whole feature; in 2026, with agentic coding tools drafting both ends, that one person ships what a small team used to.

Is full stack a real specialism or a jack of all trades?

It is a real job with a real ladder, judged on ownership rather than depth in one layer. The common career shape is full stack first, then a specialism chosen from the layer you enjoyed - frontend, backend, data, infrastructure - if a larger company's structure calls for it. The mistake is calling yourself full stack with no deployed proof of both halves.

Which stack should I learn?

One language across the stack is the 2026 default: TypeScript with React and Next.js on the front, TypeScript on Node or Python on the back, Postgres underneath, and managed services for authentication, payments, email and storage. It is the stack the Stack Overflow survey shows most developers using and the one AI builders and most job descriptions assume.

Do I need to learn DevOps too?

Enough to deploy and keep your own service running: a container, a pipeline, environment variables and secrets, logs, error tracking and backups. Vercel and the managed platforms do most of it for a first job. Kubernetes, infrastructure as code and on-call are the DevOps roadmap's territory; learn them when a role asks.

How long does it take to become job-ready?

It depends on where you start and nobody can promise a timeline. A beginner usually needs several months of steady work to reach a complete deployed application with a database, authentication and one real integration; a developer with one half already needs weeks for the other. The proof - a live app, a readable repository, a verified certification - matters more than the months.

Should I use AI tools to build my portfolio projects?

Yes, and say so. Employers expect agentic coding tools used well; what they test is whether you can explain, review and fix what the tool produced. Keep a short note in each readme on what was generated and what you changed, and never ship a line that touches data, money or authentication that you did not read.

Will AI replace full stack developers?

The tools have raised what one developer can ship and lowered the price of boilerplate. What they have not replaced is ownership: deciding the data model, the contract between front and back, what to test, how it fails, and taking responsibility for the release. Full stack is the role that owns all of that, which is why demand for people who can direct the tools has grown.

How do I prove full stack skills without job experience?

One complete application beats five tutorial clones: sign-in, a database, one real integration such as payments or email, tests on the critical path, deployment, a readme with the decisions and a note on your AI workflow. Add a scored certification with a public verification link and a GitHub profile with real commit history, and a reviewer can check all of it in a minute.