1. LandOffer
  2. Blog
  3. All articles
  4. Try Engineering Management Before Committing to the Role

Career Growth

Try Engineering Management Before Committing to the Role

Design an approved management learning trial with authority boundaries, mentor support, adjusted IC workload, privacy, and an explicit return decision.

9 min readLandOffer team

Try engineering management through an approved, time-limited assignment that exposes you to supporting other people, not just running a project. Agree on the work, authority limits, mentor, reduced IC commitments, privacy rules, review dates, and supported return to individual contribution before starting. At the end, distinguish what you enjoyed from what you have not yet experienced. A trial can inform a career choice without proving readiness for every management responsibility.

This LandOffer.ai guide uses a fictional eight-week learning trial and completed reflection. The example is an editorial design, not a tested employer program or an actual personnel decision. Eight weeks is its chosen boundary, not a universal requirement or entitlement.

An engineer practices supporting a colleague at a boat workshop while an experienced mentor stays nearby and personal craft tools remain available.

Choose a learning question that requires people work

An engineer can enjoy planning, architecture, and removing technical blockers while disliking the recurring responsibility of supporting people. Use the trial to separate interest in technical coordination from interest in recurring people support. Delivering a project successfully does not establish that you want to manage people.

Start with a question such as: “Do I want to spend a meaningful part of my week listening, giving developmental feedback, following through on another person's needs, and negotiating capacity?” That is more useful than asking whether you can tolerate additional meetings. Describe the responsibilities in your employer's actual manager role, since team structures differ.

GitLab's IC-to-manager guidance lists supervised ways to gain experience, including manager backup, mentoring, onboarding support, and coordination. It also recommends discussing the work with managers and using role-play. These are company-specific examples of learning activities, not permission to assume authority at another employer.

Pick activities that can answer your question within the allowed scope. A supported mentoring conversation can reveal whether you listen and follow up. A role-play can expose your urge to avoid difficult feedback. Neither establishes how you would handle a sustained performance problem with formal accountability. Record those limits from the beginning.

Separate a learning trial from an acting appointment

A learning assignment does not automatically change reporting lines or authorize decisions about pay, ratings, hiring, discipline, or confidential employee information. Name the manager who retains those responsibilities. Colleagues should know whom to approach for matters beyond the trial.

GitLab's engineering career-development page describes an apprenticeship with an agreed time allocation, deliverables, support, and appropriate workload. It distinguishes learning from business-driven reassignment. Its stated default duration and eligibility belong to that program; they do not define the eight-week example here or your employer's process.

Ask your manager which internal arrangement is available and who must approve it. If the organization needs someone to hold formal management accountability, discuss that appointment through its actual process rather than labeling it a low-risk experiment. Responsibility should not become real while support and authority remain imaginary.

For a bounded trial, write down what you may propose, facilitate, or practice, and what you may decide. “Facilitate the capacity discussion; the manager decides staffing priorities” is clearer than “help manage the team.” Include an escalation route and a substitute mentor if the named person is unavailable.

Protect time and a credible return to IC work

Trying management on top of an unchanged technical workload produces ambiguous evidence. Exhaustion may reflect an overloaded arrangement rather than a dislike of management. Conversely, keeping only enjoyable technical tasks can hide the trade-off involved in a real switch.

A 2022 first-person Monzo account describes a management trial with a return checkpoint and a support network. The author also recounts taking on too many roles and reducing coding and technical-lead responsibilities. This is a historical employee experience, not evidence that Monzo currently offers the same arrangement or that readers can claim it.

Agree which work leaves your schedule, who receives it, and how expectations will be adjusted. Naming the duty that moves makes the time allocation reviewable when delivery pressure rises. If planned learning time repeatedly disappears, review the arrangement before drawing conclusions about your capability.

The return path also needs practical content. Identify the IC work you would resume, the person handling its interim ownership, the transition date, and how colleagues will be told. Confirm what is agreed and what still depends on organizational decisions. An encouraging remark about “always being able to go back” is weaker than a supported plan with named owners.

Completed eight-week trial agreement

In this fictional example, Rohan is an IC on a team maintaining a scientific scheduling tool. He enjoys helping colleagues reason through problems but does not know whether he wants ongoing people responsibility. Manager Tessa remains the team's formal manager and mentors the trial. The team receives an explanation of its scope before it begins.

The agreement below is filled in for this case. It does not grant access to personnel records or assign direct reports.

Agreement item Completed fictional agreement
Learning question Does Rohan want recurring coaching, feedback preparation, and capacity conversations as a substantial part of his work?
Time and old work One day per week for eight weeks. Tessa removes Rohan's release-coordination duty and defers his optional optimization proposal. Engineer Mae accepts release coordination for the eight weeks; Tessa confirms its time fits Mae's revised commitments before Week 1.
Mentor and review Tessa holds a weekly debrief. Engineering lead Luis is the escalation contact if she is unavailable. Weeks 4 and 8 are explicit review points.
Approved practice Mentor a consenting colleague on a work-learning goal, facilitate two team-capacity discussions, and practice difficult-feedback scenarios with Tessa using invented cases.
Authority retained Tessa owns staffing decisions, formal feedback, ratings, compensation, hiring, leave approvals, and employee concerns. Rohan can recommend a capacity option, not impose it.
Privacy and records No HR files, performance histories, or private manager meetings. Keep only agreed work actions in the mentoring record; reflection notes describe Rohan's behavior without personal details about colleagues.
Stop and return Either participant can request a review if boundaries or capacity fail. At Week 8, mentoring returns to Tessa's oversight. In Week 9, Rohan resumes the agreed IC investigation work; Mae continues release coordination under her separately confirmed allocation, so it does not silently return to Rohan. Any extension needs a fresh agreement.

The eight-week sequence makes the learning visible. Weeks 1–2 establish the mentoring goal, practice listening, and rehearse a fictional feedback conversation. Weeks 3–4 include the first capacity discussion and midpoint review. Weeks 5–6 repeat coaching and facilitate the second capacity discussion. Weeks 7–8 consolidate follow-through, obtain feedback, and make the direction decision.

The midpoint is not a ceremonial check-in. In this example, the first capacity discussion exposes an authority ambiguity: a colleague asks Rohan to decide which commitment should be dropped. He brings the options to Tessa, who makes the priority decision. They revise the meeting introduction to state that Rohan facilitates and Tessa decides.

In this fictional record, the correction shows Rohan following the agreed escalation route. It also reveals how easily colleagues can infer authority from facilitation. A trial needs room to repair that misunderstanding before it creates obligations for anyone else.

Observe behavior without collecting private employee evidence

After each approved activity, record the situation category, your action, mentor feedback, and the change to try next. Record the quality of your listening and follow-through rather than diagnosing a colleague's motivation or copying their personal disclosures.

For example, Rohan notes that he offered a technical solution before asking what the mentee had tried. Tessa suggests waiting for the colleague's reasoning and agreeing on the next learning step together. In a later session, he asks clarifying questions and follows up on the agreed action. The useful comparison concerns his behavior; it does not require publishing the colleague's work details.

Ask participants for feedback in a way that does not imply an evaluation of them. They should understand the learning arrangement and retain their ordinary manager contact. Do not promise absolute confidentiality that your organization cannot provide, or ask them to share sensitive matters to make the exercise feel more realistic.

Use fictional scenarios for activities that would otherwise require unauthorized access. A simulated difficult-feedback conversation can test your preparation, clarity, and willingness to stay with discomfort. Label the observation as rehearsal. It cannot substitute for experience of a real employee relationship over time.

Completed reflection and direction decision

At Week 8, Rohan and Tessa review the trial against its original question. The record includes positive evidence, an uncomfortable observation, an untested area, and a choice. It is not a rating of management potential.

A mentor's practice area contains two shared work stools and a separate personal craft station, with a removable boundary marker and an open return route.
Experience Completed observation and interpretation
Recurring mentoring Rohan enjoyed helping the colleague develop their own approach. He initially solved too quickly, then changed his questions after Tessa's feedback. He wanted to continue the follow-through, not only the interesting first conversation.
Capacity discussions He could summarize constraints but found competing requests draining. The first meeting required Tessa's authority clarification; the second used the corrected introduction and kept recommendations separate from decisions.
Difficult-feedback rehearsal He delayed stating the central issue in the invented case. A second rehearsal was clearer, but he still needed preparation and mentor feedback. No actual employee received formal feedback from him.
Work preference He missed extended technical investigation more than expected, even with the agreed release-duty reduction. He liked bounded coaching but did not want it to replace most of his technical week now.
Untested responsibility The trial did not cover sustained performance management, hiring decisions, compensation, confidential concerns, or full accountability for a team's development. It cannot establish readiness in those areas.

Rohan's completed choice reads:

I will return to the agreed IC investigation assignment in Week 9 rather than pursue a management role this cycle. I want to retain a separately agreed, limited mentoring contribution because supporting learning was meaningful. I do not want the larger recurring people responsibility now. Tessa retains management accountability; the trial creates no promotion, appointment, or continuing management duty.

Tessa confirms the fictional return arrangement and communicates the end of Rohan's facilitation role to the team. Any future mentoring commitment will have its own time boundary. They do not quietly extend the trial because it was useful to the organization.

This conclusion does not mean Rohan cannot become a manager later. It reflects his current preference and the evidence available. Another participant could choose further management development, but that would still require a supported opportunity and the organization's appointment process. Interest, observed practice, readiness, and an available role remain separate questions.

Decide whether to continue, revise, or stop

The review can end with a return to IC work, additional supervised learning, or discussion of an actual management opportunity. State the next step and the responsibilities that end. Avoid leaving colleagues with an informal manager whose status nobody can explain.

If the trial failed to provide meaningful practice or mentor time, identify that limitation rather than interpreting missing evidence as a personal verdict. A revised trial needs a reason and corrected conditions. Repeating the same overloaded arrangement is unlikely to answer the original question more clearly.

Before closing, confirm ownership of open actions and the approved location of any retained work records. Remove unnecessary personal detail according to the organization's rules. Keep the reflection focused on your learning and decision, with a clear distinction between fictional rehearsal and authorized workplace activity.

Save the choice, evidence limits, transition owner, and date so the trial ends with an executable next step. You can return to LandOffer.ai for related internal-career guidance after that record is complete. A useful trial leaves both you and the team clear about what happens next.

Sources and Further Reading