Backend Engineering
Design the services, data and business rules that make software dependable behind the interface.
Career landscape
This is not a ranking of the ‘best’ career. Explore which problems, pressures and responsibilities can hold your curiosity.
01 · Build Software
Build, test and improve products and the systems behind them.
Design the services, data and business rules that make software dependable behind the interface.
Turn product intent into fast, accessible and resilient interfaces people can actually use.
Build apps that remain useful on real phones: small screens, unreliable networks, limited battery and interrupted sessions.
Help a team understand product risk and prevent defects. Explore behavior, challenge requirements and automate useful checks—not just click through screens or count bugs.
02 · Work With Data
Make data reliable, useful and available.
Build reliable pipelines and data models so analysts, products and ML systems can trust their inputs.
Turn messy questions and trustworthy data into decisions, metrics and explanations—not merely attractive dashboards.
03 · Build Intelligence
Design and evaluate learning systems.
Turn data and models into evaluated, monitored systems that improve a real decision or product.
Build dependable product features around existing AI models, with retrieval, evaluation, cost, latency and safety treated as engineering constraints.
04 · Protect Systems
Understand threats and reduce real risk.
Reduce risk by understanding systems, finding weaknesses and helping people respond responsibly.
Turn logs, alerts and reports into evidence-led detection and response—without declaring every anomaly an attack.
Help teams design, build and verify software that resists abuse—inside an authorized scope and without becoming the release police.
Test an explicitly authorized system like a careful engineer: define scope, validate weaknesses, limit impact and make the fix actionable.
05 · Run Systems
Make delivery and operations dependable.
Help teams ship safely and keep services observable, reliable and recoverable.
Design, connect and troubleshoot the networks people and services depend on. This is not just configuring a router—or the same job as cybersecurity.
06 · Work Close to Hardware
Design electronic systems and connect software to the physical world.
Write software that interacts with sensors, devices and strict timing or resource constraints.
Design and verify electronic systems: logic, components, schematics and boards. Embedded engineering focuses more on software controlling devices; hardware is not simply computer repair.
07 · Understand Computing Deeply
Study the ideas and systems beneath tools.
Investigate how computing works, prove or measure ideas, and improve the foundations others build on.
08 · Technology + People
Connect technical work, decisions and teams.
Connect user understanding and interface implementation. UX/product design studies the problem; UI engineering turns tested interactions into accessible software.
Connect technical reality, user problems and team decisions without pretending one person knows everything.
Try this instead
Comparison gives you language. Experiments give you evidence. No quiz gives you a final identity.