<- all tokdocs

How to Spot a Fake AI Builder: Does "Show Me Where It Breaks" Work?

By , founder of Mavric and Apso

View on TikTok ->

A TikTok from @fractionalctomatt says you can spot a fake AI builder with one question: "Show me where it can break." The question is a compressed version of failure modes and effects analysis, and it holds up better than the three red flags the video lists before it. It can still be gamed by anyone who has read a public list of AI risks, so the follow-up question matters more.

What does "show me where it can break" actually test?

It tests whether the builder has a stored list of ways their system fails. That list only exists if they have run the system in production or deliberately analyzed it for failure before shipping.

Engineering has formal names for this:

  • Software FMEA. NASA's Software Engineering Handbook defines it as a hardware FMEA with software components substituted in, and says the analysis "begins looking for potential system problems while the project is still in the design phase."
  • The premortem. Gary Klein's 2007 Harvard Business Review article describes a session where "team members assume that the project they are planning has just failed" and list the likely reasons.
  • Chaos engineering. The Principles of Chaos Engineering define it as "the discipline of experimenting on a system in order to build confidence in the system's capability to withstand turbulent conditions in production." Netflix's Chaos Monkey, an Apache-2.0 tool, randomly terminates production instances to put this into practice.
  • Postmortems. Google's SRE book lists triggers for a postmortem, including "data loss of any kind" and "a monitoring failure (which usually implies manual incident discovery)."

The video's line that real builders "already know because they built it into the last one" matches the SRE view. Failure knowledge comes from having operated something.

Why the question separates real builders from fake ones

Specific failure stories are hard to fake. Someone who has run a workflow against a live API can name what broke and what they added to stop it recurring: rate limit backoff, an upstream schema change, a token that expired overnight, a retry loop that charged a customer twice. Those details belong to one system, not a category.

The Google SRE trigger list shows what an operator's answer sounds like. Operators talk about thresholds, rollbacks and manual interventions. People who have only assembled a demo talk about capabilities.

Can a fake AI builder pass the test?

Yes, with a little preparation. The vocabulary of AI failure is public. OWASP's Gen AI Security Project lists ten named LLM risks for 2025, from LLM01 Prompt Injection to LLM10 Unbounded Consumption. Reciting "prompt injection" and "hallucination" shows only that someone has read the list.

The video says the question works in five seconds. Five seconds shows whether someone hesitates, but judging the answer takes longer, and the video gives no way to score it. A stronger follow-up is to ask what they changed after the last failure and when it happened. Generic knowledge does not hold up when asked for a date.

The question also produces false negatives. A competent engineer who just inherited someone else's system may freeze for honest reasons, while a confident bluffer will not.

Are Zapier and n8n stacks a red flag?

No. The video's first red flag is a stack of apps "wired together from a tutorial" that is "really just five tools talking to each other." Both major platforms ship the failure handling the video's own question looks for.

n8n documents:

  • An error workflow, set per workflow in Workflow Settings, that "runs if an execution fails."
  • An Error Trigger node, which an error workflow must start with.
  • A Stop And Error node to "force executions to fail under your chosen circumstances."

Zapier documents:

  • Autoreplay, an account-wide setting on Professional plans and higher that "works to retry any failed steps in a Zap run."
  • Custom error handlers on Professional, Team and Enterprise. When you add one to a step, "the Zap will run the error handler as an alternative workflow." Every step except triggers and Paths can have one.

What to check is whether the builder turned these features on, which is what the "where does it break" question already checks. A hand-written Python service with no retries, no dead-letter queue and no alerting is more fragile than a five-node n8n workflow with an error workflow attached, even though it looks more serious.

What the video leaves out

The clip names no tool, company, product, person or number, so viewers get a test without a way to grade it.

The second red flag, "the same setup they sold the last 10 guys and there's nothing built around it," mixes two complaints. Reusing a template across clients is normal for delivery firms. The real problem is the second half, that nothing was adapted to the buyer's business.

The video also shifts its claim. The description says the question reveals "whether someone actually knows how to build with AI," while the spoken hook says it reveals "whether someone knows how they're using AI or not." The question tests building much better than using.

Buyers who want a formal version can use the NIST AI Risk Management Framework, released January 26, 2023. It organizes the same idea into four functions (Govern, Map, Measure and Manage) and is voluntary and free.

Bottom line

"Show me where it can break" is a sound screening question because failure knowledge comes from running a system. Follow it by asking what they changed after it broke, and when, since the risk lists are public. Judge Zapier or n8n builds by whether error handling is turned on, not by how many tools they connect.

Sources

Published September 21, 2026. Based on a TikTok by @fractionalctomatt. Full video notes (markdown)