Skip to content
Ameen Abozaid
BEG-004

Introduction to engineering

  • 5 Lessons
  • 91 min of reading
  • 1 h practice (estimate)
On this page 8 topics

Overview

Topics

  • Developer vs software engineer
  • frontend vs backend vs full-stack
  • QA, DevOps, SRE, architect
  • how teams collaborate

Learn first

91 min of reading · 1 h of practice (estimate)

Learning outcomes

  1. Explain how a software engineer's responsibilities extend beyond writing code (design, testing, operation, collaboration).
  2. Describe the roles of frontend, backend, full-stack, QA, DevOps, SRE, and architect, and how they hand off work.
  3. Describe the path this curriculum follows from Beginner to Solution Architect and what each level adds.

Lessons

  1. 01Developer vs software engineer17 min read
  2. 02Roles in an engineering team18 min read
  3. 03How a feature travels from idea to production20 min read
  4. 04Your career map: the eight levels of this course17 min read
  5. 05Demo: a day in a backend engineer's workflow, walked through19 min read

Lab and exercises

Lab

BEG-004-LAB1 · Read job posts

Outcomes: 1, 2, 3 · Time: ~1 h Collect three real junior backend job posts. List the required skills and map each to a module in this curriculum. Acceptance: a mapping table with at least 15 skills.

Exercises

IDOutcomeTask
BEG-004-EX011List four tasks an engineer does besides writing code.
BEG-004-EX021Why is readable code more valuable than clever code? One sentence.
BEG-004-EX032Match each role to its job: frontend, backend, QA, DevOps, SRE, architect.
BEG-004-EX042Who hands work to whom when a feature is released? Draw the hand-offs.
BEG-004-EX053Name the eight levels of this curriculum in order.
BEG-004-EX063Pick the level you want to reach and write two sentences on what it adds.
Show solutions
  • EX01 Design, testing, code review, fixing production issues, talking to teammates.
  • EX02 Code is read far more often than written, so teammates must be able to understand it.
  • EX03 Frontend: what users see. Backend: hidden service and data. QA: finds bugs. DevOps: automates build and release. SRE: keeps production reliable. Architect: how big pieces fit.
  • EX04 Design → code → review → test → release → operate.
  • EX05 Beginner, Junior, Mid, Senior C, Senior B, Senior A, Staff, Solution Architect.
  • EX06 Any reasoned answer that matches the level descriptions in the README.

Quiz

Outcomes: O1 engineering beyond code · O2 roles · O3 career map.

A self-check for you: nothing is graded, saved or sent anywhere. Choose an answer, then check it. You can try again as often as you like.

  1. 1Which is part of engineering besides coding?O1
  2. 2Code is read:O1
  3. 3Why do teammates review code?O1
  4. 4Who builds what the user sees on screen?O2
  5. 5Who keeps the production system reliable?O2
  6. 6Who finds bugs by testing the software?O2
  7. 7A full-stack engineer works on:O2
  8. 8How many levels does this curriculum have?O3
  9. 9The last level is:O3
  10. 10True about seniority:O3

Practical part

A short written reflection: which role interests you and what it requires (about 150 words). Pass: names the role, two responsibilities, and two skills to learn.

Common mistakes

Assuming seniority means only deeper technical knowledge; ignoring operation and collaboration.

Assessment

Short written reflection: which role interests you and what it requires.

Career relevance

Sets expectations; revisited in MID-065 and STF-001.

Type to search levels, phases, modules and lessons.