A design review keeps circling back to the same objections.
- Bring
- The proposal, constraints, rejected options, and unresolved review comments.
- First useful step
- Identify the decision that is still open and what evidence would settle it.
Engineering mentoring gives you an experienced engineer to think through a design decision, promotion question, or difficult team situation with. Bring one problem you are facing at work; we will use it to decide what to work on next.
With Aleksandr Perederei, Principal Engineer and former CTO. Updated .
“I want to grow” can mean very different things. Choose the situation closest to yours. The first task is to understand what is getting in the way, before committing to a longer plan.
If you do not know what Staff means at your company, an external mentor cannot settle that question. Your manager needs to explain the expectations and whether there is an opportunity to take on that work. Otherwise, you can spend months preparing for a role that is not available.
Mentoring can help you prepare for that conversation. Ask: which expectation am I not meeting, what example would demonstrate it, and which project would let me try? Bring the answers back so we can work with your company’s actual criteria.
Build a promotion plan around the evidenceYou can use mentoring alongside those resources. The important part is knowing which question each person can answer.
Before building a learning plan, write down something you want to do differently at work. “Improve communication” is difficult to evaluate. “Write a proposal that lets the reviewers decide between two migration options” gives us something to examine.
After trying the next step, bring back the result: the review comments, the decision, or the question that is still unresolved. That feedback tells us whether to keep working on the same problem, change approach, or stop because you have what you need.
See a worked example of a mentoring sessionA few sentences are enough. Remove confidential details and share only material your employer permits you to disclose.
My background includes Principal Engineer work at Delivery Hero, Staff Engineer work at Tesla, and Engineering Manager and CTO roles. That experience shapes the questions I bring to a review: who needs to make the decision, what will be harder to operate, and can the team deliver it?
You can read that reasoning before booking. In Microservices Should Reduce Coordination, I discuss judging service boundaries by whether a team can ship independently. In Go Architecture: Start With Boundaries, I describe how an elaborate design got in the way of delivery. Both articles were adapted from my webinars.
Read my experience and backgroundEngineering mentoring is a working conversation with an experienced engineer about your decisions and development. It can include reviewing a design, examining promotion feedback, or preparing a difficult technical discussion. The useful output is a next action you can try at work and evaluate afterward.
Start internally when you need company context: how a team operates, who owns a decision, or what a promotion committee expects. An external mentor can offer another technical perspective and help you prepare questions or review work you are permitted to share. You may benefit from both.
No. Bring examples of work you want more of and work you want less of. We can compare the responsibilities behind each path, then identify an assignment or conversation that helps you test your preference before committing to a title.
No. A mentor can help you assess your work, choose projects, and explain your contribution. Your company decides the promotion criteria, available scope, timing, and outcome. Confirm those constraints with your manager before building a plan around them.
Prefer to start on your own? Browse the engineering mentoring resources or use the mentor evaluation checklist.
A design review, a piece of feedback, or a career decision is enough to start the conversation.