Could someone tell me the red flags to look out for an IT Job?

Could someone tell me the red flags to look out for an IT Job?

Why women love us:

  • Daily articles on career topics
  • Jobs at companies dedicated to hiring more women
  • Advice and support from an authentic community
  • Events that help you level up in your career
  • Free membership, always

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.

5 Comments

Join the conversation
  1. Anonymous

    Short answer: if the place smells like panic and duct tape, run. Longer answer, with fewer sirens.

    A big red flag is “hero culture.” If they brag that people “wear many hats” and “do whatever it takes,” that usually means chronic understaffing and burnout dressed up as grit. Healthy IT runs on processes, not martyrs.

    Another is no documentation. If everything lives in one bloke’s head and that bloke is permanently on holiday or about to rage-quit, you’re walking into a knowledge black hole. Systems without documentation are systems powered by vibes.

    Watch for vague job descriptions. If the role says “IT support / systems / security / cloud / other duties as assigned,” you’re not joining a team, you’re becoming a sponge. Clarity is respect.

    Constant firefighting is a classic warning sign. Some incidents are normal; living in Sev-1 mode is not. If they’re proud of how often production goes down, that’s not resilience, that’s dysfunction with a badge.

    Outdated or unsupported systems with zero upgrade plan. Legacy tech can be fine if there’s a roadmap. If the roadmap is “we’ve always done it this way,” congratulations, you’re now a digital archaeologist.

    Pay attention to how they talk about users. If IT openly despises clinicians, staff, or customers, that’s a cultural rot. Good IT complains privately and designs better systems publicly.

    Another quiet killer: no change management. If changes go straight to prod on a Friday afternoon because “it’ll be fine,” it won’t be. That’s how weekends get eaten.

    Security as an afterthought is a huge red flag. If passwords are shared, MFA is “too annoying,” or audits are treated like a nuisance, you’re one breach away from a very bad year.

    Finally, high turnover with awkward explanations. If everyone you’d rely on has left in the last year and management blames “the new generation,” the problem is not the generation.

    A decent IT job feels boring in the best way: clear scope, calm systems, adults in charge, and crises that are occasional—not a lifestyle. That’s the gold standard, and it does exist, despite rumours to the contrary.

  2. Anonymous

    Look for how they treat the Help Desk staff (the first line of defense). If they are blaming tech support for network issues - run, don't walk.

    One other thing, I spent over 20 years supporting IT in law firms (the pay is great but should include combat pay since that is what it feels like), they tend to be unforgiving. If there is an equipment failure or any type of outage, they want to see heads roll (firings).

  3. Evelyn Livant

    I missed some red flags — when I interviewed for a position, one of the interviewers had really dumb questions like “do you know what a database is?”

    I took the position and wound up regretting it.

    I figured out how to get a good reference and moved on.

    Honestly, trust your instincts.

  4. Anonymous

    Understand their application testing process - not software dev testing but actual testing of Applications and patching process. Who are the testers - Business Users or someone in IT Applications? - Can you have access to the Business testers as needed or is there always a roadblock t their ability to test ? Who manages the test scripts - How often are the updated? Where are they stored?

    As one person already stated. Where are processes, Procedures, work instructions for systems stored? Formal repository or in someone's hard drive or brain or even desk drawer? How is SaaS systems purchased and managed? Can anyone just make purchases or is it managed in one area so it minimize risk of data security or leakage. Also regulated allows for one system to perform the same function across the entire company instead of several SaaS products duplicating each other.

    Also stated by another person - how many legacy systems do they have and what is the path forward to consolidate or update?

    What version of their current systems are they using? I would be suspicious of companies who are at least 5 to 6 versions behind. What is the current patching process if on Prem - SaaS systems you have to take as they come - you don't get to delay.

    Change management is another item - what is the process, do they have a Change Approval Board - How often does it meet? How are reports/dashboards created/managed - is it the business telling IT what to do or is there a partnership. Does IT have a seat at the table with each business unit to help them find solutions to their IT needs?

    What operating system are they using - Windows 10 and older - means they have security vulnerabilities.

    Do they have a Governance, Risk and Compliance area - if not, how is it handled - who manages it? How do they identify and manage Segregation of Duties Conflicts? How are access approvals managed/handled? - Is there a system documented approval form/workflow /policy?

  5. Anonymous

    Thank you all for your comments

Browse recent posts

Fairygodboss VIP
Achieve your career goals.
Be part of the largest online career community for women to find jobs, advice, and support — for free.
Fairygodboss members