When You Know Everyone in the Room
Photo by Charles Deluvio on Unsplash

When You Know Everyone in the Room

What it’s like to interview with your own team

Recently, a position opened up within my team that I really wanted, and as the role was also open to the external applicants, I had to interview for it just like everyone else. Although it might sound like an easier process to interview with my own team, I had to quickly identify the challenges and dynamics of this experience. It’s one thing to interview with people you don’t know because you get to walk in and have a blank slate. But what happens when you walk into an interview for a role you really want, and you know everyone? How do you prove yourself? Here is my experience and things I learned along the way. ?

Get comfortable being uncomfortable.?

First off, it was awkward for both me and my teammates?doing the?interviewing?as they were not just colleagues, but friends too. So, acknowledging the uncomfortableness at the onset of the interview is good to do. It’s also vital to respect that the business and decision-making process was separate from our individual rapport. If things didn’t go my way, I knew I had to?make sure?my personal feelings?didn’t?affect?our?work relationship.

Preparation is everything

Although I have experience in working with the team, I still had to prepare for the interview all the same. In fact, I would say instead of feeling like I might be at an advantage since I was already on the team, I wanted to over prepare and use all the available resources at my disposal.

Tip: One way to prepare for an interview if you don’t have internal experience is by finding people within the company with similar roles. Use LinkedIn to see their past professional experience. See if they have produced or shared articles that resonate with you about what you could experience. Seek information that might shape a better picture of what could be asked of you.

Another way to prepare is to comb through your old jobs on your resume. Try to think back to when you were in each role. What were some major growth experiences you took away from the job? Can you craft stories about those experiences that might be relevant to the new job you’re applying for? ?There may come a time where you could be asked to give an example of what you did, and you may be caught off guard. But if you have a bank of stories from your experiences you can draw parallels to show what you know and how it could translate across future work. When those stories are top of mind before your interview, they will surface at the right time.

Root your answers in real examples from your experience

At a senior level, interviewers typically tend to ask more behavioural, thought-provoking questions like, “Can you give me an example of when you did…?” rather that the hypothetical “What would you do if…?” type questions.

When I originally joined Microsoft, the role I was in was a close match to the skills needed for the job I was interviewing for. This served me well,?as I had a full story bank to rely on during my initial interviews.?For this new?role, it was clear to me that I had some gaps in?the required?job?experience.?I?did have?the relevant competencies though, so?I started to map out my own experiences?to?demonstrate?my?capabilities. For e.g. I had never had a "difficult conversation" with a direct report?regarding?compensation.?However,?in my prior role,?I had several difficult conversations with junior colleagues over workplace culture. I also spent time thinking about how I could close these gaps?to?show how I can grow and map out pathways to get there. I wasn’t a 100% match,?which is ok. No one ever is, but I found potential ways to meet those expectations.

Confidence is key

Lastly, I always believe that I can do a job even if I don’t have every single qualification. What I don’t know, I will learn. I continually grow and expand my skills. And every time I go outside of my comfort zone to pursue my next dream job, it works out!

Have you ever interviewed internally? I’d like to hear your stories in the comments.

Catherine Tomasko

Sr. Technical Program Manager @ Red Hat | PMP, Scrum Master

3 年

Nicely written. This article is timely and personally resonates with me because I have recently interviewed internal candidates. It's critical to set the ground rules and expectations so that both the candidate and the hiring team know what to expect and how to behave. Discussing the "awkwardness" is wonderfully transparent and should be a natural step in open communication instead of an elephant in the room that no one acknowledges. I'm going to share this on my network to help others along their career journeys.

One idea that I often come across while reading through posts of people who have made it big is "Get comfortable?being uncomfortable" & you have wonderfully articulated it.

Rohan Shirsat

Product, Organization, Business Strategy

3 年

Personally i never interview... I always have a conversation. Whether I am looking to hire or be hired. I dont like the process of asking people what they know and to point out what they lack. That's not me. So first, take the discomfort out of the equation. The hiree and hirer are in a symbiotic relationship. Both need each other. Hiring should always be strategic IMHO and should be less on skills and more on dedication, work ethics, and problem solving. At least when discussing about senior roles. The preparation part is the key. Infact in internal transfers, you probably know what challenges the hiring team is facing. I would in fact work on their problem statement and prepare a presentation to tell them what value add i would bring. Now interviewing is just one part because you could crack the interview but still suck at the job. Because the movie is only starting. So I would rather worry and work on a plan on what I should do once I get the job Because it is always as the zen master says "it remains to be seen" ?? Excellent article

Limor Lahiani, PhD.

Startup Advisor | AI Speaker | Co-founder & CTO | Engineering Group Manager | Empowering Women in Tech | Career Mentor

3 年

Great write up Sonal ?? Glad you got that role!

Cliff Lewis

DevOps Team Lead - Principal System Test Engineer at Itron, Inc.

3 年

Wow, your article is packed with some great advice. Thank you for sharing your experience, Sonal!

要查看或添加评论,请登录

社区洞察

其他会员也浏览了