Cloud engineering readiness
Real cloud rides. Real decisions. Real evidence of capability.
No AWS account required. No surprise cloud bill.
Certifications, quizzes and tutorials show that someone understands cloud concepts. They do not show what that person does when a release stops serving traffic at 14:00 on a Tuesday.
Shakeride puts them in the situation and watches what they do:
It tests capability in context.
01
The environment is already running and already broken.
02
Real tools, real logs, real metrics, real infrastructure.
03
Diagnose, remediate, recover — with no answer key.
04
Technical execution and operational judgement, separately.
05
Track readiness over time, not one result.
Every ride below is a real Shakeride environment. Nothing is a mock-up.
External researchers report that they can list and download files from a data store without any credentials. Public-access settings are inconsistent across the account, and a second store with a similar name exists. Identify the unintended exposure and close it.
5 min · level 1
The web application is unreachable. The platform reports no running copies of the service, and the traffic router marks every target unhealthy. The most recent release points at a build that was never published. The expected configuration is documented on the resources themselves. Restore service.
20 min · level 3
Traffic keeps going to the primary region even though the standby is healthy and should have taken over. Health checks and routing rules exist, but nothing shifts when the primary fails. A second, near-identical set of records exists. The operations team keeps the expected configuration on a dashboard. Restore automatic failover.
45 min · level 4
New orders stop flowing end to end: the intake queue grows, the order count stalls, and customer notifications never fire. Several workers and tables from earlier releases are still around. Every break in the path must be found — repairing three of the four changes nothing.
90 min · level 5
Two engineers can both restore the service. One took forty minutes and three risky actions to get there. The score says so.
Whether the system actually works again, verified by the environment itself.
How long until the actual cause was identified.
How long until service was restored for users.
Whether the steps taken risked data, availability or a wider outage.
Changes made that had no bearing on the problem.
Whether the cause was identified rather than the symptom suppressed.
These roll up into a readiness score as your history grows.
Individuals
Practice against real failures, measure your gaps, and come away with evidence of capability rather than a certificate of attendance.
Teams
Team readiness at a glance, a capability matrix by ride type, and benchmarking against comparable teams.
Partners
Add realistic practice and measurable outcomes to a programme that currently ends with a slide deck.
Free to explore. €19 per month for the full individual plan. Teams and partners are priced per agreement.
One ride. Twenty minutes. No account with a cloud provider needed.