I have a phone interview tonight for a Tier 2 IT position that could potentially double my current help desk salary. I'm excited but extremely nervous, especially because my resume has a few gaps. I want to clearly explain how my troubleshooting ability, performance under pressure, teamwork, and thoughtful ticket escalation prepare me for the role without sounding like I'm exaggerating or filling the conversation with empty claims. I've been preparing STAR-format examples and answers for questions such as "Tell me about yourself," "What do you do in your current role?" and "Why are you looking for a new position?" I've also researched the company and understand why the position and its industry interest me. What practical advice would help me stay calm, communicate my experience effectively, and avoid overexplaining?
5 Answers
Try to treat it as a conversation rather than a performance. Take a breath, speak at your normal pace, and answer the question directly without adding unrelated details just to fill silence. Be confident but not arrogant, and focus on real examples of problems you solved, how you communicated with users, and how you worked with teammates.
A first phone screen is often fairly general: they may explain the role, confirm your experience, discuss what you’re looking for, and check whether your salary expectations align. Take a short walk beforehand, keep a few notes nearby, and allow yourself a pause before answering. Nervousness usually means you care—it doesn’t mean you’re unprepared.
For the reason you’re leaving, keep it positive. You can say you’re looking for greater technical depth, more room to grow, and compensation that better reflects your skills. Avoid criticizing your current employer. Also remember that the interview works both ways, so ask what challenges the team is facing, what success looks like in the first few months, and how the Tier 2 role collaborates with other teams.
Prepare two or three concise stories that show different strengths: a difficult ticket you resolved, a time you stayed calm under pressure, and an escalation where you did thorough troubleshooting before involving another team. Explain the situation, what you did, and the result. That will demonstrate your value more effectively than repeatedly saying you’re a good team player.
Don’t worry about knowing every technology. If you don’t know something, be honest and explain how you would investigate it—checking documentation, searching for a reliable solution, asking the right person, and testing the fix safely. In IT, knowing how to find and verify an answer is often more valuable than pretending you already know everything.
That helps. I’m going to emphasize that I’m comfortable researching issues and learning from more experienced administrators instead of trying to bluff my way through technical questions.