Applying for a Job at Your Own Company

An internal application inverts the usual problem. Normally you are writing to a stranger who knows nothing about you, and most of the letter is spent establishing that you exist and are competent. Internally, the reader can look you up in about four seconds. Half the standard letter is therefore dead weight.

What replaces it is harder. The reader isn’t asking “who is this person?” They’re asking “why is this person leaving where they are, and can they do something they haven’t done here?” Those are the two questions, and a letter that ignores them and recites your history instead is the most common internal failure.

Do you even need one?

Often the process asks for one, and then you write one. Where it’s genuinely optional, write it anyway if the move is any kind of stretch — sideways into a different function, up a level, into a team that doesn’t know your work. A short note is the only place you get to frame the move before someone else frames it for you.

Where you’re applying to a role adjacent to what you already do, for a manager who has watched you do it, a three-paragraph note is plenty. Length here is a function of how much explaining the move needs, not of respect.

The three questions

Why are you leaving your current team? Answer this, briefly, and answer it forwards. I want to work on X is fine. My current role has stopped growing is fine. What is not fine is any version of my manager and I don’t see eye to eye, however true, because an internal letter is a document inside a company and it will be read by people who talk to each other.

Can you do work you haven’t done here? This is the real question for any non-lateral move, and it’s the same argument as not meeting one of the requirements — except that here you can be checked. Don’t overclaim. Point at the closest thing you’ve actually done and say what transfers.

Is this going to be awkward? Unspoken, and always present. Does your manager know? Is your current project mid-flight? A single sentence handling this makes you look like someone who thinks about consequences: My manager knows I’m applying and we’ve discussed cover for the migration through October.

What “why this company” becomes

You can’t write the usual answer to “why this company” — you already work there, and telling people who pay you how much you admire the mission reads as strange. The internal equivalent is much better: evidence that you understand how this place actually operates.

That’s a real advantage. You know why the last attempt at the thing failed. You know which two teams have to agree before anything ships. Say one such thing, precisely, and you have demonstrated something no external candidate can.

The reason I want this role specifically is that the pricing changes keep stalling at the same point — nobody owns the handover between billing and support, so every fix arrives as a Slack thread and dies there. That’s the part I’d want to fix, and it’s mostly a process problem rather than a systems one.

Assume it gets forwarded

Internal letters circulate. Yours may be pasted into a thread with your current manager on it, read aloud in a calibration meeting, or kept in a file for two years. Write it as though all of that will happen, because some of it will.

Practical consequences: no complaints, no comparisons to colleagues, no salary hints, no I’ve been overlooked, and nothing about a conversation you had in confidence. If a sentence would embarrass you when read by the person it’s about, cut it. This is the one context where the cheerful, forwardable version is also the strategically correct one.

A hypothetical internal letter

For a support lead applying to an internal product role. Names invented.

Hi Priya,

I’d like to apply for the Product Manager role on Billing. I’ve been in Support for three years, the last eighteen months as lead for the payments queue.

The reason I want this one rather than a product role generally: I’ve been writing the escalation summaries for billing failures since last year, which means I’ve read roughly every way a customer can be charged wrong. About a third of what comes to us isn’t a bug, it’s two settings that are individually reasonable and contradictory together. I’ve been filing those as tickets, and I think they’re actually product decisions nobody has been given.

What I haven’t done is own a roadmap or run discovery properly. The closest is the refund-flow change last spring, where I wrote the spec, argued it through with Finance, and worked with Dan on the rollout — that’s the shape of the work I’d want to do more of, but I’d be doing it at a larger scope than I have.

Marcus knows I’m applying. The queue has cover through the end of Q3 either way.

Happy to talk it through whenever suits.

Rachel

Four short paragraphs, no history recital, and every one of them doing something the reader can’t get from the internal directory.

The failure modes

Tenure as an argument. I have been with the company for six years and feel ready for a new challenge. Six years is a fact, not a case. It tells the reader you want the job, which they had inferred from the application.

The résumé in prose. You have less excuse for this internally than anywhere else — they have your record. Spend the words on judgement instead, the way the judgement paragraph works in an external letter.

Over-familiarity. Knowing the reader socially is not licence to write three lines and a joke. It’s still an application; someone who isn’t in on the joke will read it.

The soft resignation. A letter that spends two paragraphs on how much your current role has disappointed you reads as a person leaving rather than a person arriving. If you find the negative version easier to write, write it, delete it, and then write the version about the work you want.

If the answer is no

Internal rejections carry information that external ones don’t, because you can still ask. Ask the hiring manager what would make the answer yes in a year, in person, once the decision is settled and not on the day. That conversation is worth more than the role was, and it’s not available to anyone outside.

The whole thing in one line

You are not introducing yourself. You are making a case for a move, to people who can check every word, in a document that will be forwarded.