Read a sample: 1. The Introduction Only an Internal Candidate Can Give
The interview begins with a familiar question: “Tell us about yourself.”
Across the table is a manager who has seen your name on project updates. Beside her is someone you have worked with for years. A third panelist is from another part of the organization and has never met you. All three are waiting for the same answer, but they are not starting with the same picture of who you are.
That is the particular challenge of an internal interview. You are not introducing yourself to a room of complete strangers, yet you cannot assume the room knows your work. You may have a reputation, a history, and a working knowledge of the organization. You may also be carrying expectations you did not create: that your current title explains your abilities, that your manager has already told the panel about your contributions, or that your reason for applying is obvious.
Your opening answer is a chance to give the panel a useful starting point. It connects the work you do now with the work you want to do next. It tells familiar colleagues what you want them to notice about your experience and gives unfamiliar panelists enough context to follow the rest of the conversation.
It does not need to tell your entire career story. It does not need to prove that you are the only possible choice. It needs to make the next question more productive.
“Tell me about yourself” sounds broad, and sometimes an interviewer may leave it deliberately broad. In the context of an internal interview, though, the panel is usually looking for a professional introduction rather than a complete autobiography. They want to understand where you are now, what experience you bring, and why this opportunity makes sense for you.
That does not mean every sentence must name a requirement from the posting. A natural answer can include the path that brought you to your current work or the kind of problem you enjoy solving. The difference is purpose: you choose details because they help the panel understand your candidacy, not because they happened to occur earlier in your career.
Consider the difference between these two openings for a hypothetical employee applying to a project coordinator role:
> “I’ve been here for several years. I started in customer support, then moved to operations. Most people know the work I do, and I thought it was time for something new.”
And:
> “I work in operations, where I help our team track requests and coordinate handoffs with customer support. Over time, I’ve become especially interested in keeping work moving when several groups are involved. I’m applying for the project coordinator role because it would let me build on that experience in a position focused more directly on planning and follow-through.”
The second answer is not more valuable because it sounds formal. It is more useful because it gives the panel something to work with. It names the candidate’s current setting, describes relevant work in accessible terms, and offers a reason for the move. It also makes a distinction between experience the candidate already has and the opportunity they want to develop further.
Neither answer needs to be copied. Your own introduction should sound like you and reflect the role you are pursuing. The comparison simply shows what changes when you treat the opening as an orientation for the panel rather than a summary of your employment history.
As an internal candidate, you can speak from firsthand experience with the organization. You may understand how teams depend on one another, how decisions move through the business, or what customers and colleagues need from your area. You can draw on work the panel may recognize and connect your interest in the role to the organization’s actual environment.
That knowledge can make your introduction more grounded. An external candidate might reasonably describe a general interest in improving handoffs. You can describe what you have learned while participating in them. Someone outside the organization might express interest in the team’s mission. You may be able to explain how your current work brought you into contact with it.
The advantage is not that you possess inside knowledge for its own sake. It is that you can use relevant experience to explain why you are ready to contribute and what you hope to learn.
For example, a hypothetical employee moving from a frontline service role into a training position might say:
> “In my current role, I’ve enjoyed helping newer colleagues learn how we handle customer requests. I’m interested in the training position because I’d like to focus more of my work on helping people build that confidence, while developing my skills in designing and delivering learning.”
The candidate does not claim to be an experienced trainer merely because they have helped colleagues. They identify a genuine connection and acknowledge the development the new role would involve. That is a credible use of internal experience.
You may also have access to context that can help you prepare: a posting, conversations with people familiar with the work, or knowledge gained through collaboration. Use that context thoughtfully. Being internal does not necessarily mean you know everything about the role, and an impression formed from the outside of a team may not reflect its current priorities. Curiosity remains an advantage even when the building, systems, and people are familiar.
The most common trap for an internal…