Already provide an agenda of our time together when I set up our time. "First, I would love to learn about your career journey a bit more, then I will have some operational questions, spend some time sharing about our company and where we are going and then allow enough time for you any of your questions" Since I drive the conversation, I choose the format, as giving choices have back-fired up to and including the time of interview. This is MY pov. I am reaching out with already doing a lot of research on your resume, to pple I know at your current cpy, companies you've worked already and review of skill set provided. I don't do titles. I have my hopes and dreams that you will reflect what your resume says with the intent of moving you forward to a panel interview which is an on screen Teams or Zoom interview. This is my why with me wanting to choose. Let's say they're unfamiliar with Teams, they don't use it a lot, their current org uses more of Zoom or something else, this allows them to get that set up on their end, do the struggle part with me first. THEN, once moved to a panel, if chosen, they will have that part down, makes them feel more confident with even getting logged into the panel as they've done it already. They may not know my motivation but that's my motivation as it's ok to not be familiar with some programs. So, I'm wanting to set candidates up for success. If I recommend you to move one, that's a big deal, and I want you to do GREAT and to Succeed. NOW, in saying that, if a candidate can't do an on screen interview and they have a valid reason, connection is spotty, etc, then we pivot. Staying flexible will also help them be at ease, BUT if they do get moved on I have the moment to say hey, make sure you're where you have a good connection, take that stressor off your plate as it will be on screen. Be human, not a BOT.
Share your insight
Join an authentic community that helps women support each other at work. Share your professional experience or ask for advice — you can even post anonymously.
46 Comments
Join the conversation