Ce parcours n’est pas encore traduit en français : son contenu s’affiche en anglais.
Backend Developer
Build the server-side logic behind every app
Pas sûr(e) que ce soit pour vous ? Trouver ma voie →
0 missions sur 8 faites
Ce métier est-il fait pour vous ?
Deux minutes avant d’y consacrer des mois
Cochez ce qui vous ressemble
Cochez celles qui sont vraies pour vous.
Les compétences que vous en tirerez
Les emplois auxquels il mène
- Backend Developer
- API Engineer
- Server-side Engineer
- Platform Developer
Avant de commencer
- ✓ Basic programming knowledge helpful
- ✓ Comfort with the terminal
8 missions jusqu’à Backend Developer
4 mondes, 8 missions. Touchez un cercle pour l’ouvrir ; celui qui brille est le suivant.
Don't try to learn everything at once. Pick one language—Python, Node.js, Go, or Java—and deeply understand its server-side ecosystem and execution model.
Data is the core of backend engineering. You must learn how to structure, query, and scale data storage efficiently using both relational (SQL) and NoSQL paradigms.
Learn how to build secure, robust RESTful APIs that act as the middleman between the database and the frontend clients.
Localhost works, but real users are on the internet. Learn how to containerize apps, deploy them to virtual machines, and monitor them to catch errors.
En savoir plus sur ce métier
Le métier, le salaire là où vous vivez, les questions fréquentes, et où ce métier peut vous mener ensuite.
Le métier
Ce que vous feriez
- Build the overall technical structure of websites and web applications
- Write the supporting code that web applications run on
- Develop databases that support web applications
- Check code is valid, well structured and meets industry standards
- Test sites on a planned schedule and after every revision
- Analyse user needs to work out technical requirements
Où vous travailleriez
- Computer systems design firms (about 21% of US web developers)
- Self-employed (about 18% in the US)
- Information sector companies (about 11% in the US)
- Schools, colleges and universities (about 10% in the US)
- Management and technical consulting firms (about 6% in the US)
Toutes les étapes en détail
Le texte complet de chaque étape, à lire ou à imprimer. Avancez étape par étape dans le parcours ci-dessus.
Choose Your Language & Master It 1 étapes
Master Core Language Constructs
Before you write web servers, you need to be extremely fluent in your chosen language. Understand memory management, concurrency models, and how to structure a large codebase without relying on a framework.
Tâche concrète: Build a command-line interface (CLI) application that reads a large CSV file of user data, filters out invalid rows based on complex logic (e.g., date formats, missing fields), sorts the data, and writes the clean data to a new JSON file. Use native file streams to ensure it works even if the CSV is 5GB in size. Publish it locally.
Pourquoi c’est important: Frameworks come and go, but strong foundational knowledge of your language ensures you can debug deeply when the framework fails. Memory and stream management are critical for writing backend code that doesn't crash under load.
Liste de contrôle
- Understand basic syntax, data structures (Arrays, Maps, Sets), and control flow
- Learn object-oriented concepts (Classes, Interfaces, Inheritance) or functional equivalents
- Understand your language's concurrency model (Event Loop for Node, Goroutines for Go, Threading for Java/Python)
- Learn how to handle files, streams, and buffers natively
- Master your language's package manager (npm, pip, maven, go mod)
- Learn effective error handling (try/catch, panic/recover, or returning errors)
- Setup linters and formatters (ESLint, Prettier, Black, Gofmt)
Databases & Data Modeling 2 étapes
Master Relational Databases & SQL
SQL is the undisputed king of data storage. You need to understand how to design schemas that avoid duplication and how to write efficient queries that join multiple tables without locking the database.
Tâche concrète: Design the SQL schema for an e-commerce platform. Include tables for Users, Products, Categories, Orders, and OrderItems. Write a SQL script that creates these tables with proper foreign keys. Then, write a complex SELECT query that joins these tables to calculate the 'Total Revenue generated by a specific Category over the last 30 days'. Use EXPLAIN to see how the database executes it.
Pourquoi c’est important: Poor database design is the #1 cause of backend performance bottlenecks. If your database schemas are flawed, every API you write on top of them will be slow and hard to maintain.
Liste de contrôle
- Understand database normalization (1NF, 2NF, 3NF) and the rationale behind it
- Write basic CRUD operations: SELECT, INSERT, UPDATE, DELETE
- Master JOIN operations (INNER, LEFT, RIGHT, FULL OUTER)
- Understand and use constraints (PRIMARY KEY, FOREIGN KEY, UNIQUE, NOT NULL)
- Learn when and how to implement column indexing to speed up read queries
- Understand ACID properties (Atomicity, Consistency, Isolation, Durability) and database transactions
- Connect to a PostgreSQL or MySQL database from your primary programming language
Explore NoSQL & Caching
Relational databases cannot solve every problem. Learn document databases for unstructured data and in-memory stores for ultra-fast caching.
Tâche concrète: Build a simple caching layer. Write a script that simulates fetching an expensive dataset (e.g., weather data) which takes 3 seconds. Configure Redis so the first fetch hits the simulated API, but subsequent fetches within a 1-minute TTL read instantly from the Redis cache.
Pourquoi c’est important: Scaling backends to handle high traffic requires offloading repetitive, heavy queries from your primary database. Knowing Redis is standard baseline knowledge for intermediate-to-senior backend roles.
Liste de contrôle
- Understand the CAP theorem and the differences between SQL and NoSQL
- Set up MongoDB and learn how to model document-based data
- Implement basic CRUD using a driver (like Mongoose for Node.js or PyMongo)
- Set up Redis and understand its in-memory key-value architecture
- Use Redis to cache expensive database queries or store user sessions
APIs, Authentication & Frameworks 2 étapes
Build Robust RESTful APIs
An API is a contract. You need to understand HTTP verbs, status codes, and how to architect predictable, standard API endpoints using a web framework.
Tâche concrète: Build a REST API for a 'Task Management' app. It must have endpoints for creating, reading, updating, and deleting tasks. Add request validation (a task cannot have an empty title). Connect it to a real database using an ORM. Document every endpoint using a tool like Postman so someone else could integrate with it strictly by reading the docs.
Pourquoi c’est important: APIs are the product that backend developers build. If your APIs are confusing, slow, or constantly failing due to bad input, the frontend teams will be blocked, and the app will break.
Liste de contrôle
- Understand the anatomy of an HTTP request/response (Headers, Body, Verbs, Status Codes)
- Learn RESTful design conventions (e.g., GET /users, POST /users, DELETE /users/:id)
- Pick a backend framework (Express, Django, FastAPI, Spring Boot) and initialize a server
- Implement route controllers, middleware, and request validation
- Implement structured JSON error handling so frontend apps can easily parse errors
- Integrate an ORM/Query Builder (e.g., Prisma, SQLAlchemy, Hibernate) into your API
- Document your API endpoints using Swagger or Postman collections
Implement Security & Authentication
You can't trust the client. Backend servers are responsible for ensuring that users are who they say they are (Authentication) and that they can only access what they own (Authorization).
Tâche concrète: Add complete authentication to your Task Management API. Implement user registration (hashing passwords appropriately) and login (issuing a JWT). Use middleware to protect the Task routes so that User A can only see and edit their own tasks, but an 'Admin' user can view all tasks.
Pourquoi c’est important: Security flaws can destroy a company. If you accidentally allow an endpoint to dump the entire user database, or expose passwords, it's a catastrophic failure. Security must be built-in, not bolted on later.
Liste de contrôle
- Never store plain text passwords; learn how to securely hash and salt passwords using bcrypt/Argon2
- Implement stateless authentication using JSON Web Tokens (JWT)
- Understand stateful session-based authentication using cookies
- Implement Role-Based Access Control (RBAC) (e.g., Admin vs User routes)
- Understand standard web vulnerabilities listed in the OWASP Top 10 (SQL Injection, XSS, CSRF)
- Implement rate limiting to prevent brute-force attacks on your login endpoints
- Configure secure HTTP headers (CORS, Helmet)
DevOps, Deployment & Monitoring 3 étapes
Containerization with Docker
Docker ensures that if your code runs on your machine, it will run exactly the same way on a production server. It is industry standard.
Tâche concrète: Take the Task API you built in Phase 3. Write a Dockerfile for it. Then, write a `docker-compose.yml` that defines two services: your API and a PostgreSQL database. A new developer should be able to run `docker-compose up` and have the entire app and database running perfectly in under 1 minute.
Pourquoi c’est important: Without containers, setting up engineering environments and deploying code is a nightmare of differing OS versions and dependency conflicts. Docker solves 'it works on my machine'.
Liste de contrôle
- Understand virtualization vs. containerization
- Write a Dockerfile for your backend API (choose the correct base image, handle dependencies, expose ports)
- Build, run, and debug Docker containers locally
- Write a docker-compose.yml file to spin up your API and its associated Database simultaneously
- Understand Docker volumes to persist database data across container restarts
CI/CD & Cloud Deployment
Stop doing things manually. Learn to automate your deployments and host your applications on cloud infrastructure.
Tâche concrète: Rent a cheap VPS server ($5/mo). SSH into it, install Docker and Nginx. Pull your Dockerized Task API, run it, and configure Nginx to expose it to the internet securely via HTTPS. Finally, set up GitHub Actions so that when you push to the 'main' branch, it automatically runs an automated test suite before merging.
Pourquoi c’est important: Deploying code safely is a critical backend skill. Understanding the Linux environment and CI/CD pipelines bridges the gap between 'backend developer' and 'cloud/systems engineer'.
Liste de contrôle
- Learn basic Linux server administration (SSH, User management, cron tasks)
- Set up a VPS (Virtual Private Server) on AWS EC2, DigitalOcean, or Linode
- Configure a reverse proxy using Nginx to route traffic to your application
- Secure your domain with free SSL certificates via Let's Encrypt / Certbot
- Write a GitHub Action (CI) to run your automated tests on every pull request
- Understand basic deployment automation (CD)
Observability: Logs & Metrics
When your app goes live and inevitably crashes, how will you know why? Setting up logging and alerting gets you out of the dark.
Tâche concrète: Integrate Sentry (free tier) into your deployed API. Break an endpoint on purpose (e.g., throwing a hard runtime error). Check the Sentry dashboard to ensure the error is captured with the full stack trace and the specific user's request details. Then fix it.
Pourquoi c’est important: A backend developer operating without logs and metrics is flying blind. Professional engineers rely on dashboards and error alerting to proactively solve issues before customers complain.
Liste de contrôle
- Implement structured logging (JSON format) instead of simple console.logs
- Assign unique Request IDs to track a user's flow through the system
- Track critical metrics: Request rate, Error rate, and Response time (Latency)
- Set up central error tracking using a tool like Sentry or Datadog
- Ensure sensitive information (passwords, tokens) is stripped from logs
Questions fréquentes : Backend Developer
Des réponses claires sur la durée, les prérequis, les salaires et les méthodes d’étude.
Combien de temps faut-il pour devenir Backend Developer ?
Ce parcours estime 6–12 months. Il compte 4 phases et 8 étapes, de « Choose Your Language & Master It » à « DevOps, Deployment & Monitoring ».
Comment devenir Backend Developer ?
Suivez les 4 phases dans l’ordre, en commençant par la phase 1, « Choose Your Language & Master It ». Votre première tâche : Build a command-line interface (CLI) application that reads a large CSV file of user data, filters out invalid rows based on complex logic (e.g., date formats, missing fields), sorts the data, and writes the clean data…
Combien gagne un Backend Developer ?
Le salaire dépend du pays. L’encadré salaire de cette page indique l’estimation de DraftMyCareer, en monnaie locale, pour le pays choisi dans le menu.
De quoi ai-je besoin avant de commencer ?
Ce parcours indique : Basic programming knowledge helpful; Comfort with the terminal.
De quelles compétences un Backend Developer a-t-il besoin ?
Ce parcours couvre : A programming language, Databases, APIs, Server management, Security basics.
Changer de métier : passerelles vers ce poste et depuis ce poste
Voir toutes les reconversions →Évolutions et changements de poste possibles
- AI & ML Engineer
Backend developers already have the infrastructure and API skills that most AI prototypes lack, making them prime candidates for lucrative AI Systems Engineering roles.
⏱ 4–6 months🧭 ModerateCe que vous apprendriezPython & PyTorch / HuggingFace · Vector Databases (Pinecone, pgvector, Qdrant) · RAG Pipelines & LLM Orchestration (LangChain, LlamaIndex)
Voir le plan d’action
- Month 1: Python Data & LLM Foundations Master Python, NumPy, and call foundation model APIs (OpenAI, Anthropic) with streaming responses and structured JSON outputs.
- Month 2–3: Vector Embeddings & Production RAG Build high-throughput Retrieval-Augmented Generation (RAG) pipelines using pgvector or Qdrant with hybrid search and reranking.
- Month 4–5: Fine-Tuning & Model Evaluation Fine-tune open-weight models (Llama 3 / Mistral) with LoRA/QLoRA and build automated evaluation test suites.
- Month 6: High-Scale AI Microservices Deploy low-latency AI inference microservices with streaming endpoints, token caching, and rate limiting on cloud GPU clusters.
- DevOps Engineer
DevOps & Platform engineers are among the most sought-after tech specialists with high job security and remote leverage.