What Happened to Lambda School (BloomTech)?
TL;DR - Lambda School rebranded to BloomTech in 2022 after FTC scrutiny, regulatory issues with its income share agreements, and public controversy over placement rate claims. - The school went through significant layoffs, leadership changes, and program restructuring in 2021-2022. - If you attended Lambda or BloomTech, your technical skills are real. The credential's recognition is limited, which means your portfolio and real-world experience carry more weight. - What's working against former Lambda/BloomTech grads isn't the skills. It's the credential skepticism plus a harder junior job market. - Practical path forward: fix the portfolio, sharpen interview skills, and get real-world team experience.
Lambda School launched in 2017 with an unusual pitch: you could attend for free and pay only if you got a job. The income share agreement model — where students give up a percentage of their future income instead of paying tuition upfront — was positioned as proof that the school was confident in its outcomes.
That pitch attracted significant venture capital and a lot of students. It also attracted a lot of scrutiny.
What Actually Happened
The Lambda School story is long, but the key events are worth understanding clearly.
The ISA model came under pressure. Income share agreements, by their structure, can expose students to significant financial obligations. Lambda School's ISAs required graduates to pay 17% of income for two years once earning above $50,000, capped at around $30,000 total repayment. Consumer advocates and regulators raised concerns about whether students fully understood what they were agreeing to, and whether the terms in some cases amounted to unregistered securities.
Placement rate claims became a controversy. Lambda School publicized placement rates that critics — including journalists, former students, and researchers — argued were inflated or calculated in ways that didn't reflect reality. The definition of "placement" and the percentage of graduates included in the calculation were disputed. Outcomes for students who didn't complete the program or didn't find in-field employment were, by some accounts, underrepresented in the public numbers.
The FTC sent a warning. In 2021, the Federal Trade Commission sent letters to several ISA-based programs, including Lambda School, warning that some business practices could violate consumer protection laws. This wasn't a lawsuit or a definitive finding, but it signaled regulatory attention that made investors and prospective students more cautious.
Layoffs and restructuring. In 2021, Lambda School laid off a significant portion of its staff. This included curriculum staff, career services personnel, and other roles directly involved in student outcomes. The stated reason was a move toward more automated and scalable instruction. Former employees publicly described a chaotic internal environment during this period.
The rebrand. In early 2022, Lambda School rebranded to BloomTech. The company framed this as a fresh start with updated programs and a clearer focus. Critics viewed it as an attempt to distance the brand from accumulated controversy. The programs continued to run, but on a much smaller scale than during the peak years.
The underlying company has faced continued challenges since the rebrand. The coding bootcamp market overall contracted as the 2021 hiring boom ended and junior developer hiring became more competitive.
What This Means If You Attended Lambda or BloomTech
The controversy around the school's business practices doesn't invalidate the skills you learned. If you worked through the curriculum, built projects, and engaged with the material, you have real technical knowledge. That's not retroactively erased by the school's regulatory or reputational problems.
What it does affect:
The credential carries skepticism. Some hiring managers and recruiters are aware of the Lambda School controversy. The name on a resume may prompt questions it wouldn't have in 2019. This isn't universally true — many hiring managers either don't know the history or don't weight it heavily — but it's real enough that you shouldn't rely on the credential to do much work for you.
Career services may be limited or unavailable. If you graduated during a period of layoffs or restructuring, the career support you were promised may not have materialized. That's a real grievance. It's also the situation you're in, and the path forward doesn't depend on the school delivering on promises it made.
Your cohort peers who got hired are probably not meaningfully different from you in technical skills. Job placement at any bootcamp is rarely a strict function of who learned the most. It's a combination of technical skills, portfolio presentation, interview performance, networking, and timing. If you're still looking, the gap probably isn't in your technical knowledge.
What to Focus on Now
If you attended Lambda School or BloomTech and are still in the job search, here's where to put your energy.
Your GitHub Is Your Real Credential
The Lambda School brand on your resume is working against you in some cases. Your GitHub profile, if it's strong, is working for you regardless of where you went to school. A hiring manager who looks at a GitHub profile with real projects, clean code, good commit history, and thoughtful documentation will draw conclusions from that — not primarily from the school name.
Read about building a GitHub profile that gets you hired and make that your priority. A profile that looks like it belongs to a working developer is more persuasive than any credential.
The Resume Framing Matters
How you present the Lambda/BloomTech credential on your resume affects how it's read. There are specific choices — where to list it, how to describe it, what to lead with — that can work for or against you. Read the guide on how to explain a bootcamp on your resume for the specific formatting and language decisions that matter.
Don't hide the bootcamp or use vague language. That tends to read as evasive. Present it directly as the technical training it was, and let your projects and skills do the differentiation work.
Real-World Experience Fills the Signal Gap
One of the things that makes Lambda/BloomTech grads vulnerable in hiring is the same thing that makes all bootcamp grads vulnerable: no real-world team experience. Every project in the portfolio was built in isolation or in a cohort setting. Employers know the difference between a project built in a learning environment and a project built in a production environment with real requirements, real constraints, and real teammates.
If you can add actual professional experience to your resume — even unpaid or volunteer technical work — it changes the profile significantly. Nonprofit software internships are a direct path to this. You're building real software for an organization with real needs. That shows up differently on a resume and in interviews than bootcamp projects do. Read more about how to get real software engineering experience without waiting for someone to hire you first.
Diagnose Where You're Actually Losing Jobs
If you've been applying for several months or longer without offers, you're losing at a specific point in the process. Getting clear on where that is matters.
Not getting any interview callbacks: the problem is in your resume, LinkedIn profile, or application targeting. Fix those before applying more.
Getting first-round interviews but not advancing: the problem is usually in technical screening. Either a take-home project or a phone/video technical screen. This requires targeted practice, not just general studying.
Getting deep in interviews but not getting offers: the problem might be in behavioral or system design rounds, or in how you present yourself in final stages.
The job search after six months of trying is a different situation from actively job searching for a few weeks. The approach needs to change when the original strategy isn't working.
Should You List It as Lambda School or BloomTech?
This is a practical question that comes up for anyone who attended during the transition period.
The answer depends on timing. If you attended and graduated under the Lambda School name, listing it as Lambda School is accurate. If you attended after the rebrand, BloomTech is correct. Some people who attended across the rebrand window list both names in parentheses for clarity.
What matters more than which name you use is what surrounds the credential on your resume. The projects, skills, and accomplishments you list alongside it are what hiring managers actually evaluate.
The Broader Lesson
Lambda School/BloomTech's story illustrates a specific risk in the coding bootcamp model. When schools promise employment outcomes as a core part of their marketing — and especially when they structure payment around those outcomes through ISAs — they create incentives that don't always align with what students actually need.
The pitch of "pay nothing unless you get hired" sounds like a risk-free offer. In practice, it's a bet that the school is making on your employment, and the terms of that bet (the ISA) may not be as student-friendly as the marketing implies.
This doesn't mean all ISA-based programs are predatory, or that all bootcamps overpromise. Many graduates of many programs have landed real jobs and built real careers. But the incentive structure is worth understanding before signing any income share agreement.
Where to Go From Here
If you're a Lambda/BloomTech graduate still in the job search, the most useful mindset shift is this: the credential question is mostly settled. Employers will see what they see when they look at the school name. You can't change that. What you can change is everything else — the portfolio, the GitHub profile, the interview performance, the professional experience on your resume, and the strategy of your job search.
Those are the things that actually move hiring decisions. They're also the things you have full control over.
The work isn't starting over. It's building on what you already know with the additional signal that makes employers confident enough to make an offer.
Interested in the program?