Making the Jump: Internal Move or New Employer

Monday, 08:30, at Northgate Retail. Jonah has been on the desk four years and has a ladder card with a full evidence column. It lists two permission rebuilds and the print server standard. It also lists a certificate renewal done with the sysadmin's hand near the keyboard, and a runbook other people use. Adaeze, the sysadmin, said last week, in the lift, "You're ready, you know." Northgate has one sysadmin, no junior role, and no plans for one. A logistics firm across town has advertised a junior systems administrator position, closing Friday. Jonah has asked Carmen, the desk lead, for twenty minutes at nine. He has not yet decided which of two conversations he is about to have.

Making the jump is the move from the desk to an infrastructure role, and it takes one of two shapes. One is the internal move, where the organisation that has watched you work gives you the next rung. The other is the move to a new employer, where a stranger has to be persuaded from the evidence. Both are ordinary, both work, and the choice between them is mostly made by whether a rung exists where you are. This article is part of our The Helpdesk-to-Sysadmin Ladder series. It assumes the evidence is already on the card. What the card is and how to fill it is in What the Helpdesk-to-Sysadmin Ladder Looks Like.

It starts with the honest comparison between the two routes, then the conversation with the manager and the three answers it can produce. Next comes the shadow-sysadmin arrangement, which is the internal route in practice, followed by interviewing from the desk. We cover the first ninety days on the other side, which are slower and more dangerous than anyone warns you. Then come what you will miss, leaving the desk well, and a short war story. We finish with the move plan, a one-page template for either route.

Internal Move or New Employer: The Honest Comparison

The internal move is the easier jump and the one most technicians would prefer. The people deciding have seen the work, and the systems are familiar. The first ninety days happen among colleagues who will forgive a slow week. The internal move's weakness is that it depends on a vacancy or on an organisation willing to create a rung. And many small organisations have neither: one sysadmin, no plan to hire a second, and a desk that cannot spare anyone. The internal move also carries the desk with you. For a while you will be the sysadmin that store managers still phone about tills, because you were the technician who fixed them. The phone does not know you have moved.

The new employer is the harder jump and the one that is always available. The rung exists because it was advertised. The pay and the title are stated rather than negotiated from a desk grade, and nobody will phone you about the tills. Its weaknesses are the ones you would expect: a stranger must be persuaded from write-ups and an interview. The systems are unfamiliar. And the first ninety days happen among people who do not yet know that you are usually good at this. It also means leaving a desk you know how to run, which is a real cost and the subject of a later section. The table puts the two side by side; neither column wins. And the one that applies to you is usually decided by the first row.

The Conversation With the Manager

Have the conversation before you need it, which means before the advertisement closes on Friday rather than after you have accepted the job. Open with the card, not with the wish: "I'd like to show you where I think I am on the ladder and ask what the route from here looks like." Then show the evidence column and let it do the talking. A manager shown a wish has to guess. A manager shown two permission rebuilds, a print server standard and a renewal runbook has something to respond to. Most respond better than technicians fear, because a manager who has run a desk knows what those lines cost.

Ask the one question that sorts the answer: "Is there a next rung here, or is the next rung somewhere else?" There are three honest answers and all three are useful. "Yes, and here is when" is the internal move, and the rest of the conversation is about the shadow arrangement and the date. "Not yet, but" is the shadow arrangement without the date. It is worth having on the condition that a review date is written down. That is because "not yet" without a date is a way of saying no slowly. "There is no rung here" is the most useful answer of the three, because it is honest and it stops you waiting. A manager who says it plainly will usually help you leave well. That is worth more than most people realise until they have done it the other way.

Do not bring the advertisement as a threat. "I've been offered a job unless you promote me" produces either a counter-offer made under pressure, which sours, or a no made under pressure, which is final. Neither is the conversation you wanted. Bring the advertisement as information if it is relevant: "There's a junior role at the logistics firm closing Friday; I'd rather move here if a route exists, and if it doesn't I'd like to apply with your support." That is a sentence a decent manager can work with. It says what you want, gives them the first option, and tells them the clock without pointing at it.

The Shadow-Sysadmin Arrangement

The shadow-sysadmin arrangement is the internal route in practice: a written agreement between the technician, the sysadmin and the desk lead. For a fixed part of each week, usually half a day, the technician works infrastructure tasks alongside the sysadmin. The agreement has named tasks, a review date and cover for the desk. It is how a rung gets built in an organisation that does not have one. And it is how a technician moves from "ready, you know" in the lift to a job description with their name on it. It is not a favour from the sysadmin. And it is not free extra labour for the infrastructure team; both of those versions collapse inside a month.

Three things make it hold. First, the tasks are named, in writing, and they are the teaching tickets and the routine. They include the certificate calendar, the patch cycle, the backup check, and the next permission tangle. Each has the dangerous step marked as the sysadmin's. Second, the desk is covered for the half day, visibly, on the coverage calendar. That way, the technician is not doing both jobs and the desk lead is not quietly losing a person. The way to arrange that cover is in The Coverage Calendar. Third, there is a review date, usually at three months. A question is written beside it: "Is there a rung at the end of this, and when?" An arrangement without the review date is a hobby. A pleasant one, with servers in it, but a hobby.

The review is where the arrangement either becomes a role or becomes honest. If the organisation can create the rung, the review produces a date and a title. If it cannot, the review says so. In that case, the technician now has three months of infrastructure evidence, a sysadmin who will vouch for them, and a clear reason to look outside. That is a far better position than the one they started in. Either way the organisation has gained: a runbook set, a second person who knows the calendar, and a desk that saw what the route looks like. The sysadmin has gained a colleague. Sysadmins are not, as a group, over-supplied with colleagues.

Interviewing From the Desk

Interviewing from the desk means being honest about the gap and loud about the evidence. The gap is that you have not owned a system. Say so in the first minute, because the interviewer knows it from the CV and is waiting to see whether you do. "I've worked on the desk for four years, and I haven't owned infrastructure yet; what I have done is worked the tickets that lead into it, with the sysadmin watching the dangerous steps, and I've brought three write-ups." That sentence removes the question the interviewer was going to ask and replaces it with something to read. Bring the write-ups anonymised, two of successes and one of a mistake with its change record. The mistake with the record is the one that gets you hired.

The questions will be about changes, not vocabulary, if a sysadmin is on the panel. "Tell me about a change you made to a shared system." "What happened when something you did broke something else?" "What would you do in the first week if you found a server nobody had patched for a year?" Answer from the tickets, with ticket numbers if the panel seems to like detail, and with the sysadmin's part stated honestly. The panel may ask what you would do alone that you have only done with a watcher. If so, say "the same, with a change record and a time when the fewest people are affected, and I'd ask who the watcher is here". That is the correct answer and it is also a question about the job.

Ask two questions of them. "Who supervises the junior administrator's changes, and how?" The answer tells you whether the rung is real or whether you would be the only sysadmin with a junior title. The latter is the Bellweather problem from the first article in this series, and a thing to walk away from unless you want it. "What does your change process look like?" tells you whether they have one. An employer with no change process is an employer where the first ninety days are more dangerous than they need to be. An employer who answers both plainly is probably one worth joining. One who finds the questions odd has told you what the job is.

The First Ninety Days on the Other Side

The first ninety days are slower, quieter and more dangerous than the desk, and nobody warns you about the quiet. On the desk the day arrives as a queue and you are measured in tickets. On the other side the day arrives as a calendar with gaps in it. The gaps feel like failure to a person who has spent four years closing forty tickets before lunch. They are not failure. The gaps are the time in which a sysadmin reads, checks, plans and writes. The new junior administrator who fills them with the nearest ticket to feel productive has brought the wrong instinct across. Fewer tickets is the job. The tickets you do get are the ones nobody else could close.

The danger is that mistakes are bigger and slower to show. A desk mistake phones you back within the hour. An infrastructure mistake surfaces when the backup is needed, the certificate expires or the policy applies at Monday's start-up to four hundred machines. The habit that keeps you safe is the one The One-Page Change Record describes. Write down what you will change, when, who it affects, how to undo it and who you have told, before you touch anything. For the first ninety days have someone read it. Ask before you touch, every time, even when it feels slow. Especially when it feels slow. The desk taught you to fix things fast. The first ninety days are where you learn that fast was a property of the blast radius, not of you.

Keep a daily log for the ninety days: what you touched, what you learned, what you did not understand and who you asked. The log is partly for the review at the end and partly for the runbooks you will write from it. There is another reason: a new junior administrator forgets most of the first month. The log is how the second month gets easier. Expect to feel, around week six, that you were better at the old job than you are at this one. You were. You had four years of practice at it. Give this one the same courtesy.

What You Will Miss

You will miss the closure. A desk gives you thirty small completions a day, each with a person at the end who says thank you. Infrastructure gives you one large completion a fortnight, with nobody at the end because nothing happened, which was the point. Technicians who loved the desk for the people find the first months on the other side lonely. That is hard to explain to colleagues who never worked a queue. The honest advice is to keep visiting the desk, not to help, but to remember what the users look like. The sysadmin who forgets is the one who schedules the change window for nine on a Monday morning.

You will miss knowing what you are doing. For four years you were the person the queue went to for tills, and now you are the person who asks where the tills' server is. That passes, and it passes faster for people who ask more questions, write more down, and do not pretend. The one thing not to miss is the desk's habits: the reactive instinct and the fix-first-write-later reflex. Those habits also include the belief that a quiet hour means something is wrong. A quiet hour, on the other side, means the planning worked.

Leaving the Desk Well

Leave the desk the way you would want the person before you to have left it: with nothing in your head alone. Two weeks before the last day, list everything only you know. The list is longer than you think, because four years of fixing tills builds a private encyclopaedia nobody asked you to write down. There are the tills' quirks and the store manager who needs a phone call rather than a reply. There is the printer that only works if you restart the queue twice, and the password to the thing. Each item becomes a runbook, a knowledge article, a note on the right ticket, or a conversation with a named colleague. And the list is ticked off before the last Friday. The organisation's side of that same job is the audit of what walks out of the door when an expert leaves. It is in When the Expert Leaves. A leaver who does it for them is remembered for years.

Hand over the tickets, every one. Nothing stays claimed under a name that will not be at the desk on Monday, and nothing is transferred with a one-word note. Each open ticket gets a new owner and a note saying where it stands and what happens next. It also gets a message to the requester saying who has it now. The method for transferring a ticket so that nothing falls between the cracks is in Transferring a Ticket Between People or Departments. On a desk with claim-based ownership, the queue shows who holds what, as in QuerySolv. The list of tickets to hand over is then a filter on your own name rather than an archaeology dig. That makes the last week shorter and the Monday after it quieter.

Then close the side doors. The store managers who e-mail you directly need telling, in writing, with the desk's address. The message should go a week before you leave. That way, the first "I usually e-mail Jonah" arrives while Jonah is still there to redirect it. Consider the direct messages and the personal phone number on the laminated card in the warehouse. There is also the forwarding rule you set up in your first year and forgot. Each one is a channel that will keep delivering after you have gone, to nobody. The internal move needs this as much as the external one. You are still in the building, and that is precisely why the store managers will keep phoning you.

A Short War Story: The Thirty-One Tickets at Northgate Retail

Two years before Jonah's conversation with Carmen, a technician called Priya had left the desk at Northgate Retail on a Friday. She left for a junior administrator role at a bank, with thirty-one tickets still claimed under her name. The store till system's quirks were in her head rather than in the knowledge base. That was because the last fortnight had been busy and the handover meeting had been cancelled twice. The tickets were found over the following week, one at a time, as store managers phoned to ask why nobody had replied. The first till failure after she left took six hours to resolve instead of the forty minutes it had taken Priya. The fix involved restarting a service in an order that only she had known. The cost was two weeks of apologies to stores and a Saturday of lost trading at one branch. It also meant a desk lead who thereafter required a signed handover list from every leaver. That was reasonable, and everybody resented it for a year. Priya had been an excellent technician and left a desk that did not know it had lost one. The lesson Carmen took was that leaving well is a task with a checklist, not a feeling. The checklist starts two weeks out.

The Move Plan

The move plan is one page for either route. The top half is the decision: which route, who decides, what the evidence is and what the conversation produced. The middle is the shadow arrangement, filled in if the route is internal, with the named tasks, the cover and the review date. The bottom is the leaving list and the first ninety days, which apply to both routes, because an internal move is still a leaving. Fill the top in before the conversation with the manager, and the middle in the conversation. Fill the bottom in the fortnight before the last day on the desk. Keep it with the ladder card; together they are the whole story of the move. And a year later they are the document you hand to the next technician who asks how it was done.

THE MOVE PLAN — ONE PAGE, EITHER ROUTE
Name: ______________________   Date: ____________   Desk lead: ______________   Sysadmin: ______________

1. THE DECISION
   Route:  [ ] internal move   [ ] new employer   [ ] shadow arrangement first, then decide
   Does a rung exist here?  [ ] yes, from: ________   [ ] not yet; review on: ________   [ ] no
   Evidence on the ladder card (three strongest lines): ______________________________________
   The manager conversation held on: ________   Outcome in one sentence: ______________________

2. THE SHADOW ARRANGEMENT (internal route)
   Hours per week: ______   On which day: __________   Desk cover arranged by: ______________
   Named tasks (the dangerous step is the sysadmin's):
      [ ] ____________________________________   [ ] ____________________________________
      [ ] ____________________________________   [ ] ____________________________________
   Review date: ________   The question at the review: "Is there a rung at the end of this, and when?"

3. INTERVIEWING (new employer route)
   Three write-ups to bring (two successes, one mistake with its change record): ______________
   The gap, said plainly in the first minute: ______________________________________________
   Two questions to ask them: who supervises the junior's changes? what is the change process?

4. LEAVING THE DESK WELL (both routes; starts two weeks out)
   [ ] Everything only I know, listed:  runbook / article / ticket note / told to: ______________
   [ ] Every open ticket handed over with a note, a new owner and a message to the requester
   [ ] Side doors closed: direct e-mails, messages, phone numbers, forwarding rules
   [ ] Handover list signed off by the desk lead on: ________

5. THE FIRST NINETY DAYS (both routes)
   [ ] A change record before every change, read by: ______________
   [ ] Daily log kept; review at thirty, sixty and ninety days with: ______________
   [ ] The desk visited, not to help, on: ______________

Jonah's twenty minutes with Carmen produced the third answer: no rung at Northgate, not this year. Carmen supported the application across town. She also provided an introduction to the logistics firm's sysadmin, whom she had once worked with. Jonah started there two months later, with thirty-one fewer tickets to hand over than Priya had, because he had read the story. The desk missed him. It also ran, which was the point.

Frequently Asked Questions