Engineering Mentorship & Pairing

Mentoring that has goals and a rhythm, pairing and mob sessions that actually spread knowledge, and the habits that let senior and junior engineers learn from each other on purpose.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Engineering Mentorship & Pairing, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

202

Starter tasks

⚙️ Software Engineering

Engineering Mentorship & Pairing

Growing engineers through mentoring, pair and mob programming, and deliberate knowledge sharing between senior and junior team members.

  1. Six-month mentoring goal statement
  2. Finding a mentor outside your reporting line
  3. Mentoring working agreement and first session
  4. Pairing environment ready on your machine
  5. Personal skills map for mentoring sessions
  6. Mentoring session notes system
  7. Team pairing working agreement
  8. When to pair and when to work solo
  9. Mentor readiness check before taking a mentee
  10. Twice-monthly mentoring session rhythm
  11. Weekly protected pairing block
  12. Friday team mob programming session
  13. Weekly learning log for mentees
  14. Monthly internal tech talk series
  15. Pair rotation schedule across the team
  16. Quarterly mentoring relationship review
  17. Mentoring and pairing feedback themes
  18. Senior engineer office hours
  19. Driver and navigator role practice
  20. Strong-style pairing with a less experienced partner
  21. Asking for help well as a mentee
  22. Teaching with questions instead of answers
  23. Ping-pong test-driven pairing
  24. Explaining a system at the whiteboard
  25. Mentoring and pairing reading list
  26. Choosing a remote pairing tool for the team
  27. Checking whether pairing is paying off
  28. Knowledge silo map and pairing targets
  29. Designing a team mentoring programme
  30. Matching mentors and mentees fairly
  31. Restarting a mentoring relationship that has stalled
  32. Making mentoring time visible in team capacity
  33. First team mob programming day
  34. Pair-on-everything week experiment
  35. Shadow day with a staff engineer
  36. Coaching a mentee through their first talk
  37. Closing session for a mentoring relationship
  38. Mentoring a career changer or bootcamp graduate
  39. Mentoring and pairing across time zones
  40. Becoming a first-time mentor as a new senior
  41. Mentoring versus managing your own reports
  42. Summer intern mentoring plan
  43. Pairing across working styles and access needs
  44. Reverse mentoring from junior engineers
  45. Mentoring a senior engineer towards wider technical scope
  46. Peer mentoring circle for underrepresented engineers
  47. Mentor guild for developing other mentors
  48. Facilitating mob programming across several teams
  49. Pairing with an AI coding assistant as a third seat
  50. Apprenticeship pairing curriculum for a junior hire

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Six-month mentoring goal statement

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Most mentoring stalls because nobody can say what the mentee is trying to get better at, so every session drifts into whatever broke that week.

First tasks

  • List the three pieces of work in the next quarter you most want to do well
  • Turn each into a goal naming the skill it would stretch
  • Write the visible sign of progress next to each goal
  • Share the goals with your manager and ask which projects fit them
  • Reread the goals and mark each as on track, stuck or changed @recurring(quarterly)

Finding a mentor outside your reporting line

Your manager judges your performance, which makes it hard to admit what you do not understand. A mentor from another team, a senior engineer you admire or someone at another company can hear the half-formed questions and give advice with no stake in your rating.

First tasks

  • Write down three engineers whose work you would like to learn from
  • Note what specifically you would ask each of them about
  • Send a short request to your first choice offering three trial sessions
  • Book the first session as soon as someone agrees

Mentoring working agreement and first session

The first conversation sets expectations that are awkward to change later: how often you meet, who sets the agenda, what stays private and how either side ends it. Agreeing these in writing at the start prevents the slow fade where sessions get cancelled and nobody says why.

First tasks

  • Send your goals to the mentor two days before the first session
  • Agree frequency, length and who sets the agenda during the session
  • Write down what stays confidential and how either side can end it
  • Book the next three sessions as a recurring calendar event

Make it yours.

Install Engineering Mentorship & Pairing, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.