Career journeys
The work that doesn’t make the release notes
A fictional conversation about quiet expertise, useful documentation, and learning to recognise the work that keeps everything running.
Maya is a fictional systems engineer in this sample interview. Her story explores a familiar feeling: being dependable for years, yet struggling to describe what that dependability is worth. No real person or employer is represented.
Experience can look like knowing which question to ask before touching the keyboard.From this fictional sample conversation
What does a good working day look like now?
For a long time I measured a good day by the number of tickets I closed. In this imagined version of my working life, a good day is when someone else can solve a problem because I left them a clear note.
It is less dramatic than rescuing a server at midnight. It is also the sort of work I would like to keep doing.
Which skill took you longest to appreciate?
Asking what changed. Not what should have changed, or what the dashboard says, but what actually happened between the last good state and now.
That question came from years of small mistakes. It does not become obsolete when the tools change.
How do you approach a new AI tool?
I give it a small, non-sensitive task I already understand. Then I read the result and check its assumptions. It can help me draft a checklist, but I still need to know whether the checklist fits our system.
I do not need to understand every new product this week. I need to make a sensible next experiment.
What habit would you pass on?
Write down the reason, not just the command. A command can be copied. The reason helps the next person decide whether to use it.
What would you say to someone feeling invisible at work?
Keep a private record of what became easier for other people because of your work. Include the explanation you gave, the incident you helped prevent, and the person you taught. Those things belong in your account of your career too.