Test a career direction before you commit
Try the work behind a job title before changing careers. Build a small experiment that tests one important assumption without betting your livelihood.
Test a career direction by trying a small piece of its ordinary work, then compare the experience with what you expected. An experiment should inform your next decision, not prove that you have found your permanent calling.
Before becoming an engineering manager, help plan a small project and discuss a difficult priority with its owner. Enjoying those conversations tells you something different from enjoying the idea of a management title.
A job title hides most of the working week. An architect may spend more time resolving incompatible requirements than drawing systems. A developer advocate may spend more time editing and answering questions than presenting. Before investing in a transition, find out which part of the actual work attracts you.
Name the assumption behind the move
Start with a sentence you can investigate. “Architecture sounds interesting” is too broad. “I enjoy comparing technical options and getting several teams to agree on one” points to work you can try. It also reveals a possible disappointment: enjoying technical exploration does not necessarily mean enjoying the negotiation around it.
The useful idea from Bill Burnett and Dave Evans’s Designing Your Life is to explore possibilities before treating them as commitments. Their public guide to prototyping life designs distinguishes conversations about another person’s experience from small first-hand experiences. Neither needs to become an application for a job.
Write down what you hope will change, what must remain acceptable, and what you do not yet know. “More responsibility” might mean deciding technical direction, earning more, having fewer approvals, or managing people. Those are different aims. A role that satisfies one may make another worse.
Try the decision
A developer wonders whether architecture work suits them. Which first test gives useful evidence?
The course may teach concepts, but it does not test the coordination work behind the role.
Next step: Name the ordinary task you still need to try.
This is an illustrative decision with stated assumptions. It cannot establish your employer’s policy or predict an individual career outcome.
Build a small test of ordinary work
Consider an illustrative example: a backend developer is curious about architecture. Their first idea is to complete a large distributed-systems course. That could build knowledge, but it would not test whether they enjoy the everyday work they are considering.
Instead, they agree with their manager to write a short options note for a low-risk internal tool. A named engineer retains the decision. The developer interviews two people with different needs, compares two approaches, presents a recommendation, and revises it after objections. The task is useful even if the developer decides against the career move.
Before beginning, the developer records an expectation: “I think I will enjoy clarifying conflicting needs, not just designing the solution.” They arrange a review after the task and agree which existing work will move to make room. An experiment is not small merely because somebody performs it in unpaid evenings.
Use a compact experiment note: the assumption, the activity, the person who can authorise it, the time boundary, the work it replaces, and the observation that will guide the next decision. Our proposed note is a planning aid, not a validated career assessment. For the actual options document, follow the guide to writing design documents people can use.
Separate the role from the setting
Afterwards, distinguish the task from its circumstances. Did you dislike explaining trade-offs, or did you dislike presenting without preparation? Did you enjoy the work itself, or mainly the attention of trying something new? A bad meeting with one person is not a verdict on an entire profession.
In the example, suppose the developer enjoys gathering requirements and revising the design but finds the cross-team negotiation tiring. That is not an automatic rejection of architecture. It suggests a more precise next test: observe how an experienced engineer prepares for disagreement, then try another bounded discussion with that support.
Ask the reviewer about an observable contribution: “Which part of my recommendation helped the decision, and which part still needed you to take over?” Avoid turning the review into “Would I be a good architect?” The larger question invites a broad judgement from a tiny sample.
What a trial cannot tell you
A trial gives incomplete evidence. Shadowing a manager does not give you their accountability, access to sensitive conversations, or the experience of supporting a struggling employee. Building a hobby tool does not reproduce the demands of maintaining a service for paying customers.
Acknowledge those missing parts instead of making the experiment larger until it becomes the full transition. Ask somebody doing the role which important demands the trial leaves out. A second conversation may reveal a missing constraint more cheaply than another month of study.
There are also real access limits. Some employers cannot offer rotations; some people cannot reduce paid hours or take an unpaid placement. A conversation, a public sample project, or reviewing a published case may be the available test. None is evidence of less ambition. Do not experiment with production access, people management, or customer commitments without permission.
Choose the next step, not your whole future
End with one of three decisions: explore further, reshape the direction, or stop pursuing it for now. Record what would change your mind. Discovering that you enjoy technical depth more than coordination is useful information, not a failed exercise.
A title can mean different work in different organisations. Read how senior and staff roles differ in scope before assuming the same experiment answers both questions. When you have a plausible direction, plan the move around transferable skills and explicit gaps, rather than treating your previous experience as irrelevant.