Skip to content

Engineering mentoring

AI already writes the code. Now your people's seniority decides.

Seniors are accountable for what AI produces. We grow your people into the ones who can carry that: with judgment, confidence in decisions and influence without formal authority. Your guide is Jimi, who has 20+ years in IT and runs a team where AI writes all the code.

The first 30 minutes online are free.

Jiří Mikulášek - Jimi Software Engineering Lead · mentor

What people come with

Do any of these sound familiar?

  1. 01

    Half the teams quietly work around last month's architecture decision, and the debates with architects keep going in circles.

  2. 02

    The new tech lead writes more code than anyone else on the team, and every decision waits on them.

  3. 03

    The team is all in on AI tools, but nobody can say what has actually changed.

  4. 04

    A senior doesn't know where to go next, has no one to learn from internally, and is starting to look around.

The common thread

Knowledge isn't the problem. What's missing is someone who has been there, helps untangle it and has no stake in the company's politics.

Why now

Seniority used to grow on its own. Not anymore.

  1. 01

    Code got cheap, judgment didn't

    Writing code costs almost nothing now. An engineer's value has moved to decisions, quality and architecture. To what to build, in what order and how.

  2. 02

    Juniors are losing their training ground

    They used to grow on simple work. AI now writes much of it, so future seniors have less to learn on.

  3. 03

    Growing is cheaper than hiring

    Hiring a staff engineer is slow and expensive. Growing one internally costs a fraction and the know-how stays with you.

Ways to work together

You work on whatever is on your plate right now.

You bring something concrete to a session: an architecture proposal, a pull request, a decision coming up, or a conversation with an architect. You go through it together and leave with a clear next step. Sessions are 60 minutes, online or in person in Brno.

Technical pairing

For tech leads, architects and staff engineers.

It works like pair programming, just not over code. Jimi works through the same problem with you over time: architecture, technical decisions, aligning stakeholders and guiding juniors. It also suits engineering managers and CTOs who want to think a decision through with an independent engineer.

  • Regular sessions at a rhythm that suits you
  • A quick call before a big decision
  • Someone with no stake inside the company

OutcomeInput for your decision: options and trade-offs laid out so you can take them straight to your team or leadership.

ExampleA company faces a decision that will last years: choosing a platform, what to do with the monolith, vendor lock-in or how to build with AI. No one inside can properly stress-test the proposal. With Jimi you work through the options and their impact before you commit to anything.

Engineering mentoring

For seniors on the way to staff and principal roles.

Technical depth, influence without formal authority and defending designs in front of architects and company leadership. On your own situations, not textbook examples.

  • Short 15–30 minute check-ins between sessions
  • Preparing for promotion, so the progress shows

OutcomeA senior who grows with you instead of leaving to grow.

ExampleA senior at a company with hundreds of engineers leads a major project, but their promotion request keeps getting stuck. Six months of mentoring: alignment across departments, defending designs in front of architects and work that's visible across the company. The result is a promotion case backed by facts.

What the company gets

You're not buying hours of mentoring. You get a staff or principal engineer grown in-house, confidence in architecture decisions, progress visible on your career ladder and less risk of losing a key person.

Who will guide you

Jimi

Software Engineering Lead · mentor

20+ years
in IT, from backend to leading R&D
AI-first team
AI writes all the code in his team
AIThatWorks
talk on how senior work is changing, 2026

Jimi has been in IT for 20+ years. He started as a backend developer (SaaS and on-premise), did stints in operations and frontend (mobile apps at a startup), and for the past ten years has led teams as a tech lead, software architect and head of R&D. For the past year his team has had AI write all the code, and he talks at conferences about what that has done to the work of senior engineers. He works with people on what they're really dealing with: understanding the system, the decisions behind it and the trade-offs they bring.

Testimonials

What people who worked with Jimi say.

  • “I found a way to grow in my role through external mentoring. (…) Thanks to our sessions, I gained more confidence in my decisions and improved my ability to guide my team forward.”

    Michal D.Growing in the role

  • “I was focused on transitioning from senior to principal. (…) Jimi helped me reframe conflict as a tool for achieving better results, rather than viewing it as a negative obstacle.”

    Oleksandr S.From senior to principal

What we build on

What you can count on.

  1. 01

    What's said in a session stays between you

    When the company pays, the manager hears the agreed goals and how it's going. Not what was said. We're happy to sign an NDA.

  2. 02

    We don't poach your people

    We never talk about jobs elsewhere with anyone we work with in mentoring or training. We want them to grow with you.

  3. 03

    No commitment to start

    The first 30 minutes are free. We carry on only if it makes sense for both sides.

Frequently asked questions

How much does it cost?

It depends on the format and scope. After the intro call we'll send you a concrete proposal.

Does the company pay, or the individual?

Either. Companies usually pay for pairing for tech leads and architects and mentoring for seniors. But you can also pay for mentoring yourself, or suggest it to your employer.

Online or in person?

Online from anywhere, in person in Brno. Between sessions you can have a short 15–30 minute call.

How will you know it works, and how long does it take?

At the start we agree with you on a goal for each person. Along the way you know how it's going, and at the end we hold a joint review. What's said in sessions stays between Jimi and your person. It usually takes a few months, because the value shows in everyday decisions.

How does it follow AI training?

Training teaches the team to use the tools. Mentoring makes sure it shows up in the everyday decisions of specific people. For example two tech leads for three months: together we set a standard for reviewing AI-written code, working with context and measuring impact.

How does it relate to Engagement Radar?

Mentoring works on its own. For a new tech lead it makes sense to add Engagement Radar, so the manager sees early on how the new role is going.

Shall we talk about what you're dealing with?

Write a few lines about what's going on. We'll get back to you and set up a free 30-minute call with Jimi, no strings attached.

  1. 1You write a few lines
  2. 2We set up a call with Jimi
  3. 3We suggest how to work together

We'll only use your details to reply. Privacy policy