Who it’s for
Most engineers only get to practice judgment when the decision is already real.
A production issue is happening. A deadline is at risk. A senior engineer disagrees with you. You have to decide whether to take on technical debt, trust an AI-generated change, or push back on a direction the team is already moving toward.
Those moments are valuable learning experiences, but they are also high stakes.
Engineering GPS gives you a place to practice those decisions before the consequences are real.
You work through realistic engineering situations, make the call in your own words, have one part of your reasoning challenged, rethink the decision, and leave with feedback on how you approached it.
No score. No perfect answer. Just deliberate practice for engineering judgment.
The same judgment challenges can help different engineers in different ways.
Early in your engineering career
Practice difficult engineering decisions before you are the one carrying the risk.
Growing toward senior
Prepare for the judgment that matters more as your responsibilities grow.
Already experienced
Step into situations you may not encounter often in your current role.
AI is making implementation faster.
That does not remove the need for engineers. It changes where more of their value comes from.
Engineers still have to decide what to build, what to trust, where to accept risk, which trade-offs are worth making, when to challenge an approach, and when something that technically works still should not ship.
Those decisions are difficult to learn from a course or a framework alone.
Judgment develops through exposure to situations, making decisions, seeing what you missed, and trying again.
Engineering GPS is built to give you more of those repetitions.
You are given a realistic engineering situation with enough context to make the decision.
You explain what you would do in your own words.
The mentor does not immediately tell you whether you are right or wrong. Instead, it challenges one important part of your reasoning.
You respond again.
Then you see what your reasoning shows: what was strong, what changed, what you may have missed, and one principle you can reuse in future decisions.
Then you can try another situation.
Engineering GPS is not trying to replace the tools you already use to work on your code.
For deliberate practice, you should not need to upload your architecture, explain months of technical debt, connect your repository or recreate your company context.
The situation gives you the context you need. That means you can focus on the part you are actually trying to develop:
The decision and the reasoning behind it.
Engineering judgment can show up in many forms.
You might have to decide whether to ship an AI-generated change you do not fully understand. You might have to choose between protecting quality and meeting a deadline. You might disagree with a more experienced engineer and need to decide whether to push back.
Over time, Engineering GPS can expose you to decisions involving architecture, technical debt, operational risk, AI, ownership, product thinking, stakeholder pressure, uncertainty and influence.
The goal is not to memorise the “right” answers. It is to become better at reasoning when there is no obvious one.
Situation Clinic · Beta
Practice is only one way to use Engineering GPS.
Sometimes you already have the situation. You are weighing a real trade-off, facing a difficult technical decision, or trying to work out how to respond to something happening in your team.
Bring a real situation where the answer isn’t obvious. The mentor won’t simply tell you what to do. It will challenge how you’re thinking about the decision, help you see the trade-offs, and work with you toward a decision you can explain and defend.
You don’t have to wait for the next production incident, architecture disagreement or difficult release decision to become better at engineering judgment.
Practice the decisions now. Make the call, get challenged, and try again.