If you're interviewing for a tech role, here's a fast way to tank your chances: walk in and immediately trash the company's systems. You know the move. "Honestly, your system is outdated. I'd replace it with something better." It feels confident. Like you're demonstrating vision and technical chops. But to the people across the table? It usually just sounds arrogant. Why this backfires When you critique infrastructure without context, you're not showing expertise and you are showing you don't understand how businesses actually work. That "outdated" system you're eager to scrap? It might be running payroll for thousands of employees. It could be the backbone of compliance reporting that keeps the company legally covered. It represents years of investment and decisions made under constraints you know nothing about. The people interviewing you probably built it, maintain it, or depend on it. When you dismiss it out of hand, you're not just criticizing code—you're dismissing their work and their reality. What to say instead Skip the unsolicited teardown. Lead with curiosity: "I'm curious how your team thinks about modernization, especially when balancing business continuity and innovation." You're still signaling strategic thinking. But now you're inviting conversation instead of passing judgment. How this plays out Two candidates. Same senior engineering role. Candidate A: "This tech stack is old. I'd rebuild it using modern tools." Candidate B: "In previous roles, I modernized legacy systems without disrupting operations. How has your team approached that balance?" Same technical opinion. Completely different delivery. One sounds like a know-it-all. The other sounds like a leader. The takeaway Companies aren't just hiring for technical skill, they are hiring for judgment and the ability to build trust. Great IT candidates don't rush to fix. They ask to understand first. Because your insights only matter if people listen—and people only listen when they feel heard. Innovation isn't just about having the right ideas. It's about earning the credibility to implement them.
Founder & Chief Human Capital Strategist at Blue Spruce Human Capital Advisory
Answered 2 months ago
The one phrase candidates should stop using in interviews? "I was responsible for..." It's technically fine. But it's forgettable. "Responsible for" describes a job description. It doesn't describe impact. And in today's environment — where companies are focused on disciplined execution, stronger customer relationships, and sustainable growth — impact is what matters. Instead, try this structure: "I led [initiative] that delivered [measurable result] by [specific action]." That shift moves you from passive to accountable. It signals ownership. It shows you understand how your work connects to business outcomes. For example: Weak: "I was responsible for HR during a growth period." Stronger: "I led a workforce redesign during a 30% growth phase, reduced time-to-fill by 22%, and strengthened coverage for our top revenue-generating customers." Now you're not just describing a function — you're demonstrating how you drove performance. In my work advising boards and leading human capital strategy, I see this distinction constantly. Organizations aren't looking for caretakers. They're looking for operators who can deepen customer partnerships, execute relentlessly, and scale sustainably. Language shapes perception. When candidates speak in terms of outcomes, metrics, and enterprise value, they position themselves not as functional leaders — but as strategic growth partners. And that's who gets hired.
My name is Phil Santoro and I am a Co-Founder of the startup studio Wilbur Labs. We identify unsolved customer problems and build companies to solve them. Since 2016, we have built and invested in over 21 technology companies, so I interview and hire a lot. One specific phrase I advise candidates to avoid is "I am a quick learner." Although being a quick learner seems like a positive trait, it is very vague and offers the interviewer no tangible proof of your abilities. It's best to provide specific instances that show your ability to learn new ideas, skills, techniques, etc., relatively quickly. Instead of a generic claim like "I am a quick learner", you can tell a story where you demonstrate the ability. For example, you could say something like "In my previous role, I was able to become proficient with our new CRM system in only 2 weeks, which allowed me to onboard new clients at a rate 30% faster than anyone else on the team. I started hosting office hours once per week to help my colleagues after a few were struggling with the transition." Providing a clear, measurable example of how you applied a new skill will always make a stronger impression than a generic promise.
I wish applicants would stop defining themselves by their current job title and years of experience. A lot of introductions still sound like this: "I'm a [Job Title] at [Company], where I specialise in [Field]." "I'm a Marketing Manager at a mid-sized SaaS company, where I've spent the last three years leading digital campaigns, analysing performance data, and collaborating closely with sales and product teams." Is it an immediate red flag? No. Stale and forgettable? Absolutely. In almost any interview, the employer is going to ask you "tell me a bit about yourself." That's your biggest opportunity to pitch your skills as the solution to the hiring manager's needs. It's hard to do that if you open with a self-focused summary of your role and area of expertise. Whether they're an external recruiter or the employer themselves, the person sitting opposite you has already read your CV. They know what you do and how long you've been doing it. What they want from the interview is a clear sense of who you are and the value you'll bring to the team. So don't talk about your current job or proudest achievements — highlight what you can do for this specific employer. "I'm a [Professional Title], and I help organisations like yours achieve [meaningful result]." Before the interview, choose a professional title that aligns with the employer's needs while accurately reflecting your experience. For example, I'm a professional CV writer and careers specialist, but I also have a background in marketing and journalism, so depending on the role, I could pitch myself as a career coach, a writer, or a digital strategist — and that title choice will have an immediate influence over how the interviewer perceives me. The same goes for your "meaningful result." Reflect on the strengths you highlighted in your CV. Which one got you the interview? Turn those strengths into promises that make the employer lean in and take interest. For example: "I'm a careers writer, and I help organisations like yours produce unique resources that jobseekers actually read and return to."
It's not one specific phrase but the importance of being mindful of how and when you use "I" versus "we" when describing your work. As leaders we naturally default to "we" because we value collaboration and want to recognize our teams. That matters. But in an interview the hiring manager or recruiter is trying to understand your direct impact. Your decisions. Your influence. Your role in driving outcomes. If you continuously say "we," it can unintentionally blur your contribution. For example if you are sharing the following, "We redesigned our onboarding program and saw great engagement." You could consider saying "I led the redesign of our onboarding program, partnering closely with my team and other hiring leaders. As a result we were able to increase engagement by 30% and we reduced our time to productivity." This ensures you are still giving credit to your team but you are also clearly owning your role in the work. That clarity helps interviewers truly understand the value and contributions you will bring to their company.
Skip saying "Sorry, I'm really nervous" in interviews. I've had candidates say this, and while I truly get it, it pulls focus away from what they're good at. The people who stand out aren't always the most confident, yet they know how to keep control of the moment. Better response would be "That's a great question. Give me a few seconds to think about it." You sound calm, you buy yourself time, and you stay in control. I had a candidate use that exact line once. Paused, collected their thoughts, then gave a sharp answer. They got a second round invite. In my experience, candidates don't realize how much presence matters. Sometimes more than the actual answer.
I say this as an executive headhunter and recruiter for over 20 years. Many candidates get very excited when the role and company is a great match for their profile and experiences. So they often fall into the trap of telling a recruiter or company interviewer that they are "a perfect fit for the role." This demonstrates that a person may be too emotional, and lose sight of rational logic, as no one is a perfect match. And specifically with executive recruiters, the clients are looking for a needle in a haystack, and it is almost impossible to deliver on all the things that would make a candidate perfect. In fact, after over 10,000 interviews with executives and about 500+ candidates who have said they are a perfect fit, I have never found one to be, and worse, they are usually below average compared to the top 10 candidates whom I interview for the same role. A better way for a candidate to describe that emotional excitement towards a role would be the following: "I read the job description and know the industry and this company well. Although there is no perfect candidate, I check most of the boxes/requirements, and I'm excited to have you explore my experiences and background to see if I align with what you are looking for." It shows enthusiasm as well as practicality.
Any phrase that points to personality or character could be open for interpretation. For example, if the interviewer asks you to describe a weakness, a phrase like "I'm a perfectionist, isn't likely to land well. This is a trait one cannot change, so if the interviewer views perfectionism as a crutch, there's little chance of advancing through the interview process. It's always better to be well-versed in the particulars of the position description and choose a 'weakness' that can be improved or corrected shortly after hire. For example, the position description might ask for proficiency in Salesforce. The interviewee might not have this experience but they used Hubspot in the past. Their answer might then be "Im unfamiliar with the Salesforce platform; however, I have deep experience with Hubspot and am a quick study, so give me 30days and it will ne a non issue." Happy to elaborate, Heather
"How soon can I get promoted?" This is a terrible question to ask in an interview because of the numerous red flags it raises in the interviewer's mind. The applicant thinks they're showing ambition, but the interviewer is thinking other things. They don't want the job they are applying for. They are way ahead of the process. They are conceited. They are demanding. An alternative phrase for an ambitious job seeker is to ask about career development opportunities. For example, "If I work hard and do my best to contribute to the strength of the organization, are there opportunities for growth and advancement?" Notice the applicant first wants to make a contribution. That's the type of mindset that will win over interviewers.
Stop saying "I'm a team player" because every single candidate says that exact same thing. It says nothing to me about what you actually bring to the group or how you work with others. That is a phrase that is overused to the point that my brain tunes it out the second I hear it. What is more effective, however, is to show me a specific example of collaboration. Say "I coordinated with three departments to get our new enrollment system running in half the time we were supposed to" or "I trained four new agents who are now consistently achieving their monthly targets." Those kinds of statements demonstrate that you work well with others without resorting to the generic label. I had a candidate last year who said, "I'm great at teamwork" in her first interview. I asked her to give me an example, and she couldn't think of one off the top of her head. Someone else came in and told me about dividing up her commission with a struggling teammate to keep up morale in a tough quarter. That person got hired.
When asked why they left their last position, candidates should refrain from using the phrase "It wasn't a good fit." This always raises concerns for me as an interviewer of its vagueness and because it avoids accountability. It lacks insight into the candidate's decision-making, self-awareness, or professional growth. A more effective approach is to name the specific professional misalignment and pivot toward what you're seeking next, without assigning blame. For example, "I met and, in several cases, exceeded the goals of the role and was proud of the results we achieved. As organizational priorities evolved, the work gradually shifted away from some of the areas where I was able to contribute most effectively, so I made a thoughtful decision to pursue opportunities where my strengths and experience could have the greatest impact." In this case, the language chosen demonstrates both judgment and self-awareness, and it frames the transition as intentional and is future-forward. From an interviewer stance, the choice to focus on result instead of complaints also carries huge impact.
One phrase candidates should avoid using in interviews is "I'm really passionate about this role." I still hear this general phrase all the time. Sure, it sounds positive, but it's vague. Passion tells an interviewer how you feel, not how you think. It doesn't help them understand your judgment, priorities, or how you approach real work. We don't hire for passion. And if you think about it does any interviewer want someone in front of them who doesn't feel passionate about the roll in some way? It's a dull and useless phrase. A more effective alternative is to replace emotion with evidence of thinking and connecting dots. Instead of saying: "I'm really passionate about this role." Try something like this: "What drew me to this role is the focus on X. In my last position, I worked on Y, where I approached it by doing Z. That experience shaped how I think about this kind of work." The shift is subtle but very important. The first phrase is generic and interchangeable. The second gives the interviewer something concrete to evaluate. It shows how the candidate connects experience to the role and how they make decisions. In interviews, impactful language isn't louder or more confident. It's specific enough to be trusted by the interviewer and the company. My Bio: Gina Dunn is a brand strategist and founder of OG Solutions, where she helps leaders brand themselves and their businesses, with a focus on how to communicate credibility and with intent.
"In general." When a candidate is being interviewed, we are looking for specifics, not generalities. Most [good] interviewers are using situational interviewing techniques - this sounds like, "tell me about a time when..." Many candidates want to be general in their response, but I am always looking for a specific example. When I get a generality, I follow up with, "That's great. Do you have a specific example you can reference?" This is because we can talk about how things could or should be all day long, but we need to know how you actually perform during a situation, circumstance, or on a certain type of tech or during a particular project. The more specific you can be, the more we can picture you sitting in that role, performing at our organization.
One of the things I tell my clients is to avoid the phrase "I'm a people person." The phrase has been repeated so often it no longer signals anything. Every candidate claims it, but interviewers hear it as filler. What actually works is language that reveals how you think about working with others, not that you necessarily enjoy it, but that you've learned to navigate it when it's difficult. Something like acknowledging you've developed the capacity to stay effective with people you don't naturally align with. That signals maturity, self-awareness, and the kind of adaptability organizations actually desperatily need. Interviewers are listening for evidence of judgment and critical thinking. Language that's specific and slightly unexpected creates a different quality of attention. It suggests someone who reflects on experience rather than simply performs confidence based on platitudes. This shift maybe small in words, but it's very significant in impact.
In my experience, any phrases that are canned or overused are absolutely a turn-off for me, including overly generic humor, even if it ends with "I am just kidding." Phrases such as "I go with the flow" or "change management is crucial." These phrases wouldn't work with experienced hiring managers because they don't communicate anything specific. As hiring managers, we need a candidate with strong experience and a strong conviction in their beliefs. What they believe in, what shaped that belief, where there might be gaps, and where they need help with their own personal growth. This helps us understand how deeply they would connect with the business and how well they would align their effort with business priorities. With this approach, we generally find A-players who, surprisingly, don't complain much, never ask for more than business can afford, and are a delight to work with. An example of impactful language is leading with stories, which can be challenging for candidates at the start of their journey. But note, you don't need to overthink stories. Stories are examples of your experience. You don't need to oversell your experience. When you overpitch, experienced hiring managers can sense that from a mile away. Something like: When I started in a leadership role, I had no clue what I was doing. Not even sure why I secured the position, what they saw in me. I had fears about what a leadership role would be. What would my colleagues reporting to me think of me as a leader? The initial days were challenging. But as I settled in, I learned that I don't need to overthink leadership. I just need to humanize the experience a bit and be available when they need me. Obviously, this would be an example of a leadership role where specific subject matter experience is not as critical. But this storytelling style can be applied across most roles that involve communication, transformation, learning, curiosity, attitude, or teamwork. If they have these skills down, it's very likely that they will apply for positions where they are the best fit. A-players just don't overcommit, and they are very clear on what they want in their lives.
Executive Career Management Coach * Recruiter * Resume Writer * Career Keynote Speaker at Career Thinker Inc.
Answered 3 months ago
Why should candidates avoid the phrase "work-life balance" within a job interview? Regardless of the good intentions, what the interviewer really hears is. * Limited availability/flexibility. * Conditional commitment. * Potential performance ceilings. * Future negotiation before value is proven. Even if none of the above is true, what does it really say? * It centers personal needs before business needs. * It signals constraints, not capability. * It raises risk in a hiring decision. * It forces the interviewer to wonder how flexible you will be under pressure. Interviewer's internal reaction: * Will this person push back during crunch time? * Will deadlines turn into boundary conversations? * Will this become an issue six months in? The ruthless truth. Work-life balance is earned, not negotiated upfront. Top performers get flexibility because they deliver. Average performers ask for it because they need protection.
One phrase I always tell candidates to stop using is: "I'm a hard worker." Not because it's wrong, but because it's empty. Everyone says it. By the time an interviewer hears it for the tenth time that day, it's meaningless. It doesn't paint a picture, and it doesn't help them imagine you actually doing the job. A stronger alternative is to show effort through a specific moment. Instead of saying "I'm a hard worker," try something like: "When we were short-staffed last quarter, I rebuilt our onboarding process over a weekend so new hires could ramp faster. It cut training time by two weeks." Same idea, completely different impact. Here's why that matters. Interviews aren't logic tests. They're memory tests. The hiring manager is asking themselves, Can I see this person here? Will I remember them after five more interviews? Vague claims don't stick. Stories do. I once interviewed two candidates back-to-back for a leadership role. One told me, confidently, that they were a hard worker and a team player. The other talked about staying late to coach a struggling teammate before a product launch, even though it meant missing a flight home. Guess who I remembered without checking my notes? Impactful language works because it trades labels for evidence. It shifts you from selling yourself to showing yourself. My advice is simple: if a sentence could be said by almost anyone, rewrite it. Add a detail. Add a decision you made. Add a result that actually happened. That's how you turn a forgettable interview into a compelling one.
I couldn't help but wonder... how many brilliant candidates quietly talk themselves out of jobs before they ever leave the interview room. It usually happens in the smallest way. A throwaway word. A casual shrug in sentence form. "I was just helping with..." "I basically did a bit of..." As both a millennial content manager and someone who's spent years in hiring rooms, I can tell you: "just" is the most dangerous word you can bring into an interview. It shrinks your presence. It edits out your authority. It turns real work into background noise. Because no one builds strategy, drives growth, saves projects, or moves metrics by "just helping." The more effective alternative? Language that claims space. "I led." "I owned." "I built." "I drove results by..." Watch what happens when a sentence grows a spine. Instead of: "I was just helping with blog content and social media." Try: "I owned the blog and social content strategy, building a consistent publishing system that doubled organic traffic and increased inbound leads within six months." Same role. Same reality. Entirely different woman walking out of that sentence. Impactful language doesn't mean exaggerating. It means finally telling the truth in high definition. It connects your actions to outcomes. It signals confidence without arrogance. And from an HR perspective, it answers the only question that really matters: What changed because you were there? Because interviews aren't about proving you were busy. They're about proving you were consequential. And in a job market obsessed with "potential," nothing is more attractive than a candidate who speaks in results—and isn't afraid to own them.
After 20+ years in courtrooms and hundreds of witness preparations, the phrase that kills credibility is "I'm a hard worker." It's empty calories--anyone can say it, and prosecutors taught me that unsupported claims get shredded under cross-examination. When I was Chief Prosecutor of the Narcotics Unit supervising multiple attorneys and detectives, one job candidate told me "I managed simultaneous grand jury investigations in three counties while maintaining a 19-4 trial record on felony firearms cases." I didn't need her to tell me she worked hard--those numbers proved she executed under pressure. She joined our team. The same principle applied when I interviewed expert witnesses for murder trials. The ones who said "I'm thorough" got destroyed on the stand. The ones who said "I processed 847 evidence samples last year with zero chain-of-custody violations" were bulletproof. Prosecutors can't attack documented performance. Replace every personality claim with a number or a specific outcome you personally delivered. "I closed 23 cases last quarter" beats "I'm results-driven" every single time. If you can't quantify your work, you're making the interviewer do the heavy lifting--and in my experience, they won't.
One of the most overused and under-substantiated phrases in interviews is "I'm passionate about..." While genuine enthusiasm matters, this statement has become so commonplace that it rarely resonates with hiring managers seeking substantive insights into your capabilities. A more effective approach involves demonstrating your commitment through actions and investments in your professional development. Rather than claiming passion, say something like: "I've invested significant time advancing my expertise in organizational behavior, including facilitating over 50 workshops on communication effectiveness and continuously researching emerging adult learning methodologies." This approach provides concrete evidence of your dedication. My work in talent development has shown me repeatedly that candidates who back up their interest with demonstrable commitment create lasting impressions. I once advised a candidate who initially said, "I'm passionate about training and development." We refined this to: "I've completed three professional certifications in instructional design, developed a microlearning program adopted by 200+ employees, and regularly attend industry conferences to stay current with evidence-based practices." The interview dynamic changed immediately. Instead of skeptical nods, the hiring panel began asking deeper questions about methodologies and specific projects. Language that demonstrates rather than declares transforms your interview from a series of claims into a compelling narrative of professional growth and tangible contributions.