Red Flags in IT Candidates and What Is Not a Red Flag

Why red flags show up more in IT staffing

IT hiring moves fast and often happens remotely. A requisition can pass from an end client to an MSP, to a prime vendor, to a sub vendor, and sometimes further. Each step adds speed but also distance from the actual person. So the chance of something going wrong is higher than in a local, in person hire.

The good news is that most problems leave signs. If you know what to look for, and you check consistently, you can catch the majority before a submittal or before a start date. Here is what I think every company and vendor should watch.

Identity and interview red flags

Proxy or fake interviews

This is the one everyone in IT staffing has heard about. One person interviews, and a different person shows up to work. Or someone feeds answers off camera. Watch for these signs:

• The candidate refuses video, or the camera is "broken" every time.
• The voice or face on the client interview does not match the screening call.
• Long pauses before every technical answer, eyes moving to another screen, or answers that sound read out.
• A LinkedIn profile that was created very recently, with few connections and no history.

The fix is simple. Use video for every round, compare the person against a government photo ID before submittal, and have the same recruiter join or at least check the client interview recording when possible. On the first day, someone should confirm it is the same person.

Inflated titles and borrowed projects

A resume that says "Lead Architect" for a role where the person was a developer is common. So is a project list copied from a colleague. Ask the candidate to walk through what they personally did. People who did the work give details. People who borrowed the project stay vague. We explain this approach more in how to identify the right IT candidate.

Resume and history red flags

• Inconsistent dates. The resume says one thing, LinkedIn says another, and the candidate tells you a third version on the call.
• Hidden employment gaps. A gap is fine. Hiding it by stretching dates or listing a "consulting" company that does not exist is not.
• Same project, different clients. Identical bullet points under three different employers usually means the content was copied.
• Skills that do not match the timeline. Ten years of experience in a tool that has existed for five is a quick check.

Reference red flags

References are useful, but only when they are real. Be careful when:

• The reference uses a personal email address and cannot give a company one.
• The reference's phone number is the same number as another reference, or the candidate's own.
• The reference cannot say what the candidate's role was, or describes it in the same words as the resume.
• Every reference is a peer, and nobody was a manager or client lead.

Find the reference on LinkedIn, check that they worked at the same company in the same period, and call a main company line if something feels wrong.

Vendor chain red flags

The same candidate submitted by multiple vendors

This happens more often then people think. A candidate gives permission to one vendor, then a second vendor finds the same resume on a job board and submits it without asking. The client sees two submittals and often rejects both. The protection is a signed right to represent for each requisition and end client, collected before submittal. We list this and other items in what to collect before client submittal.

Rate games

Watch for a rate that changes after the interview, a candidate who does not know their own pay rate, or a vendor who will not confirm the employment type. These usually mean there is another layer in the chain that nobody disclosed. Also be careful when the candidate's employer of record changes between the first call and the offer.

Work authorization issues

Authorization that expires before the project ends, a type that does not allow the proposed arrangement, or a candidate who gives a different status each time you ask. Verify the status and the expiry date early, follow your client's rules, and do the formal employment eligibility check at hire as the law requires.

What is NOT a red flag

Being careful should not turn into being unfair. Some things get treated as red flags when they are not, and good candidates get lost because of it.

• An employment gap with an honest reason. Layoffs, family care, health, study, or a long job search are normal parts of a career.
• Short contracts. In IT consulting, three and six month contracts are common. A string of them is often just how contract work looks.
• A career change. A tester moving into business analysis, or a developer moving into data, can bring very useful experience.
• An accent or non native English. Judge whether the person communicates clearly for the role, not how they sound.
• A plain resume. Formatting skill is not the job. Some of the strongest consultants have the weakest resumes.
• Nervousness in an interview. Plenty of capable people are nervous. Look at the substance of the answers.
• Asking about rate and terms early. That is a professional question, not a warning sign.

Also be careful with automated screening. Rules that drop every resume with a gap or a short tenure will remove good people along with the bad ones.

A simple process to check consistently

Red flags matter most when you check them the same way every time. A short routine like this works well:

1. Run the first screening call on video and save notes on what the candidate said about dates, titles and rate.
2. Compare the resume against LinkedIn and ask about any difference directly.
3. Check a government photo ID against the person on the call.
4. Collect a signed right to represent and confirm the rate and employment type in writing.
5. Verify references through company channels, not only the numbers the candidate gives.
6. Confirm identity again on the first day of the engagement.

At iCareTechno we follow these checks for every submittal, and our vendor partners get the notes with the resume.

Written by

Israr Kazmi

Israr Kazmi is the founder of iCareTechno, the IT staffing, recruitment and consulting division of iCareBilling LLC in Chicago. He writes about hiring, vendor relationships and careers in IT.

More about the author