For engineering leaders
Know who is ready before production finds out.
Hiring and on-call planning both depend on knowing who can handle an outage. Shakeride puts each engineer through one and shows you how they did.
The problem, in plain terms
- A CV and a certification do not tell you who will act well when the site is down.
- After an incident, you know who was on shift. You still do not know who else on the team would have handled it, or handled it faster.
- Money spent on training comes back as a certificate. It does not come back as a number you can put in front of a board.
A person decides
A report informs a decision about a person. It does not make it.
Shakeride reports are evidence for the people who hire, promote or coach. Scores come from code, and any written interpretation is labelled as model-generated. Whether a person is hired, assigned or advanced is a decision that stays with a human, in the spirit of Article 22 of the GDPR, and the engineer can read the same report you do.
What you get
- A dashboard for the whole team
- One view of where every engineer stands, so you can answer that question in a meeting.
- Strengths and gaps, by kind of failure
- The same person handles a routing problem well and a data problem poorly. The dashboard says which.
- Progress across months, not one ride
- One score is an afternoon. Six months of scores is a direction, and you can see it.
- The engineer sees the same numbers you do
- Nothing is hidden from the person the ride is about. That is what makes the number worth having.
- Where practice would move the needle
- The dashboard points at the two or three failure shapes each engineer would benefit most from practising next.
- How your team compares to others
- The same rides are run everywhere, so a score means the same thing across companies.
How teams use it
Before a big migration
Find the weak spots on the team while there is still time to close them, and while doing so is cheap.
Before someone goes on call
Know what that person will actually meet at three in the morning, and whether they will be fine.
During the hiring process
Confirm in a working environment what the interview could only hint at.
Before a launch
Rehearse the outage on your terms, rather than meeting one on launch day.
How this differs from what you already buy
- Certifications
- Check what an engineer has learned, on paper.
- Guided labs
- Check that an engineer can follow a sequence of instructions.
- Shakeride
- Checks how an engineer acts when nobody hands them the instructions, and the clock is running.
See it against your own team
Thirty minutes with one of our engineers. We pick a ride that resembles what your team actually runs, and show you the kind of report you would get for each person.