Take the Leap · Module 03/08

Where AI Lies, Breaks, and Stalls

Know what each model gets wrong before you trust it with anything that matters.

There is a version of AI education that skips this module entirely. It talks about what AI can do, gives you ten impressive examples, and sends you off feeling optimistic. That approach is fine for selling courses. It's not fine for preparing you to actually use these tools in your career.

The most important thing a beginner can learn about AI is not where it works. It's where it fails, quietly, confidently, and sometimes in ways that are genuinely hard to spot.

This module is not a scare campaign. The tools are real and useful. But they have specific, documented failure modes that every serious user needs to understand. If you're using AI to research a field you're moving into, help with a job application, or develop your knowledge base, the failures described here are the ones that will actually hurt you.

Hallucinations: the confident wrong answer

"Hallucination" is the term researchers use when an AI model produces text that is factually incorrect but presented as fact. It's not a bug in the way a typo is a bug. It's a structural feature of how large language models work. They generate the next most likely token (the next word, essentially) given everything that came before. Sometimes the most statistically likely sequence of tokens happens to not be true.

The failure mode that catches beginners off guard is that hallucinated content often sounds authoritative. It's grammatically correct. It's specific. It uses real names, real terminology, and real structural patterns. It just isn't true.

The most dangerous hallucination for career-shifters: fake citations and fabricated credentials.

If you ask an AI to "give me three academic papers on the effectiveness of project management certifications," there is a reasonable chance it will give you author names, journal titles, volume numbers, and years, and that some or all of those papers do not exist. The citation looks real. It has all the right parts. Searching for it will fail.

This has caused real problems. Students have submitted essays citing non-existent papers. Professionals have mentioned research in meetings that doesn't exist. In a career context, if you're using AI to build your knowledge of a new field, and you're filling your mental map with fictional research findings, that's a problem.

The fix: Never use an AI-generated citation without verifying it. If you want research on a topic, use Google Scholar, Semantic Scholar, or the actual databases in your field. Use AI to help you understand real research you've found. Don't use it to find research for you.

Made-up statistics

Related but distinct from fake citations: AI models frequently generate plausible-sounding statistics that have no verified source.

"According to recent studies, 78% of career-changers who used AI tools in their job search reduced their application time by over 40%." That sentence sounds like a finding. It might be completely fabricated. The numbers are specific enough to be persuasive. They're also specific enough to be checkable, but most people don't check.

If you're going to quote a statistic in a job interview, a pitch, or a professional document, find the primary source.

A real example of how to catch one:

We asked Claude to estimate how many Australians had used an AI tool for resume writing in the past 12 months. Claude offered a specific estimate with what sounded like a sourcing basis. When pushed, "What's the actual primary source for that number?", it acknowledged it was a plausible estimate rather than a verified statistic, and the estimate was based on extrapolation from US data and Australian internet penetration figures, not a study.

That's the right outcome. But it took a direct challenge to get there. The initial response did not come with a warning label.

The lesson: if a number matters to how you're using it, ask "What is the primary source for this specific statistic?" If the AI hedges or can't name one, the number doesn't go in anything important.

Training cutoffs: the world stopped at a point in time

Every AI model has a knowledge cutoff, a date after which it has no information. The cutoff shifts with every new model release, and the gap between "trained on" and "you're talking to it" is usually somewhere between several months and a couple of years. Each model documents its own cutoff; you can also just ask it directly. Gemini, because it can optionally ground responses in live web search, has fewer cutoff problems, but still has them for content-only mode.

This matters for career research more than most beginners realise.

The job market data problem: If you ask an AI "What skills are most in demand for data analysts in Australia right now?" you may get a very confident answer that reflects what was true 18 months ago. The demand landscape for certain technical skills changes quickly. Courses that were "highly recommended" two years ago may now be outdated. Technologies that were "emerging" may now be mainstream, or may have been abandoned.

The company research problem: If you're researching a company before an interview, AI may give you information that was true a year ago. A company that "recently expanded into sustainability consulting" may have shut down that division. A CEO the AI names may have left. A product the AI describes may no longer exist.

The fix: For anything time-sensitive, job market data, company information, industry trends, verify with a current source. LinkedIn, company websites, recent news. Gemini with web grounding enabled is better than Claude or ChatGPT-no-browsing for this, but it's still not a substitute for going to the primary source.

Tone of confidence, even when wrong

This is perhaps the hardest failure mode to guard against, because it's a feature of how these models communicate, not just an occasional glitch.

AI models are trained to be helpful, which includes being clear and confident. Hedging every sentence with "I might be wrong" would make the tools feel useless. So they don't do that. They state things clearly and directly.

The problem is that this communication style applies equally to things they're right about and things they're wrong about. A hallucinated citation comes out in the same confident tone as a correctly described concept. A made-up statistic reads identically to a real one.

The rule that protects you: Treat AI outputs in the same category as information from a smart colleague who speaks with great confidence and sometimes makes things up. They're valuable. You'd listen to them. But you'd check important claims rather than just forwarding their email to your boss.

Your bad assumption, amplified

One failure mode that doesn't get enough attention: AI often starts from the premise you give it, even if that premise is wrong.

If you say "I'm thinking about moving into data science, what qualifications do I need?" and your underlying assumption is "data science is one homogeneous field," the AI will answer your question without necessarily questioning the premise. You might receive a specific qualification roadmap for the wrong branch of the field entirely.

Better approach: "I'm thinking about data science, but I'm not sure which path makes sense. Here's my background [context]. What are the different paths within data, and which ones are realistic from where I'm starting?" You're inviting the AI to push back on or refine your framing, not just answer it.

Australian-specific context gaps

Australian workplace law, Australian industry certification requirements, and Australian job market dynamics are underrepresented in AI training data compared to US and UK content.

This doesn't mean AI is useless for Australian career questions. It means you need to verify anything Australia-specific. Whether a specific certification is recognised by the relevant Australian body. Whether a qualification from a particular institution is seen as credible in your target industry. Salary ranges (Australian data is thin; the models often default to US figures and note they're "approximate").

For Australian-specific questions: The government's myfuture.edu.au and joboutlook.gov.au, industry bodies, and LinkedIn salary benchmarking are more reliable primary sources than AI for market data.

How to double-check

Here are the questions to ask before trusting an AI output in a professional context:

  1. Is this time-sensitive? If yes, verify with a current source.
  2. Is this a statistic or citation? If yes, find the primary source before using it.
  3. Does this involve Australian regulation, law, or credentialling? If yes, go to the relevant Australian body.
  4. Did I start from an assumption the AI may have just accepted? If so, ask: "What assumptions is this answer based on? Are there ways my framing might be off?"

That's it. Not complicated. Just a habit.