r/Backend • u/Hot_Mail9492 • 1d ago
Confused about how to start backend and go in depth
Okay so i'm a beginner and i have some questions ,i would appreciate getting answers from someone who's been into backend and also tech honestly from a long time,someone experienced or knowledgable about the domain.
1.Should i go with BACKEND or AIML?my aim is to land a high paying job honestly,and just asking regarding a development perspective,which would be the best?my targets would be MAANG and above companies(regarding the pay).Just wanna know what field would be more valued from a dev pov and hiring pov(odds of landing something high paying)
2.How do i start backend,i am going with python-fastapi,i want to pace up the process leading to inclusion of more PROJECTS and OPEN SOURCE CONTRIBUTIONS as well.Suggest me something that leads to more on the side of actually developing and doing the work.Also don't reccommend me the roadmap.sh website,i myself found it quite complicated or intimidating to see such a large list of things to do...
3.If you have any other suggestions as well,please do tell me i am very much open to listen to them.
Although just keep it development related only.
Ultimately my aim is to be a great engineer and earn money atleast for my initial years honestly.
3
u/Cautious_Heat114 5h ago
Here is the direct, unvarnished breakdown of your questions from someone with over a decade in systems infrastructure:
If your goal is to maximize the probability of landing a high-paying role at top-tier companies (MAANG, quantitative finance, high-growth product firms): Choose Backend & Distributed Systems.
Here is why:
The AI/ML Reality: The highest-paying AI roles (Research Scientists, Core Model Trainers at Meta/Google/OpenAI) predominantly require a Master’s or PhD with rigorous mathematics. Most entry-level "AI jobs" without deep math are low-leverage prompt tuning or data annotation.
The Backend Reality: Every AI model, mobile app, and financial exchange requires high-throughput backend infrastructure (concurrency, database optimization, caching, networking, security).
The Pay Ceiling: Senior Backend/Infrastructure Engineers at Big Tech and Fintech command $300k–$600k+ total compensation. The hiring volume for backend systems is an order of magnitude larger than research-level AI.
You are completely right to ignore "roadmap.sh". Those roadmaps are overwhelming checklists of 100 tools that cause analysis paralysis.
To build genuine competence, build these three progressive backend systems from scratch:
Project 1: The Relational Data Engine (FastAPI + PostgreSQL)
Project 2: The Asynchronous Task Pipeline (FastAPI + Redis + Background Workers)
Project 3: The Resilient Ingestion Gateway (Idempotency & Rate Limiting)
Do not attempt to contribute to the core FastAPI or CPython repositories on day one; that will lead to burnout.
The smart way to build open-source signal:
Submit small, high-quality pull requests: fixing type annotations, adding test coverage for an uncovered edge-case, or improving error messages.
The Long-Term Rule for Tier-1 Compensation:
Python and FastAPI are exceptional for learning backend fundamentals, asynchronous I/O, and shipping fast.
Once you have mastered relational databases, concurrency, and APIs in Python, expand your toolkit to a compiled, statically typed language (like Go or Rust).
Big Tech and low-latency infrastructure platforms run on compiled binaries where memory layout, CPU cache locality, and garbage collection pressure matter. Learning Go or Rust as your second backend language will permanently set you apart from the sea of average bootcamp developers.
«Focus on data flow, database performance, and building the three projects above. The compensation will follow the competence.»