CloudShift — Experience the job before you get the job

Our mission ●

There's a gap between learning cloud and working in cloud.

CloudShift exists to bridge it.

Learning Cloud → Working in Cloud the part nobody prepares you for

You can pass the certification. You can finish the course. You can build the portfolio project. And then on your first morning someone drops a P1 into a queue you've never seen, an analyst pings you about an access denial, and a manager asks what your ETA is — all at the same time. None of that was on the exam.

We're preparing people for that transition. We are not claiming they've already made it.

Why we built it ●

A lab grades whether a resource exists. A job grades your judgment.

That's the difference we set out to close. Every ticket in CloudShift has a fast wrong answer that appears to work — and the simulator grades whether you took it.

The workday is the curriculum

Not services in isolation. Interruptions, priorities, SLAs, half-finished investigations and the person waiting on you.

Modelled on the real thing

Ticket mix, incident cadence and scoring weights come from published research on how cloud, DevOps and SRE engineers actually spend a day — not from our guesses.

Safe to be wrong

The cheapest place to learn that AdministratorAccess is not a fix is a simulation. The most expensive is production.

What we do ●

Every ticket hides a shortcut that looks like a solution.

Here's a real one from the library. An analyst can't read an S3 prefix. Two of these answers make the error message go away. Only one of them is the job.

OPS-4471 P3 Priya Raman · Developer

New analyst can't read the reporting bucket

Our new data analyst needs to read the quarterly exports in s3://cloudshift-reporting/exports/. She's getting AccessDenied on every object. She only needs read.

A Attach the AWS managed AmazonS3FullAccess policy to her user.

B Add s3:GetObject scoped to …/exports/* to her existing policy.

If you pick A

The analyst is unblocked in thirty seconds and writes back to say thank you. You also just gave her write and delete on every bucket in the account for a read request. Ade in Security blocks it at review.

Security −5 · the classic over-grant

Scorecard End of day

Both answers close the ticket. They do not score the same, because a real reviewer wouldn't treat them the same.

→ Correctness — did the error actually go away?

→ Security — weighted heaviest. Security skills appear in 87.6% of cloud job postings.

→ Investigation — did you look before you answered?

→ Communication — could Priya understand your reply?

If you pick B

One action, scoped to the one prefix she was actually asked about. Least privilege, which is what the person reviewing your work is looking for.

Security +5 · least privilege

This is the thing we care about most. Anyone can learn which button creates a bucket. What separates a junior engineer from a trusted one is knowing why the fast answer was the wrong one — and CloudShift is built to put you in front of that decision, over and over, before it counts.

A shift, start to finish ●

You clock in. The day happens to you.

Tickets arrive on a clock, not on a menu. Incidents are scheduled to land while you're already mid-task — because that's when they land in real life.

9:00 AM
Clock in to the queue

A morning's worth of tickets, mixed to match how the day is really spent — about a third of it operational toil.
9:20 AM
Investigate before you answer

A simulated shell with real command output, logs, policy documents and Terraform plans attached to the ticket.
10:45 AM
Ask a coworker

Five colleagues — a senior engineer, a manager, a developer, a security engineer and a PM — each of whom answers like their role would.
11:20 AM
P1 lands mid-task

46% of SREs handle five or more incidents a month. Yours arrives while you're halfway through something else, with an SLA running.
2:30 PM
Hand off cleanly

In team mode you share one queue with other engineers. Claim your tickets, and pass work over with enough context that someone can continue it.
5:00 PM
Performance review

Not a score out of ten. A written review of your correctness, security judgment, investigation habits and communication — the way a real one reads.

production-style tickets across 12 categories

difficulty tiers — junior, mid-level and senior

AI coworkers who answer in character

shared queue in team mode, with scored handoffs

The product ●

Built and running today.

These aren't mockups. This is the simulator as it stands — what we're getting ready to put in front of people.

A P1 ticket open in the CloudShift queue with attached evidence

A P1 arrives with logs and evidence attached — and an SLA counting down.

Feedback after choosing an over-permissive answer

Take the shortcut and the simulator tells you exactly what it cost you.

End of shift: a written performance review, not just a score.

In live mode you don't say what you'd do — you do it, and it grades the cloud state you left behind.

Where we draw the line ●

Being straight about the limits is part of the product.

Plenty of people will promise you a shortcut into this industry. We'd rather be the ones you can trust, so here is exactly what we do and don't claim.

What we say

✓Experience the job before you get the job.
✓Practice realistic engineering work in a safe environment.
✓Build confidence before your first day on the job.
✓Prepare for real engineering work through immersive simulations.

What we will never claim

✕That it replaces job experience.
✕That it's equivalent to working at a company like Amazon.
✕That it means you won't need a first job.
✕That it's the same as professional experience.

Our goal isn't to create fake experience. It's to create meaningful practice. Practice builds confidence; professional experience builds judgment over time. CloudShift helps you arrive at that first job better prepared to develop it.

Where employers fit

We never compete with employers — we support them. The outcome we want is companies saying “applicants who used CloudShift arrive more prepared,” never that they need fewer junior engineers. If we ever make that second sentence true, we've built the wrong thing.