Information Technology Manager (IT Manager) Interview Questions
For IT managers responsible for a department's technology services and staff. Interviews focus on service priorities, team assignments, vendors, budgets and reliable systems.
30 questions, ranked by what the job needs most
In other fields: Network and Computer Systems Administrators · Computer Systems Analysts · Web Administrators · compare them →
Information Technology Manager (IT Manager) in 3 other fields →
Print the top 10:Scoring sheetPractice sheet
Question 1: Describe a time you reset your IT department's daily priorities when support requests threatened planned work.
Example answerThe interviewer wants to know whether you can set workable IT priorities when daily support demand competes with planned work.
Build your answer around one disrupted day. Explain the support problem, the commitments at risk and your responsibility for the department's plan. Spend most of the answer on the decisions you made about coverage, deadlines and communication. End with what happened to both the urgent requests and the work you deferred.
For example: "A login problem filled our support queue while the team was preparing an equipment rollout. I moved an analyst onto the login issue and kept one technician on rollout preparation. I told the department expecting the rollout which work would move and confirmed a revised schedule. Users regained access, and we finished the rollout on the revised date. I learned to leave more room in our daily plan for support demand."
Avoid listing every ticket, claiming that everything was equally urgent or describing only what the team did without identifying your decisions.
Interviewer tipA strong example names the service impact, the work they moved and the result. Simply telling the team to work faster avoids the priority decision.
Candidate tipChoose a day when support demand disrupted the plan. Explain what you moved, what you protected and how the department handled the remaining work.
Question 2: How do you manage IT staff assignments from the initial handoff through review of the finished work?
Example answerThe interviewer wants to understand how you give IT staff clear ownership and check that assigned work meets the need.
Organize your answer around the life of one typical assignment. Cover how you match the work to a staff member, explain the expected result and agree on when to check progress. Then describe how your review changes with the assignment's complexity or risk. A brief example makes the process easier to follow.
For example: "For an access setup request, I check the scope and assign someone familiar with that system. I give them the authorized access details and the completion date. If the request is unusual, we discuss the uncertain parts before they start. Before closing it, I review the access granted against the request and confirm the user can do the required work. If something is missing, the assignment stays open."
Avoid treating assignment as simply forwarding a ticket, taking credit for the technician's work or assuming that a closed status proves the request was met.
Interviewer tipListen for clear ownership, a definition of finished work and review suited to the assignment's risk. Closing work without checking that it meets the request is a warning sign.
Candidate tipWalk through an IT assignment from matching it to a staff member to accepting the result. Name the information you provide and the checks you use before closing it.
Question 3: Share an example of how you turned conflicting requests from department heads into clear requirements for an IT system.
Example answerThe interviewer wants to learn how you turn competing department requests into requirements an IT team can use.
Choose one system request where the disagreement affected the requirements. Set out what each department needed and your role in the discussions. Explain how you clarified the underlying work, resolved unclear priorities and checked the written requirements with the people who would use the system. Finish with the result.
For example: "Two department heads wanted different information on a shared request form. I met with their users to trace how each field would be used. We found that some information was needed only for one type of request. I wrote requirements for a common form with extra fields for that request type and reviewed examples with both departments. They agreed that the requirements covered their work, so the team could estimate the change without guessing."
Avoid portraying disagreement as a personality problem, presenting a feature list without business needs or saying that you satisfied everyone without showing how requirements were confirmed.
Interviewer tipListen for the candidate's own work with department heads to separate business needs from preferred features. Choosing the loudest request without checking its impact is a concern.
Candidate tipUse one system request with competing needs. Describe the discussions you led, the requirements you clarified and how the departments confirmed the resulting requirements.
Question 4: Tell me how you worked with a technology vendor to resolve a service problem affecting your department's users.
Example answerThe interviewer wants to see how you work with a vendor to get an IT service problem resolved for users.
Use one real incident involving a vendor you dealt with directly. Briefly explain the affected service and your responsibility. Describe the information you brought to the conversation, the action you asked the vendor to take and how you followed up on commitments. Close with the outcome users experienced and anything you learned about managing that relationship.
For example: "Users kept losing access to a hosted reporting service. I collected the times and error messages from our support tickets and reviewed them with the vendor's service lead. We agreed on a test window and an update schedule. I arranged for affected users to test the vendor's correction and kept the department heads informed. Access stabilized after the change, and I kept the issue open until we had checked normal use."
Avoid blaming the vendor, giving only a technical diagnosis or describing escalation without explaining what you did to secure a resolution.
Interviewer tipThe example should show facts shared with the vendor, an agreed next step and follow-through for users. Blaming the vendor without pursuing a resolution is a red flag.
Candidate tipPick a vendor service problem you helped resolve. Focus on your conversations, the commitments you secured and what changed for the affected users.
Question 5: Walk me through a time you corrected a weakness in your IT department's backup process.
Example answerThe interviewer wants to know whether you can manage a backup weakness through to a credible recovery check.
Choose a weakness you actually helped correct. Explain what was missing or unreliable, the data involved and your responsibility for the backup process. Focus on the actions you directed or took, then describe how you checked the change. End with the result and what you learned about maintaining backup coverage.
For example: "We found that a new shared folder was outside our scheduled backups. I had the team check the backup scope against the folders we supported and added the missing location. I arranged a restore to a separate test location so we could check the files without changing the working folder. The restored files opened correctly. I also added a backup coverage check to our process for setting up shared storage."
Avoid confusing a completed backup with a tested recovery, claiming that backups eliminate every risk or spending the whole answer on software settings rather than your management actions.
Interviewer tipLook for what the manager changed and how they checked that needed data could be recovered. Treating a successful backup message as proof of recovery is a warning sign.
Candidate tipChoose a real backup weakness, such as missing coverage or an unreliable recovery step. Explain your management actions and the recovery checks that showed whether the change worked.
Question 6: Give an example of how you kept recurring IT service costs within your department's operating budget.
Example answerThe interviewer wants to understand how you control recurring IT spending while considering the services users need.
Pick a budget period with a specific cost pressure. Briefly explain the services involved and your spending responsibility. Show how you reviewed recurring charges, chose an action and checked its effect. Close with the spending result and any service consequences you observed. Use actual figures only if you know them and can share them.
For example: "Our software renewals were putting pressure on the operating budget. I compared the renewal list with current staff assignments and checked with department heads before removing unused accounts. I also confirmed which shared functions still needed access. We renewed the accounts people needed and brought the recurring charges back within our planned spending. I added an account review ahead of each renewal so the same issue would be easier to catch."
Avoid claiming savings you cannot support, treating every subscription as unnecessary or describing cost cuts without considering the work those services support.
Interviewer tipLook for costs they tracked, a spending decision they owned and its effect on service. Dropping needed services without considering user impact is a red flag.
Candidate tipChoose a budget period with a real cost pressure. Explain which recurring charges you reviewed, what you changed and how spending and service were affected.
Question 7: Describe a time you addressed a skills gap on your IT team through hiring or staff training.
Example answerThe interviewer wants to learn how you connect IT staffing or training decisions to a real gap in the team's capabilities.
Choose a skills gap that affected work your team needed to handle. Explain how you recognized it and your role in deciding whether to hire or train. Describe the action you took and how the team's ability to do the work changed. Keep your answer focused on your decisions rather than the entire hiring or training program.
For example: "Only one analyst knew how to administer our file access groups, which made coverage difficult. I arranged for another technician to train with that analyst using ordinary access requests. I protected time for the training and reviewed early assignments with them. The technician became able to handle routine requests without waiting for the analyst, and unusual cases still went to the more experienced person."
Avoid presenting training attendance as proof of skill, criticizing an employee personally or claiming the team gained capabilities you never observed.
Interviewer tipA strong answer connects a specific service need to a hiring or training decision and its result. Training with no connection to the team's work misses the skills gap.
Candidate tipName the capability your team lacked and the work it affected. Explain your part in hiring or training and what the team could handle afterward.
Question 8: Talk about a technology upgrade you recommended to solve a recurring problem for your department's users.
Example answerThe interviewer wants to see whether your technology recommendations start with a user problem and lead to a useful decision.
Choose an upgrade you personally recommended. Explain the recurring problem, the information you used to understand it and why the proposed change fit. Describe how you presented the recommendation and what happened next. If the upgrade was not adopted, explain that honestly and keep the outcome within what you observed.
For example: "Staff kept reporting that their older laptops froze during video meetings. I reviewed the support records and compared the affected machines with ones that handled the same work reliably. I recommended replacing the machines that could no longer support the workload rather than replacing every laptop. Management approved a staged purchase. After the first replacements, the affected users stopped reporting that meeting problem."
Avoid choosing an example only because the equipment was new, skipping the recurring user problem or promising benefits that you did not check after the decision.
Interviewer tipListen for the user problem, the reason this upgrade fit and the outcome the candidate observed. Recommending newer technology without a business need is a concern.
Candidate tipPick an upgrade you actually recommended. Connect the recurring user problem to your recommendation, then explain the decision and any outcome you could observe.
Question 9: Tell me about an IT policy you wrote or interpreted for a department's request.
Example answerThe interviewer wants to learn how you turn a department's request into clear IT policy or a sound interpretation of an existing rule.
Use Situation, Task, Action, Result. Explain the request and the policy issue it raised. Describe the wording you wrote or clarified, the authority you had and how you communicated the decision. End with the result rather than stopping at the policy document.
For example: "A department needed specialized software, but our installation policy did not explain how to request it. I managed that policy, so I worked with the department and our support team to define the information needed for a review. I added a request route and explained when installation could begin. The department submitted the missing details, and we reviewed its request without treating urgency as permission to install first."
Avoid assuming the IT manager always owns the policy, describing someone else's decision as your own or claiming that a business need automatically overrides a restriction.
Interviewer tipListen for how they turned a department's need into clear policy or guidance within their authority. Treating a request as permission to bypass the policy is a red flag.
Candidate tipExplain the department's request, the policy wording you developed or clarified, your authority to decide and the result. IT means information technology; keep the example about your own policy work.
Question 10: Give an example of an IT operations report you used to show management where service was falling short.
Example answerThe interviewer wants to learn how you turn an IT operations report into a clear account of a service shortfall.
Choose a report you prepared or reviewed and identify the service issue it showed. Explain how you checked your interpretation and presented the finding to management. Focus on the part you played in making the issue understandable. Finish with what management understood or decided, without claiming a later improvement you did not observe.
For example: "Our support report showed that older tickets were staying open even though the total queue looked stable. I checked a sample and found that requests needing another team's input were waiting between handoffs. I showed management the aging categories and examples without user details. That made the delay visible, and management agreed that the handoff needed attention. We assigned someone to follow up on those waiting requests."
Avoid reading out every number, hiding weak service results behind overall totals or claiming that producing the report alone solved the service problem.
Interviewer tipListen for how they interpreted service results and made the shortfall clear to management. Hiding poor results or presenting numbers without explaining them is a red flag.
Candidate tipChoose a report you prepared or reviewed. Explain the service shortfall it showed, how you presented it and what management understood or decided as a result.
Question 11: How do you prioritize when urgent support issues, planned projects and new requests from departments all compete for your team's time?
Example answerThe interviewer wants to see how you balance keeping systems running with delivering projects and serving the business. Start with the method you use, then show it in a recent example. Many IT leaders rank work by business impact, risk and effort, protect time for urgent support, and run new requests through an intake process so they are visible and easy to compare. Sample: "Outages and security issues come first, and I keep part of the team's capacity for support so projects don't stall every time something breaks. Planned projects follow the priorities we agree with department heads each quarter. New requests go into a shared queue that I review weekly with the requesters' managers. Last spring, marketing asked for a new reporting tool in the middle of our network upgrade. I showed them what each choice would delay, and we agreed to start their tool after the upgrade, with a simple workaround in the meantime." Pitfalls to avoid: claiming you handle everything at once, setting priorities alone without the business, and failing to tell people what has to wait.
Interviewer tipLook for a clear method, such as ranking by business impact and risk, and a way to tell requesters what has to wait. Saying yes to everything is a red flag.
Candidate tipDescribe the method you use, like an intake process or ranking by impact, and give a recent example of a tradeoff you made and how you explained it.
Question 12: Walk me through how you coordinated a software rollout to keep it on plan.
Interviewer tipA strong example shows how the candidate kept the rollout on track by checking that teams were ready for each handoff. Marking a milestone complete while required work is unfinished is a red flag.
Candidate tipPick a rollout with a handoff that could have put the schedule at risk. Name who had to finish what, how you tracked the handoff against the plan and whether the rollout stayed on schedule.
Question 13: Walk me through how you planned data security and recovery for a business system your team built.
Interviewer tipListen for how the candidate's decisions about access and recovery fit the system's role in the business. Leaving recovery planning until after the system goes live is a red flag.
Candidate tipName the business need behind the system and the decisions you made about who could access its data and how it could be recovered. Close with what testing or rollout showed.
Question 14: Tell me about a time you brought together developers, business users and vendors to deliver an IT project.
Example answerThe interviewer wants to see how you get groups with different goals, such as developers, business users and vendors, to work as one team. Use Situation, Task, Action, Result: the project, who was involved and what each group needed, what you did to keep them aligned, and what the project delivered. Sample: "We were replacing our inventory system, which involved our developers, warehouse supervisors, the finance team and the software vendor. Early on, each group had its own idea of what came first. I ran a kickoff where we agreed on a shared goal and a clear owner for each part, then held a short weekly meeting with one person from each group. When the vendor and our developers disagreed about who would build a data connection, I brought them together to settle it that week. The system went live on the planned date, and the warehouse team said they felt heard throughout." Pitfalls to avoid: blaming one group for every problem, describing only your own tasks, and skipping the result.
Interviewer tipStrong answers show how they set a shared goal, gave each group a clear role and kept them talking, for example through regular check-ins. Blaming one group for every delay is a red flag.
Candidate tipPick a project with several groups involved. Say who they were, what each needed, how you kept them aligned, and what the project delivered.
Question 15: What do you find hardest about managing an IT budget, with costs like software licenses, cloud services and hardware refreshes competing for the same money?
Example answerThe interviewer wants to see that you understand how IT money is actually spent and that you plan for the costs that are hard to predict. Name one real difficulty, explain why it is hard, and show how you manage it with an example. Common answers include cloud costs that change with usage, license renewals that rise over time, and deciding when to replace aging hardware. Sample: "The hardest part for me is cloud spending, because it grows with use and the bill can surprise everyone. In my last role, I worked with finance to set monthly targets for each major system and set up alerts when spending ran ahead of plan. When one alert showed a test environment running all weekend, we started shutting it down after hours. I also review license counts before each renewal, since unused seats add up quietly." Pitfalls to avoid: saying budgeting is never hard, talking only in general terms about cutting costs, and leaving out how you work with finance.
Interviewer tipA strong answer names a real tension, such as cloud spend that grows with use, and how they forecast and track it. Vague talk about keeping costs down is a red flag.
Candidate tipPick one real difficulty, like predicting cloud usage or timing a hardware refresh, and explain how you forecast it, tracked it during the year and adjusted.
Question 16: Walk me through how you set and track performance expectations for the programmers and systems analysts on your team.
Example answerThe interviewer wants to know how you guide technical staff so that work is clear, measured fairly and improved over time. Describe your process from start to finish, then give a short example. Cover how you agree on goals, what you check along the way, and what you do when someone falls behind. Sample: "At the start of each quarter, I meet with each programmer and analyst to agree on two or three goals tied to our project plan, such as delivering a feature or reducing defects in their area. I review progress in weekly one-on-ones and look at code reviews, missed dates and feedback from users. When one developer kept missing sprint commitments, we found they were being pulled into support work. I routed those requests to the help desk, and their delivery improved within a couple of sprints." Pitfalls to avoid: measuring people only by hours or lines of code, waiting for the annual review to raise problems, and describing goals without saying how you check them.
Interviewer tipLook for concrete measures, such as code review quality, ticket resolution or delivery dates, plus regular one-on-ones. Judging people only by hours logged or lines of code is a red flag.
Candidate tipDescribe how you agree on goals at the start, what you check along the way, such as code reviews or sprint results, and what you do when someone slips.
Question 17: Walk me through a long-range technology plan you developed, from setting its goals to putting it into practice.
Example answerThe interviewer wants to see whether you can plan technology years ahead and actually carry the plan out. Walk through it in order: the business goals behind the plan, how you built it and won support, the main steps, and how you tracked progress and adjusted. Sample: "When I joined my last company, most systems ran on aging servers in our own building. I met with department heads to learn their plans for the next few years, then wrote a multi-year plan to move key systems to the cloud, retire old applications and improve backups. I presented the costs and risks to the leadership team, and they funded the first phase. We moved email and file storage first because they were simpler, then tackled the finance system. When a vendor delay pushed one step back, I updated the plan and shared the change at our quarterly review." Pitfalls to avoid: describing a plan with no link to business goals, skipping how you got funding and buy-in, and presenting the plan as if nothing ever changed.
Interviewer tipStrong answers tie the plan to business goals, show how they won funding and buy-in, and note what changed along the way. A plan that was never revisited is a red flag.
Candidate tipPick a real plan, such as moving systems to the cloud. Explain the business goals behind it, the main steps, how you tracked progress and where it stands now.
Question 18: Tell me about a time you compared several systems or vendors and used the evidence to choose the best one for your organization.
Example answerThe interviewer wants to see how you make a technology choice based on evidence instead of habit or a sales pitch. Use Situation, Task, Action, Result: the need, the options, the criteria and data you used, who you involved, and how the choice held up. Sample: "Our help desk ticketing tool was going out of support, so I led the search for a replacement. With the help desk lead and two department heads, we agreed on criteria first: cost over several years, security, how well it connected to our directory and email, and ease of use. We shortlisted three products, ran a short trial of each with real tickets, and checked references with other customers. The cheapest option failed our security review, so we chose the second. After launch, technicians said tickets were easier to route, and we retired the old tool on schedule." Pitfalls to avoid: picking a tool only because you already knew it, leaving users out of the evaluation, and skipping what happened after go-live.
Interviewer tipListen for clear criteria such as cost, security, fit and support, plus input from users. Picking a tool only because it was familiar is a red flag.
Candidate tipName the options you compared, the criteria and data you used, who you consulted, and how the choice worked out after it went live.
Question 19: Tell me about a time your advice to senior leaders on a technology decision led to a better outcome for the organization.
Example answerThe interviewer wants to know whether senior leaders can trust your judgment, and whether you can explain technical issues in business terms. Use Situation, Task, Action, Result. Describe the decision leaders faced, the advice you gave and why, how you handled questions or pushback, and the outcome. Sample: "Our leadership team wanted to launch a new customer portal before the holiday season. In testing, my team found that the login system couldn't handle the expected traffic. I met with the executive sponsor and explained the risk in terms of lost sales and support calls rather than server details. I recommended a smaller launch for existing customers first, with the full launch a month later. Marketing pushed back because a campaign was already planned, so I offered a plan that kept part of it. The limited launch went smoothly, and we fixed two problems before the full rollout." Pitfalls to avoid: using jargon leaders can't follow, taking sole credit for a team decision, and choosing a story where your advice made no real difference.
Interviewer tipListen for how they put a technical issue in business terms, such as cost, risk or downtime, and handled pushback. Taking sole credit for a team decision is a red flag.
Candidate tipChoose a decision you influenced, like delaying a launch or replacing a system. Explain the options, the case you made in plain business terms, and what happened.
Question 20: Tell me about a time you had to tell senior leaders that an IT project would be late, over budget or short of what was promised.
Example answerThe interviewer wants to know whether you raise bad news early and honestly, and whether you bring options instead of only problems. Use Situation, Task, Action, Result. Set up the project and what was promised, explain when and how you learned it was slipping, describe how you told leadership and what choices you offered, then say what happened. Sample: "We were moving our payroll system to a new vendor, and two months before go-live my team found that data from the old system was much messier than expected. I confirmed the size of the problem with the vendor, then met the CFO and COO that week rather than waiting for the monthly review. I explained the cause and gave three options: cut scope, add contractor help, or move the date, with the cost and risk of each. I recommended a delay and explained what we would need to confirm before setting a new date." End with the decision leaders actually made and the result you can support from your own experience. Pitfalls to avoid: waiting until the deadline to speak up, blaming the vendor or your team, and arriving with no options or recommendation.
Interviewer tipA strong answer shows they raised the problem early, came with facts and options, and owned their part. Holding the news until the deadline is a red flag.
Candidate tipExplain how you found out, how soon you told leadership, what options you brought, and how the project went after that conversation.
Question 21: Tell me about the last time you helped a user get back to work when a business application stopped working.
Interviewer tipA good answer connects the steps they took to the trouble the user reported. Closing the support ticket without checking whether the user can finish the task is a red flag.
Candidate tipSet up the task the user was trying to finish. Explain how you narrowed down the problem, describe the help you provided, and say how you knew the user could finish the task.
Question 22: How do you keep up with technology changes that could affect the systems your department runs?
Interviewer tipUseful answers name sources the candidate checks regularly and show how they judge whether an update applies to their systems. Relying on sales claims alone is a red flag.
Candidate tipName the sources you follow, such as software release notes or professional groups. Explain how you sort through those updates to find changes that matter to the systems you oversee.
Question 23: Walk me through a time you had to decide whether to sign off on a system design before the team started building it.
Interviewer tipListen for a decision grounded in the design and a clear requirement the system had to meet. Signing off on a known design gap that blocks required work is a red flag.
Candidate tipPick a design you approved or sent back. Describe the requirement you used to make the call, what you saw in the design, and what happened after your decision.
Question 24: Walk me through how you judged whether a proposal for one reporting system could work across several departments.
Interviewer tipA strong answer connects the reporting needs to the data and staff time available. Treat a recommendation based solely on the proposed system's features as a red flag.
Candidate tipPick a proposal where the departments needed different things from their reports. Describe what you checked about the data they had, the work the change would take, and what you recommended.
Question 25: Describe how you coached someone on your IT team, such as a junior developer or help desk technician, to grow their skills.
Interviewer tipA strong answer shows a plan: a skill gap they spotted, regular check-ins, and stretch work such as leading a small project. Coaching that was only fixing the person's mistakes is a red flag.
Candidate tipName the person's role and the skill they needed, what you did over time, like pairing or handing them ownership of a task, and a concrete sign they improved.
Question 26: Tell me about a time you dealt with a difficult stakeholder, such as a department head or vendor, during an IT project or outage.
Interviewer tipListen for whether they tried to understand the person's concern, kept the work moving and knew when to escalate. Describing the other person with contempt is a red flag.
Candidate tipDescribe what made the person difficult and what was at stake, what you did to understand their view, and how you reached a workable result.
Question 27: How do you use data such as help desk tickets, system uptime or project metrics to make decisions about your IT department?
Interviewer tipA strong answer names specific measures and a decision they changed, like adding staff after ticket volume rose. Collecting reports no one acts on is a red flag.
Candidate tipName the measures you track, how often you review them, and give one example where the numbers led you to change something.
Question 28: In your experience, what is the key to developing a good team?
Example answerThe interviewer wants to know what you believe makes a team work, and whether you have acted on that belief.
Name one or two keys, such as clear roles, trust, or regular honest feedback. Then back them up with a short example from a team you led or belonged to, and say what changed.
Sample answer: "For me, the key is trust built on clear roles. On one team I joined, two people kept doing the same tasks while other work went undone, and it caused friction. I suggested we list who owned each part of our weekly work and review it at a short Monday meeting. Once everyone knew what they owned, people started asking each other for help instead of complaining. Within a month we stopped missing handoffs, and the meetings got shorter."
Pitfalls: Don't give a list of buzzwords with no example. Avoid taking all the credit for the team's success. If you were a team member, don't describe only what the manager should have done.
Interviewer tipLook for how they build mutual trust, respect, and cooperation.
Candidate tipBe sure to explain how you encourage and build trust, respect, and cooperation.
Question 29: How do you check that your department's software use meets the terms of its licenses?
Interviewer tipListen for a comparison of actual use or assigned accounts with the terms for that software. Assuming an active subscription covers everyone who uses it is a red flag.
Candidate tipExplain which license terms matter for the software you manage, such as who can use it. Describe which records you compare with those terms and how you handle any mismatch you find.
Question 30: Tell me about your last experience recruiting, interviewing, or hiring an employee. What techniques did you find most effective in finding the right person for the job?
Example answerThe interviewer wants to see that you can find the right person for a role in a fair, organized way.
Use Situation, Task, Action, Result. Describe the role you were filling, how you defined what the job needed, the techniques you used to screen and interview, and how the hire worked out. Say which technique helped most.
Sample answer: "I helped my manager hire a new team member last spring. Before posting the job, we listed the three skills that mattered most and wrote interview questions for each one. Every candidate got the same questions, and we scored the answers separately before comparing notes. We also asked the top two candidates to do a short work sample. The structured questions helped us compare people fairly, and the person we hired was working on their own within a few weeks."
Pitfalls: Don't describe hiring on gut feeling alone. Avoid any mention of personal traits that have nothing to do with the job. Don't skip how the hire turned out.
New to interviews? Start with the common questions every interview asks →