For students and early-career professionals

Platform Engineer

Builds the internal developer platform other engineers use to ship safely.

14 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

Platform engineering

Find where developers get stuck and design an easier path

What you'll learn

  • Platform as product
  • Paved road
  • Delivery metrics
  • Developer experience

Practice

  • Write a service catalogue entry another team can rely on20 min
  • Spot the Friction Points in a Developer Onboarding Flow15 min

Chapter 4

Containers

Package an app to run the same on another machine

What you'll learn

  • Container image
  • Stateless processes
  • Desired state
  • Service exposure
  • Tenant separation
  • Reusable chart

Practice

  • Read a Dockerfile and Explain What Each Line Does15 min

Chapter 4

Cloud platforms

Read a cloud bill and find which services cost most

What you'll learn

  • Core cloud services
  • Identity and permissions
  • Service tradeoffs
  • Cloud cost drivers
  • Well-Architected review

Practice

  • Find 3 wasted cloud resources from a sample bill20 min

Chapter 5

Infrastructure as code

Read server-building code and find where the real setup differs

What you'll learn

  • Desired state
  • Plan diff
  • State file
  • Module boundary
  • Configuration drift

Practice

  • Read a Terraform Config and Describe What It Builds15 min

Chapter 7

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 Conflict in a Shell Script20 min

Chapter 7

Automated releases

Explain what each automatic check on a code change catches

What you'll learn

  • CI and CD
  • Pipeline stages
  • Release gate
  • Pipeline logs
  • Pull or push
  • Reconciliation loop
  • Where the check runs
  • Environments and promotion

Practice

  • Read a Failed Pipeline Log and Find What Broke It15 min

8 more in the plan

LinuxManage files and who can open them using short commandsCh 4

What you'll learn

  • Filesystem map
  • File permissions
  • Pipes and filters
  • Process signals

Practice

  • Solve 5 Linux command-line puzzles25 min
ScriptingWrite a script that checks disk space and warns youCh 7

What you'll learn

  • Script arguments
  • Error handling
  • Input checks
  • Readable scripts

Practice

  • Write a Script That Checks Disk Space and Warns You20 min
Automation mindsetPitch automating a repetitive task, naming its benefit and limitsCh 8

What you'll learn

  • Toil test
  • Automation value
  • Safe defaults
  • Maintenance cost

Practice

  • Pitch an Automation Idea for a Repetitive Process30 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
Problem solvingTest each possible cause of a problem instead of guessingCh 9

What you'll learn

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

Practice

  • Separate the Problem from the Symptom10 min
Critical thinkingSpot a weak assumption and ask where numbers come fromCh 9

What you'll learn

  • The hidden assumption
  • Argue the other side
  • The base rate
  • Fact vs inference
  • Wanting it to be true
CommunicationRewrite an update for two different readers, cutting extra linesCh 10

What you'll learn

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

Practice

  • Write a Six-Line Delay Message10 min
Working with othersContribute to group work, ask for help and credit teammatesCh 10

What you'll learn

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

Practice

  • Write a Request That Makes It Easy to Say Yes10 min

Your plan

Chapter by chapter.

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

1~2 wks

See the work of a Platform engineer

StartFree
2~2 wks

Build a platform other teams want

Skills
3~2 wks

Build a cloud environment from code

Project
4~2 wks

Run apps in containers on the cloud

Skills
5~2 wks

Define infrastructure in code

Skills
61–2 wks

Talk to two working platform engineers

People
7~2 wks

Automate how code gets shipped

Skills
8~2 wks

Automate the tasks you repeat by hand

Skills
9~2 wks

Find the cause before you fix it

Skills
10~2 wks

Make yourself understood across a team

Skills
11~2 wks

Capstone: build a small internal developer platform

Project
121–2 wks

Answer the questions interviewers ask

Interview
131–2 wks

Decide how you will get in

Decide
14on your timeline

Send your first applications

Apply

The job

What a Platform Engineer does

Builds and runs an internal developer platform (IDP) so other engineers can deploy, scale, and watch their services without rebuilding infrastructure each time. Treats those engineers as customers and the platform as a product.

The work

  • Build self-service tooling and templates that let engineers deploy without deep infrastructure knowledge
  • Create paved roads, the recommended easy path teams follow by default
  • Write infrastructure as code (IaC) so environments are repeatable and version controlled
  • Set up shared continuous integration and continuous delivery (CI/CD) pipelines teams reuse across services
  • Run an internal developer portal so engineers find, request, and track resources
  • Add guardrails for security, cost, and reliability into the platform itself
  • Gather feedback from engineer customers and turn it into platform improvements
  • Document golden paths so new teams onboard and ship quickly

A typical day

  1. Review platform requests and triage bugs reported by engineer customers
  2. Build or improve a template, pipeline stage, or self-service workflow
  3. Pair with a product team to unblock a tricky deployment or scaling issue
  4. Test platform changes in staging, then roll out behind a safe flag
  5. Update the developer portal, docs, and runbooks so others stay self-sufficient
  6. Plan the platform roadmap and prioritize work by engineer demand

Tools

Containers: Docker, KubernetesInfrastructure as code: Terraform, PulumiCI CD: GitHub Actions, GitLab CI, Argo CDDeveloper portals: Backstage, PortCloud platforms: AWS, Microsoft Azure, Google CloudObservability: Prometheus, Grafana, OpenTelemetryScripting: Python, Go, BashVersion control: Git

Ways in

There is more than one route.

Ways to study

  • Bachelor degree in computer science, software engineering, or information systems
  • Diploma or certificate in cloud computing, DevOps, or systems administration
  • Cloud or platform engineering bootcamp with hands-on labs and a portfolio
  • Self-study path using online courses plus home lab and open-source practice

How people get their first job

  • Start as software engineer and volunteer to own builds, deployments, and tooling
  • Move from DevOps, cloud, or site reliability work into platform-focused tasks
  • Apply for platform or developer experience internships at larger engineering teams
  • Earn an entry cloud certification and build self-service tooling in a home lab
  • Contribute to open-source platform tools like Backstage or Terraform modules

How the work is changing

What AI is doing to this role

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

Build self-service tooling and portals

Sped up a lot

What AI does

AI scaffolds Backstage and Port plugins and portal wiring in hours.

Still yours

You shape what engineers actually need and trust.

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 Platform Engineer?

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

Grow in the role →

Other roles in IT & Cloud Infrastructure

Questions

Questions about this plan

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

The plan is 14 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 information systems, diploma or certificate in cloud computing, DevOps, or systems administration, cloud or platform engineering bootcamp with hands-on labs and a portfolio, or self-study path using online courses plus home lab and open-source practice.

What is free?

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

Start the Platform 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