For students and early-career professionals

Software Engineer

Builds and maintains software applications or services that solve user problems.

13 chapters · About 5–6 months · 15–30 min a day

Start this plan free →

Chapter 1 is free.

Skills

14 skills, and what you'll learn in each

Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.

Core to the job

Chapter 2

Programming languages

Build small programs in one language, handling input and errors

What you'll learn

  • Types and values
  • Control flow
  • Error handling
  • Asynchronous work

Practice

  • Trace a Function and Predict Its Output10 min

Chapter 3

Writing tests

Write tests for small functions, including odd and wrong inputs

What you'll learn

  • Testing pyramid
  • Behaviour test
  • Test isolation
  • Regression test

Practice

  • Write a Basic Unit Test15 min
  • Find what a generated test suite gets wrong15 min
  • Write the test brief before an AI tool writes the tests25 min

Chapter 3

Code quality

Review code for unclear names, then tidy a messy function

What you'll learn

  • Clear names
  • Single responsibility
  • Review the risk
  • Explain the reason
  • Proportionate change

Practice

  • Read an AI-drafted change in code you have not seen25 min

Chapter 3

Git

Save clear changes to a project's history and request review

What you'll learn

  • Change states
  • Short-lived branches
  • Merge conflict
  • Useful commit message
  • Pull request review

Practice

  • Untangle a Merge Conflict20 min

Chapter 5

System design basics

Sketch a simple web app and explain how data flows

What you'll learn

  • System boundary
  • Synchronous and async
  • Cache trade-off
  • Failure mode
  • Browser and server
  • Vertical slice

Practice

  • Sketch the Parts of a Simple Web App15 min
  • Design a URL shortener system30 min

Chapter 7

Databases and SQL

Write SQL to filter and join data, and design tables

What you'll learn

  • Tables and relationships
  • Joins and groups
  • Index trade-offs
  • Query plan
  • Lock behaviour

Practice

  • Write 4 SQL queries against a sample schema20 min
  • Diagnose a slow database query20 min

8 more in the plan

Reading codeExplain unfamiliar code and predict what a function outputsCh 2

What you'll learn

  • Feature entry point
  • Call chain
  • Reference search
  • Code reading notes

Practice

  • Read 100 lines of unfamiliar code30 min
APIsCheck requests and replies between programs, and design clear onesCh 5

What you'll learn

  • API resource
  • HTTP status codes
  • API contract
  • Idempotent request
  • API style choice

Practice

  • Design REST endpoints for a notes app20 min
Secure codingFind risks in a login process and remove exposed passwordsCh 7

What you'll learn

  • Trust boundaries
  • Access control
  • Secret handling
  • Dependency risk

Practice

  • Spot the Security Mistake10 min
  • Trace a login flow end to end20 min
Problem solvingTest each possible cause of a problem instead of guessingCh 8

What you'll learn

  • Problem vs symptom
  • Clean problem splits
  • Root cause
  • Deciding under uncertainty

Practice

  • Separate the Problem from the Symptom10 min
Adapting to changeTry a new tool and describe how you handled changeCh 8

What you'll learn

  • Change vs your response
  • The messy in-between
  • Not there yet
  • Real change vs a feeling
DebuggingUse error messages to find bugs and explain your fixesCh 8

What you'll learn

  • Hypothesis before keyboard
  • Reliable reproduction
  • Root cause, not symptom
  • Narrow it down
  • Reading a stack trace

Practice

  • Find the Bug Using an Error Message10 min
  • Read a stack trace and find the real error15 min
  • Check the fix an AI assistant suggested for a crash15 min
CommunicationRewrite an update for two different readers, cutting extra linesCh 9

What you'll learn

  • Lead with the point
  • Match detail to the reader
  • Said versus heard
  • Specific feedback

Practice

  • Write a Status Update for a Non-Tech Manager10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 9

What you'll learn

  • Early team friction
  • Clear ownership
  • Challenge ideas, not people
  • Lead or follow

Your plan

Chapter by chapter.

13 chapters, in this order. Chapter 1 is free.

1~2 wks

See the work of a Software Engineer

StartFree
2~2 wks

Write code inside an existing codebase

Skills
3~2 wks

Write tested, reviewed code under version control

Skills
4~2 wks

Write up a system you built

Project
5~2 wks

Design systems that connect through APIs

Skills
61–2 wks

Talk to two working software engineers

People
7~2 wks

Store and query data securely

Skills
8~2 wks

Find the real cause of a bug

Skills
9~2 wks

Make yourself understood across a team

Skills
10~2 wks

Capstone: build a link shortener with rate limiting

Project
111–2 wks

Answer the questions interviewers ask

Interview
121–2 wks

Decide how you will get in

Decide
13on your timeline

Send your first applications

Apply

The job

What a Software Engineer does

Designs, builds, tests, and improves software so people and organizations can solve tasks faster and more reliably.

The work

  • Design software features based on user needs and technical constraints
  • Write and review code to build apps, APIs, and background services
  • Test, debug, and fix issues found in development and production
  • Work with product and design to clarify requirements and tradeoffs
  • Improve performance, reliability, and security of existing systems
  • Automate repetitive tasks like builds, deployments, and monitoring
  • Document decisions and keep codebases maintainable for the team

A typical day

  1. Check messages, dashboards, and bug reports to spot urgent issues
  2. Plan work in a short team sync, then focus on coding blocks
  3. Pair or review code, then update tests and documentation
  4. Investigate a tricky bug, reproduce it, and ship a safe fix
  5. Share progress and risks, then adjust plans as requirements change

Tools

Programming languages: Python, Java, JavaScript, C#Version control: GitIssue tracking: Jira, GitHub IssuesCI and CD: GitHub Actions, GitLab CIContainers: DockerDatabases: SQLCloud platforms: AWS, Azure, Google CloudMonitoring: Grafana, Prometheus

Ways in

There is more than one route.

Ways to study

  • Bachelor degree in computer science, software engineering, or related field
  • Diploma or certificate in programming or IT with strong project work
  • Coding bootcamp focused on web or backend development
  • Apprenticeship or employer training program with mentored delivery work

How people get their first job

  • Build a small portfolio with 2 to 4 deployed projects and clear README files
  • Apply for internships or trainee programs that include code reviews and testing
  • Contribute small fixes to open source projects to learn team workflows
  • Start in QA or IT support and move into automation and scripting tasks
  • Earn a practical certificate in cloud or programming fundamentals and ship projects

How the work is changing

What AI is doing to this role

How AI is changing this role · one of 6 tasks we track

Debug failures and fix defects

Sped up a lot

What AI does

AI reads the stack trace and proposes a fix in seconds.

Still yours

Root cause judgement on complex systems stays with you.

Reviewed September 2026

In the app · Premium

The rest is in the app

  • How AI affects the other 5 tasks
  • Whether this job is growing or shrinking
  • How hard the first job is to get
  • Similar roles that are easier to get into
  • Updated every month, with sources
See it in the app →

How we rate a job →

Already working

Already a Software Engineer?

Plan your move to Senior Software Engineer: 12 chapters that end with a strong case for your next review.

Grow in the role →

Other roles in Software Development

Questions

Questions about this plan

How long does it take to become a software engineer with Welica?

The plan is 13 chapters, 5–6 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.

Do I need a degree?

Not always. Common routes are bachelor degree in computer science, software engineering, or related field, diploma or certificate in programming or IT with strong project work, coding bootcamp focused on web or backend development, or apprenticeship or employer training program with mentored delivery work.

What is free?

Chapter 1, See the work of a Software Engineer, is free for good. Premium unlocks the rest of the plan.

Start the Software Engineer plan.

Chapter 1 free. About 15 to 30 minutes a day.

Start on web Continue your session Download for MacMac Get the iPhone appiPhone Get it on Google PlayAndroid