DevOps & Cloud Track
Infrastructure and platform roles
DevOps & Cloud Track
This track covers CI/CD, infrastructure as code, and container security so you can judge whether it fits the infrastructure and platform work you are aiming for. Read what each stage asks of you before you commit weeks to it.
Built for learners who already read a terminal without panic and want structured practice with pipelines, declarative infrastructure, and container isolation.
What this track is for
Platform and infrastructure teams hire for a specific habit: turning manual steps into repeatable, reviewable systems. This track builds that habit in order. You start with version control and a working shell, move into pipeline design and build automation, then write infrastructure as code that can be read, reviewed, and rolled back. Container security sits alongside the container work rather than after it, because image hygiene and runtime isolation only stick when you practise them while building.
It is not a certification course and it does not promise a title at the end. It is a structured sequence with labs you run yourself, so the fit question is honest: if you want guided practice with CI/CD and infrastructure as code and you are prepared to run the exercises, this track is aimed at you. If you want a lecture-only overview, the shorter modules below will cover the ground without the lab hours.
The four stages of the track
Each stage is a graded slab in the sequence. The label column tells you the job it does; the content column tells you what you actually practise and what you finish with.
Version control, shell, and Linux basics
Branching and merge practice on real repositories, file permissions, process inspection, package management, and reading logs under pressure. This is the floor everything else stands on, and it is the stage most learners underestimate.
CI/CD design and build automation
You write pipeline definitions from scratch: build, test, artifact, and deploy stages, environment variables and secrets handling, cache strategy, and failure diagnosis when a job breaks at 2am. The goal is a pipeline you could hand to a colleague and explain line by line.
Infrastructure as code and cloud provisioning
Declarative resource definitions, state and drift, modules and reuse, review workflow for infrastructure changes, and provisioning across a hybrid cloud footprint. You build and tear down environments rather than reading about them.
Container security and runtime practice
Image layering and minimal base images, registry hygiene, scanning as a pipeline gate, least-privilege runtime configuration, and separating build-time from run-time concerns. Container security is taught here as a set of decisions you make while writing the Dockerfile, not as a separate theory block.
How the labs run
Every stage ends in a lab you finish alone
Labs are written as short briefs with an expected outcome, not as guided walkthroughs. You get the environment and the requirement; you work out the commands, the pipeline definition, and the resource files. When something fails, you diagnose it against logs and state rather than a hint list.
That is deliberate. Platform interviews rarely ask you to recite a tool flag; they ask what you would check first when a deployment stalls. The lab format is built to leave you with that reflex.
Expect several hours per lab. Budget for them before you start the track rather than after.
Who this track suits, and who it does not
Honest fit matters more than a long feature list. These are the two profiles we see most often.
A good fit if you are
- Comfortable in a terminal and willing to read documentation without a summary
- Moving from support, systems administration, or a junior developer role toward platform work
- Able to give several focused hours a week across the full sequence
- Interested in how systems are built and repaired, not only how they are configured
Look elsewhere if you
- Want video lectures only, with no hands-on environment to run
- Are looking for a guaranteed job placement or a salary figure attached to the course
- Have not yet worked with files, processes, or a command line
- Need a self-paced course that finishes in a single weekend
What you will actually be able to do
By the end of the sequence you should be able to read an unfamiliar pipeline definition and explain what each stage does; write and review infrastructure as code for a small environment; diagnose why a build or deployment failed using logs and state; and argue for a specific container configuration on least-privilege grounds. Those four abilities are the ones platform teams test for in interviews, and each one has a lab behind it in this track.
Before you enrol
Three questions worth answering first
Choosing a track is mostly a scheduling decision. Answer these three honestly and the fit becomes obvious.
-
Time
Can you hold a steady weekly rhythm for the whole sequence, labs included? Stage three in particular does not compress well into scattered evenings.
-
Target role
Are you aiming at platform, infrastructure, or release engineering work? If the answer is application development, the AI & MLOps track may match better.
-
Starting point
Do you already work with a shell and version control? If not, take the foundations material first — it is included, and skipping it costs you later.
Questions we get about this track
If your question is not here, send it and we will answer plainly.
Ask a questionDo I need prior cloud experience to start?
No prior cloud account is required. Stage one covers the command line, version control, and Linux fundamentals, and stage two introduces pipelines on a local runner before anything is provisioned remotely. If you have never used a shell, start with the foundations material and give it real time.
Which tools does the track use?
You work with a pipeline runner, a declarative infrastructure tool, and container tooling for building and running images. The labs name the specific tools when you open them, so you can check the syllabus before you commit and confirm the stack matches what you already use or want to learn.
How much of the work is container security?
It runs through the container stage rather than sitting in one block. You cover image layering and minimal base images, registry hygiene, scanning as a gate in the pipeline, and least-privilege runtime settings. Because it is woven into the build work, you practise it while writing Dockerfiles rather than reading about it separately.
Does the track prepare me for a certification exam?
It is built around practical work rather than an exam blueprint, so it is not a substitute for a certification study plan. The labs do cover the day-to-day ground those exams test, but check the exam guide for the exact objective list if that is your goal.
How do I know the track fits before I pay?
Ask for the syllabus and read the stage breakdown above against the work you actually want. If your target is platform or infrastructure engineering and you can commit steady hours to the labs, the track is designed for you. If either of those is untrue, the comparison page will show you which track fits better.
Where this track sits in the catalog
The academy runs three tracks. This one is the infrastructure route; the other two cover different ground.
This track
DevOps & Cloud
CI/CD, infrastructure as code, container security, and hybrid cloud provisioning for platform and infrastructure roles.
You are hereRelated track
Cybersecurity
Defensive fundamentals, network and endpoint monitoring, and incident response practice for security operations roles.
View trackRelated track
AI & MLOps
Model development, evaluation, and deployment pipelines for teams putting machine learning into production.
View trackNot sure which route matches your background? The Course Tracks page lays the three side by side, and How Our Courses Are Built explains how the labs and stage sequence are put together.
Ready to read the full syllabus?
The syllabus lists every stage, the labs inside each one, and the tools you will use, so you can compare it against the role you are targeting before you commit. Ask us anything the page leaves open and we will answer with the specifics rather than a brochure.
Talk to the academy
- 452 Tech Plaza, Suite 300, San Francisco, CA 94105, USA
- +1-415-555-0192
- info@rob-inhood.digital
- Monday to Friday, 9:00 AM – 6:00 PM