Questions to Ask a Coding Bootcamp
These are questions to ask a coding bootcamp before you pay a deposit or sign an income share agreement, written for career changers comparing schools. The list follows the order the decision usually takes: outcomes and how they are counted, the teaching, the curriculum, cost and contract terms, and job search support, with a last group to put to recent graduates. Each has a note on what a good or a worrying answer sounds like, or what to do with it.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Outcomes
How is your job placement rate calculated, and who is left out of the count?
Why ask it
A placement rate is a fraction, and the part that moves it is the bottom: everyone who enrolled, or only graduates the school classed as actively job seeking. The follow-up is what takes a person out of that group. A rep who can walk through the arithmetic is a good sign; one who only repeats the percentage has told you nothing yet.
Which jobs count as a placement: only full-time developer roles, or contracts and non-coding work too?
Why ask it
Schools draw this line in different places. Some count only full-time roles writing code, while others include short contracts, internships, part-time work, jobs outside tech or teaching assistant posts at the bootcamp itself. The share that was full-time, paid and technical is the rate to compare between schools.
Of the students who started your last few cohorts, how many finished the course?
Why ask it
Placement is usually measured among graduates, so people who left partway vanish from it. A school that knows its completion figure and can say why people leave, whether money, pace or life, is watching the right thing. If nobody has the number to hand, settle for a head count: how many started the cohort that ended most recently, and how many finished.
What is the median starting salary for graduates, and how many of them reported one?
Why ask it
The median is the figure to hold out for, since a few high offers pull an average up. The second half matters as much: a salary built on the minority of the class who answered a survey may mostly describe the people with good news to share. Pay also varies a great deal by city, so a national number needs a local one beside it.
How long does it take a typical graduate to get a first offer after finishing?
Why ask it
This is the number to budget around, because rent has to be covered through the search as well as the course. A worrying answer is a best case told as a story about one student. Better is a spread, such as the share with an offer at three months and at six, with your savings planned on the slower figure.
Has anyone outside the school checked your outcomes figures, and can I read the full report?
Why ask it
Some schools publish outcomes reviewed by an outside auditor or filed with a regulator, and some publish only what marketing wrote. What you want is the document itself, with its definitions and dates. A full report with awkward numbers in it is more reassuring than one tidy figure on a landing page.
How do the results for your most recent cohort compare with those from two or three years ago?
Why ask it
Hiring for junior developers rises and falls, so an old figure may describe a job market that no longer exists. A straight answer admits it if things have gotten harder and says what the school changed in response. Check the date on any statistic you are shown: one more than a year old is history.
What do outcomes look like for students who started where I am starting?
Why ask it
Describe yourself first: your degree or lack of one, your current field, where you live, how much you have coded. Graduates who arrived with a technical degree or a related job can carry a school's average. A rep who cannot split the figures can still introduce you to two graduates whose starting point matches yours.
Teaching
Who would teach my cohort, and what did they do before teaching here?
Why ask it
You want a name, not 'our experienced instructors'. Look the person up afterwards: years spent working as a developer and years spent teaching are both worth having, and someone who finished the same bootcamp last year has little of either. It is also worth knowing who takes over the class if that instructor leaves midway.
How many hours a week are live teaching, and how many are recorded video and self-study?
Why ask it
'Live' and 'instructor-led' get stretched, so pin the answer to hours on a calendar. A course that is mostly recordings with a weekly check-in can still work, but its price belongs beside other self-paced material. Live hours also come in two kinds, lectures and time when someone looks at your code, and the second is the one that is hard to get anywhere else.
Do you run this course both full time and part time, and how do completion and job results differ between them?
Why ask it
Career changers who cannot stop working usually end up on the evening version, so those are the figures that apply to them. A school may quote one set of results for every format. If the part-time numbers are not kept separately, find out whether the same instructors teach it and how many months longer it runs.
What does a typical week on the course look like, and how much work is there outside class hours?
Why ask it
The timetable shows the scheduled hours; the useful figure is what students report on top of them. If you plan to keep a job or have people depending on you, say so and hear how others in that position managed. A rep who says a full-time course fits around full-time work is telling you what you want to hear.
How many students are there for each instructor and each teaching assistant?
Why ask it
The ratio decides how long you wait when you are stuck. Get it for the cohort running now, since the brochure may describe a smaller class than the one being filled. The assistants deserve a question of their own, because at some schools they finished the same course a few months earlier.
When I am stuck on an assignment in the evening, who can I ask, and how fast do they answer?
Why ask it
Most of the learning happens in the hours when something will not run. A good answer names a channel, the hours it is staffed and a usual wait. 'Post in the community chat' means other students will help if they happen to be around.
Who reviews my code, and how often would I get written feedback on it?
Why ask it
Passing automated tests shows the code runs. It says nothing about whether another developer could read it, which is what a first employer will judge. A sample of the feedback a past student received, with the name removed, settles it: count how many of the comments are specific.
Can I sit in on a live class or watch a recording of a real one before I enroll?
Why ask it
An hour in the room tells you more than a sales call can: the pace, how questions are handled, how many students are following. A school that is confident in its teaching usually says yes. A polished sample lesson made for marketing is not the same thing, so say you mean an ordinary session from a current cohort.
If I fall behind partway through, can I repeat a unit or move to a later cohort?
Why ask it
People fall behind for ordinary reasons: a sick child, a hard week at work, a topic that does not click. A yes needs two more facts, what the repeat costs and how many students used it last year, because an option nobody takes may not really be open. Be wary of 'nobody falls behind', and equally of a rule that removes you with no refund.
Curriculum
Which languages, frameworks and tools does the course teach, and why those?
Why ask it
The useful half is the 'why'. A good answer points to the jobs graduates apply for and what those postings ask for. Before the call, read a few dozen junior postings in your own city and see how much of the school's list turns up in them.
What is the pre-work, and how much should I already know on day one?
Why ask it
Pre-work is often where the course really begins, and a student who skips it can spend the first weeks catching up. How many hours it takes and whether anyone checks it are both worth knowing. Doing it before you pay the balance is also a cheap test of whether you like the work.
How do you decide who gets in, and what share of applicants do you turn down?
Why ask it
A school that admits everyone who can pay has no stake in whether you are ready, and a class with a wide spread of starting points is hard to teach. A technical exercise or an interview about your reasons suggests somebody is protecting the results. Being told you are a perfect fit ten minutes into a first call is a sales decision, not an assessment.
When was the curriculum last revised, and what changed?
Why ask it
Tools and versions move quickly, and material written several years ago can teach habits that working teams have dropped. Someone who teaches the course should be able to name a recent change and the reason for it. 'We update constantly', with no example, suggests nobody in the conversation knows.
How much of the course is building things from a blank file, and how much is following guided exercises?
Why ask it
Following a tutorial feels like progress and can leave people unable to start alone. One way to measure it is the share of weeks that end with a project where students choose the design themselves. What you are hoping to hear described is a course that takes the guide rails away a step at a time.
What will I have built by the end, and can I see final projects from the last cohort?
Why ask it
Get links, then open several. If every student's project is the same app in different colors, an employer who has interviewed graduates before will have seen it too. Look for a few that solve a problem the student clearly cared about and that still run.
How much computer science does the course cover, such as data structures and algorithms?
Why ask it
Technical interviews at some employers lean on these topics, even for jobs that rarely call on them. Bootcamps differ: some teach them properly, some add a week at the end, some leave them to you. Where the coverage is thin, graduates will have filled the gap on their own time, and those weeks belong in your timeline.
How does the course treat AI coding assistants?
Why ask it
There is a real tension here: a beginner who leans on an assistant too early may never learn to read and debug code, and employers differ on how much they expect a new hire to use one. What matters is the point at which the tools are allowed and how students are tested without them. A thought-out position either way beats a flat ban or a shrug.
How are students assessed, and what happens to someone who does not pass?
Why ask it
A course nobody can fail is selling attendance. Graded checkpoints with a retake are a sign the certificate means something, and the number of people who did not pass in the last cohort tells you if the bar is real. What failing does to your place and to any refund should be in the enrollment agreement, so check it there as well.
Do I keep access to the lessons, recordings and my own project code after the course ends?
Why ask it
The job search is when people go back over the weeks that went by too fast, and some platforms close a student's login soon after graduation. 'Lifetime access' is easy to say on a call, so get it in writing, along with what becomes of it if the school changes platform. Whatever the answer, keep your project code in a repository under your own account from the first week.
Cost
What is the total I would pay, including everything beyond tuition?
Why ask it
Get one number in writing that includes the deposit, registration or materials fees, any software or equipment you must buy, and interest if you finance it. Then add your own living costs for the course and for a job search of several months. That total is the one to weigh against the salary figures.
What is the refund policy, and what is the last date I could withdraw and get money back?
Why ask it
Have the written policy sent to you and read the dates yourself. Each school sets its own schedule, and the rules that sit above it depend on where the school is registered, so ask how it works there. Whether the deposit is ever returned is a separate matter, and any spoken promise is worth having confirmed by email.
If I use an income share agreement, what percentage of my income would you take, for how long, and what is the cap?
Why ask it
Three numbers define the deal: the percentage, the number of payments and the most you could ever pay. Work out what you would hand over at the salary the school quotes and compare it with the upfront price. If the cap is well above that price, you are paying for the delay, and it is fair to ask how much.
What income starts the payments, and does a job outside tech count?
Why ask it
Some agreements start collecting once you earn above a set amount in any work, including the job you were trying to leave. The threshold, whether it is measured before or after tax, and whether payments pause if you lose the job are the three things to pin down. The contract's definition of qualifying income is the one that binds, and it will be longer than the sales page.
What do I owe if I leave early, am asked to leave, or never get a developer job?
Why ask it
These are the three ways the plan goes wrong, and the contract should have a clause for each. A clear answer gives a figure or a formula for every case. If the rep says it rarely happens, ask again, because you are asking about the cost and not the odds.
Who holds the loan or agreement, and can I read the whole contract before I pay a deposit?
Why ask it
Financing is often run by an outside lender or servicer, so a dispute may be with a company you have never spoken to. You want the full document, not a summary, and a few days alone with it. Pressure to sign the same day is a reason to slow down.
If there is a job guarantee or a tuition-back offer, what exactly must I do to stay eligible?
Why ask it
The promise lives in its conditions. They can include a set number of applications every week, taking the first offer whatever it pays, being willing to move, and logging everything in the school's tracker. Two figures show what the promise is worth: how many graduates have been paid out, and how many lost eligibility on a technicality.
Is paying upfront cheaper than financing, and are there scholarships I should apply for first?
Why ask it
Put the totals under each payment option side by side before comparing anything else. Scholarships and early-payment discounts are worth raising by name, and their deadlines can fall well before the cohort starts. A discount that 'ends on Friday', mentioned on a first call, is a sales tactic; see whether it will be there for the next cohort too.
Is the school licensed or approved by a regulator where it operates, and what happens to my money if it closes mid-course?
Why ask it
Whether a bootcamp needs approval, and what protection its students have, depends on the country and often the state or province. Ask how it works there, then check with that body yourself. Bootcamps have closed or been sold with cohorts in progress, and a school with a plan for that will be able to describe it.
Job search
What does career support consist of, when does it start, and how long does it last after graduation?
Why ask it
'Career services' can mean a named coach who meets you weekly or a folder of resume templates. A useful answer is a list of what each student receives and the week each part begins. Support that ends a few weeks after the course may stop before most of the search has happened, so get the end date.
Who are the career coaches, and how many students does each one work with?
Why ask it
A coach who has hired developers, or been hired as one, gives different advice from a general recruiter. The caseload shows how much attention is possible: a one-on-one meeting every week or two during the search would be a strong answer. If coaching means group webinars, count it as that.
Which employers hired your graduates in the last year, and what does 'hiring partner' mean here?
Why ask it
A logo on the website can mean one graduate was hired there once, or already worked there before enrolling. Ask how many people each named employer took in the past twelve months. A real partnership has something behind it, such as reserved interviews or an apprenticeship program.
How do you prepare students for technical interviews?
Why ask it
Find out how many mock interviews each student gets, who runs them and whether they include live coding in front of someone. One practice session in the final week is not preparation. The strongest answer is that interview practice runs alongside the course and working engineers do some of the interviewing.
Do you help with a job search in my city, or mainly where the school is based?
Why ask it
An online bootcamp may have its employer contacts in one or two cities, none of them yours. The test is how many graduates found work in your area or in remote roles, and whether any coach knows the local market. If the honest answer is that you would be on your own, the search will rest on your own network.
What do you do for a graduate who is still looking after six months?
Why ask it
Every cohort has some, and the answer shows whether the school stays with them. Good signs are continued coaching, access to updated material and introductions that keep coming. If the reply turns to what the graduate must have done wrong, picture yourself on the receiving end of it.
Graduates
How long did it take you to get your first developer job, and how did you find it?
Why ask it
Put this to graduates you found yourself, as well as any the school introduces. The 'how' matters as much as the 'how long': through the school, through a personal contact or through hundreds of cold applications. What they lived on in between is worth hearing too.
Was your first salary in the range the school talked about?
Why ask it
People will often give a range even when they will not give a figure. Whether the first role was permanent, a contract or an apprenticeship changes what the number means, since those are paid differently. Two or three answers from the same year tell you more than the brochure's single number.
What did the school tell you before you enrolled that turned out to be different?
Why ask it
Asked without an edge, this usually brings out one thing: the amount of live teaching, the help with jobs, the workload. One mismatch is normal for any course. The same complaint from three people is a finding.
How many people from your cohort are working as developers now?
Why ask it
A graduate can usually count this from the group chat, and it is the nearest thing to an unpublished placement rate you will get. The rest of the count is as telling: still searching, back in their old field, or in a tech role that is not programming. Set it beside the figure the admissions rep gave you.
How many hours a week did it really take, and what did you have to give up?
Why ask it
The rep answered this for the average student. A graduate answers for one life, so look for someone who carried the same job or family load as you. Listen for what dropped away, whether sleep, weekends or income, and decide before you enroll which of those you can afford.
What did you have to teach yourself after the course before you were hireable?
Why ask it
Most graduates can name something, and for a given school it tends to be the same few things. That list is the gap in the curriculum, and you can take it straight back to the instructor. It also tells you how many more months to plan for after the last day.
How did employers react to the bootcamp on your resume?
Why ask it
Reactions differ by employer and by city, so note where each person applied. Some graduates find the school's name opens doors; others lead with their projects and mention the bootcamp last. If several say they left it off, weigh that against the price.
If you were starting over, would you pay for this bootcamp again or get there another way?
Why ask it
Save this for last, once they have warmed up. A yes with reasons is worth hearing, and so is 'yes, but I would have picked the cheaper part-time one'. The other way might be self-study, a community college course, a degree or a move inside their old employer, and the one they name tells you what the bootcamp gave them that it could not.
How to question a coding bootcamp before you pay
Practical guidance for the conversation itself
Before you talk to anyone
Know who you are talking to
The admissions rep's job is to fill the cohort, and it is fair to ask whether they are paid on enrollments. They are the right person for Outcomes and Cost, where you want figures and documents. Ask for twenty minutes with an instructor for Teaching and Curriculum, and keep the last group for graduates. If a school will not let you speak to anyone who teaches, that is information too.
Read job postings first
Before any call, read a few dozen junior developer postings in the place you want to work. Note the languages, the tools and whether a degree is asked for. That list is the yardstick for the curriculum and for the outcomes claims, and it shows whether the job you are picturing is being advertised near you at all.
Find graduates the school did not choose
The graduates a school introduces are its happiest ones. Search a professional networking site for people who list the bootcamp under education and finished one to two years ago, and write to five or six with one short, specific question. Include some whose current job title is not a developer's, because they are the part of the cohort the brochure leaves out.
Set your own numbers
Write down what you can spend in total, how many months you can go without a salary, and the lowest starting pay that would make the change worth it. Every answer under Cost and Outcomes then has something to be measured against. Without those three figures it is easy to be talked into a plan that only works in the best case.
Try the work for free
Spend a few weeks on a free beginner course before any sales call. You will find out whether you like programming, your questions about the curriculum will get sharper, and you will be harder to rush.
On the call and afterwards
Put the same questions to every school
Pick eight to ten, at least one from each group, and ask each bootcamp on your list in the same words. Keep the answers in one table. A school that looked best on its website can look different beside two others answering the same thing.
Start with Outcomes, end with Graduates
If a school cannot explain its own placement figure, the remaining groups matter less, so begin there. Leave Cost until you know what you would be buying. Graduates come last so that you can check what you were told against what happened.
Ask about the last cohort, not the best one
Most questions under Outcomes and Job search get a better answer when you tie them to a date: the cohort that finished most recently, or the past twelve months. A story about one graduate who doubled her salary can be true and still say nothing about the middle of the class.
Get figures and promises in writing
After a call, send a short email listing the numbers and commitments you heard and ask the rep to confirm them. Refund terms, the payment cap, the conditions on any job guarantee and the length of career support all belong in it. Where the email and the contract differ, ask which one will be changed before you sign.
Take the contract away with you
Do not sign on a call. Ask for the enrollment agreement and any financing contract as documents, read them over a few days, and mark every clause you do not understand. Rules on these agreements differ from place to place, so for a commitment this size it is reasonable to have someone independent, who knows consumer contracts where you live, look at it.
Reading the answers
Definitions beat percentages
A high placement rate with no definition behind it is weaker evidence than a modest one with the denominator, the time window and the kind of job spelled out. When you compare two schools, compare the definitions first and the figures second.
'I will find out' is a good answer
A rep who does not know the completion rate and comes back with it two days later has shown you how the school treats a hard question. One who changes the subject, or smoothly answers a different question, has shown you that too.
Notice pressure
A deadline that appears during the call, a seat that is 'the last one', a discount that needs a deposit today: none of these is about your education. A course that suits you this month will suit you next cohort, and a school with good results can afford to let you think.
Weigh graduates against the rep
Where a graduate's account and the admissions account differ, ask a second graduate before deciding who is right. One unhappy person is one person. Three who describe the same gap, in teaching hours or in help with jobs, are describing the course.
Mistakes to avoid
Comparing headline rates
Two schools can report very different placement figures for similar results because they count differently. Setting the two percentages side by side without the definitions rewards the school with the looser one.
Budgeting only for the course
The search after graduation can run for months, and it is unpaid. Someone who budgets to the last day of class may have to take the first job of any kind, which under some agreements also starts the repayments.
Treating deferred payment as free
An income share agreement or deferred tuition moves the bill, and can enlarge it. Work out the total at a realistic salary and at the cap before you compare it with paying upfront or with a cheaper course.
Skipping the graduates
It is the step most easily left out, because it means writing to strangers. Graduates are also the one group in the process with nothing to sell you. Send the messages before your second call with the school, so the replies can shape what you ask.