How to Spot a Bad Coding Bootcamp: 7 Red Flags Before You Pay

The coding bootcamp industry has a quality control problem. Unlike universities, which are regulated by accreditation bodies with decades of standards, bootcamps can launch with a Squarespace website, a few instructors, and zero oversight. The barrier to entry is low, which means both excellent and terrible programmes exist side by side, and they often look identical from the outside.

Bad bootcamps have gotten very good at mimicking the signals of good ones. They have polished websites. They use the same language ("full-stack," "career support," "industry mentors"). They show the same stock-photo diversity. They quote the same type of outcome statistics. From the marketing alone, you genuinely cannot tell them apart.

That is why you need red flags: specific, testable indicators that separate programmes that will actually prepare you from programmes that will take your money and leave you with tutorial-level skills and no portfolio.

Here are the seven that matter most.

This is the single most reliable red flag, and the easiest to test.

A legitimate bootcamp has nothing to hide about what it teaches. The full syllabus, week by week, topic by topic, should be visible on the website before you pay anything or speak to a salesperson. You should be able to read it, compare it to other programmes, and make an informed decision.

A bad bootcamp hides the curriculum behind a "book a call" button or a deposit. The reason is always the same: if you saw the syllabus, you would realise it is outdated, thin, or identical to free resources you could access yourself. Hiding it prevents comparison shopping.

Test: go to the bootcamp's website right now. Can you see exactly what you will learn in week 1, week 5, week 12? If no, that is your first red flag.

For reference, McTaba's full curriculum is visible on the course page. Every module, every topic, every project. We are biased, but the principle applies universally: if a programme will not show you what you are buying, do not buy it.

"94% of our graduates are employed within 6 months."

That sentence is meaningless without knowing three things: how they define "employed," whether dropouts are included in the calculation, and who verified the number.

We covered this in detail in our article on whether bootcamps actually get you jobs, but the short version: most "90%+" placement rates use definitions that count freelance gigs, unpaid internships, pre-existing jobs, and non-tech positions. The real number for paid developer roles is typically 50-70% for good programmes.

A programme quoting a high placement rate should be able to tell you:

• The exact definition of "placed" or "employed" they used
• Whether the calculation includes or excludes dropouts
• The time window (3 months? 6 months? 18 months?)
• Whether an independent party verified the data

If they cannot or will not answer these questions, the number is marketing, not data.

Ask the bootcamp: "Can you show me five deployed applications that recent graduates built during the programme?"

This is the most revealing question you can ask. A programme that produces employable developers produces working applications. They should be able to point you to live URLs, GitHub repositories, or at minimum screenshots of real student projects.

If the bootcamp cannot show you real student work, one of three things is true: the programme does not require real projects (bad), the projects are so weak that showing them would hurt enrolment (worse), or the programme is so new that no one has graduated yet (risky).

What to look for in student portfolios:

• Are the applications deployed and actually working, or just screenshots?
• Do they solve real problems, or are they generic tutorial clones (to-do apps, weather apps)?
• Is there variety, or did every graduate build the same template project?
• Is the code on GitHub, and does it show real commits over time (not a single dump)?

"Only 3 spots left!" "This price expires Friday!" "Book your call now before the cohort fills up!"

Good bootcamps do not need manufactured urgency. If the programme is genuinely good, it fills on the strength of its outcomes and reputation. Artificial scarcity and countdown timers are tactics borrowed from the online course hype industry, and they are designed to prevent you from doing the research that would reveal the programme's weaknesses.

Specific tactics to watch for:

• Fake scarcity: "Only X seats remaining" when the same claim appeared last month
• Discount pressure: "This price is only available if you enrol today"
• Emotional manipulation: "If you don't act now, you're choosing to stay where you are"
• Refusal to let you think: Sales calls designed to close you on the call, discouraging you from taking time to compare options

A legitimate programme will say: "Take your time. Compare us to alternatives. Talk to our graduates. We are confident in what we offer." Any programme that pressures you to decide before you have done your research is worried about what your research will find.

You would not buy a car without test-driving it. A bootcamp asking for KES 100,000+ without letting you experience any of the teaching first is asking you to take an enormous risk on faith.

Good programmes offer at least one of these:

• A free trial period (even a few days)
• A free introductory module or mini-course
• A refund window (7-14 days is reasonable)
• A low-cost starter course that lets you test the teaching style

McTaba, for example, offers a free account to preview the platform and Tech Foundations at KES 2,999 as a low-risk way to experience the teaching before committing to the full programme. We do this because we believe people who try our teaching style will want to continue. A programme that refuses to let you try is making the opposite bet.

In 2026, the technology landscape has shifted fundamentally. AI-assisted development is the baseline expectation for new developers. Any bootcamp that does not teach you to work with AI tools (Claude, Cursor, GitHub Copilot) is training you for a job market that no longer exists.

Beyond AI, check whether the curriculum covers current frameworks and tools:

• Is the JavaScript framework current (React 18+, Next.js, or equivalent), or are they teaching jQuery?
• Is the backend stack modern (Node.js, Python with FastAPI, or similar), or are they teaching PHP 5?
• Do they teach TypeScript, or only plain JavaScript?
• Is Git/GitHub part of the workflow from day one?
• Do students deploy applications, or does everything stay on localhost?
• For African learners: does the curriculum include M-Pesa, Paystack, or any local payment infrastructure?

A curriculum that was excellent in 2022 is outdated in 2026. The industry moves fast, and a bootcamp that is not updating its syllabus at least annually is falling behind.

Who is teaching the programme? This question is surprisingly hard to answer for many bootcamps.

Check the instructor bios on the website. Look for:

• Real industry experience: Have they built production software? Do they have a LinkedIn profile showing years of professional development work? Or are they recent graduates of the same bootcamp, now teaching the next cohort?
• Verifiable credentials: Can you find their GitHub, their portfolio, their previous employers? Or is the bio a vague paragraph with no specifics?
• Current skills: Are they actively building software, or did they stop coding years ago? The best instructors are practitioners who teach, not former developers who only teach.

A pattern in lower-quality bootcamps: the "instructors" are graduates from a recent cohort who are hired at a low cost because they cannot find developer jobs. They are one chapter ahead of you in the material. This is not always bad (peer instruction can work), but it should be transparent, not presented as "industry expert instruction."

Many people ask whether a bootcamp is "accredited" as if that settles the quality question. In the university world, accreditation is a meaningful quality filter maintained by established bodies with real standards. In the bootcamp world, it is much murkier.

In the US, a handful of bootcamps hold accreditation from bodies like ACCET or are licensed by state education departments. In Africa, there is no widely recognised accrediting body specifically for coding bootcamps. Some programmes are registered as training providers with national education authorities, but this registration is typically about legal compliance, not curriculum quality.

What this means for you: do not rely on an "accredited" label to guarantee quality, and do not dismiss a programme simply because it lacks formal accreditation. The bootcamp industry is too young and too varied for accreditation to serve as a reliable proxy for quality the way it does for universities.

Instead, evaluate outcomes directly: what do graduates build, where do they work, is the curriculum current, and can you talk to real people who completed the programme? These signals are more reliable than any credential on the wall.

For a complete evaluation framework, see our bootcamp selection checklist which walks through every question to ask before enrolling.

Before you pay for any bootcamp, run through this list. If three or more are true, do not enrol.

1. You cannot see the full curriculum before paying or speaking to sales.
2. They quote a placement rate above 90% but cannot explain their methodology.
3. They cannot show you 5 deployed projects from recent graduates.
4. They use urgency tactics ("last 3 spots," "price expires today").
5. There is no free trial, preview, or refund policy.
6. The curriculum does not include AI tools or was last updated before 2025.
7. Instructor bios are vague or instructors have no verifiable industry experience.

A good bootcamp will pass all seven. A great bootcamp will proactively share this information without you having to ask.

Ready to compare specific programmes? See our best bootcamps for beginners or the best online options from Africa.