The mentorship structure I implemented is what I call rotation-based ownership, where junior team members own a production system for two weeks at a time with a senior engineer available but deliberately not intervening unless asked.
Traditional mentorship in ops teams tends to follow a shadowing model. A junior person watches a senior person handle incidents, deployments, and decisions, and eventually gets handed small tasks. The problem I found with that approach at GpuPerHour is that shadowing teaches people what to do but not how to think through an unfamiliar problem. When the junior person finally faces something the senior person never demonstrated, they freeze.
The rotation structure works differently. Every two weeks, a junior team member becomes the primary owner of a specific system, for example the GPU allocation scheduler or the billing reconciliation pipeline. They handle all decisions, all incidents, all changes. The senior engineer assigned to them is available on a dedicated Slack channel, but the rule is that the junior person has to articulate what they think the right action is before asking for input. The senior engineer confirms, corrects, or expands, but never takes over.
The result after running this for about eight months is that junior engineers reach independent decision-making capacity roughly twice as fast as they did under the shadowing model. More importantly, they develop a habit of reasoning through problems out loud, which makes their thinking visible and coachable.
The key difference from traditional approaches is that the mentorship is not about transferring knowledge. It is about accelerating judgment. Knowledge can come from documentation. Judgment only comes from making real decisions with real consequences and having someone help you understand why your instinct was right or wrong.
Faiz Ahmed
Founder, GpuPerHour
