careers
DevOps / Platform Engineer
Make shipping software fast, repeatable and safe, for every team in the company.
A DevOps or platform engineer builds and runs the systems teams use to ship and operate software: pipelines, environments, clusters, observability and the tooling around them. Security is part of the job but not all of it. This knowledge base covers the delivery foundations and the security slice of the role; deeper operations and platform work is listed as outside it.
see this path on the journey mapA day in the job
- Build and maintain CI/CD, environments and the infrastructure behind them.
- Keep platforms reliable: monitoring, capacity, upgrades, on-call.
- Make the default path for developers fast and safe, and document it.
- Automate toil and standardize how services are built and deployed.
- Work with security so controls fit the platform instead of fighting it.
Stage 1· Foundations
Learn the foundations of delivery, identity, networking and logs.
Study here
- Linux and networking essentials
- Git workflows and code review
- Containers and images
- The delivery lifecycle
- CI/CD
- Network - segmentation and zero-trust
- IAM - identity and access
- Logging & detection - signals and alerts
Learn elsewhere
- Linux administration and shell scripting
- Git, branching and release workflows
- Containers and how they differ from VMs
Build this
Containerize a small app, write its pipeline and deploy it to a cloud VM you provisioned by script.
Stage 2· Practitioner
Describe infrastructure as code and run it safely.
Study here
- CI pipelines that stay fast
- Infrastructure as code
- Containers - images and supply chain
- Secure infrastructure as code
- CI/CD hardening
Learn elsewhere
- Terraform or Pulumi in depth, with remote state and modules
- Kubernetes fundamentals: workloads, services, config
- Monitoring and alerting stacks
Build this
Recreate the same environment from scratch with IaC in one command, and destroy it just as cleanly.
Stage 3· Advanced
Run reliable platforms at scale and treat them as products.
Study here
- Kubernetes fundamentals
- Release strategies and rollback
- Observability: metrics, logs and traces
- Reliability: SLOs, error budgets and incidents
- Kubernetes - secure runtime
- Reliability at scale: idempotency, retries and backpressure
- Observability of the security platform itself
- Security as an internal product
Learn elsewhere
- SRE practice: SLOs, error budgets, incident management
- Cost awareness (FinOps) and capacity planning
- Multi-environment and multi-region design
Build this
Define SLOs for a service, build the dashboards and alerts for them, and run a game day to test the runbook.
What to show
- An infrastructure repository that builds a complete environment from nothing, with documentation anyone can follow.
- A platform write-up: what you standardized, what you left flexible and how teams reacted.
- A post-incident review (real or simulated) with timeline, causes and the changes that followed.
Certifications (examples)
- CKA (CNCF)
- HashiCorp Terraform Associate
- AWS Certified DevOps Engineer – Professional
Examples, not endorsements or requirements. Check the issuer for current details.