“Am I smart enough for tech?” Wrong question. Here’s the right one.
This is the fear behind a thousand unopened tutorials - asked quietly, usually at night, never out loud. We teach complete beginners for a living, so we can answer it with classroom evidence instead of encouragement: raw intelligence is one of the weakest predictors of who makes it. The strong predictors are practices - and every one of them is available to you.Here’s the honest breakdown, and the two-week test that retires the question for good.
Watch a few thousand beginners attempt this journey and a pattern emerges that would surprise the person asking tonight’s question: we cannot predict who makes it from how smart they seem in week one.The quick-witted early stars stall as often as anyone - sometimes more, because they’ve never practised being bad at something. What predicts completion with almost embarrassing reliability is visible by week three, and it’s all behaviour: consistency (the person protecting a daily hour beats the brilliant weekend-binger, every single cohort), confusion tolerance(everyone feels stupid in weeks two to six - the survivors are the ones who’ve been told the dip is universal and treat it as the process instead of the verdict), and build-first behaviour (making things badly and early beats studying until “ready,” because ready never arrives through study). Three practices. Zero gifts. That’s the honest entrance exam.
The roster agrees with the pattern. Our documented graduates - names and companies public on the outcomes page - include a former music teacher, a coach, a salesperson, a customer-support worker, an operations manager, a gig worker. Ordinary people by their own description, several of whom arrived carrying exactly tonight’s question. One passed his verdict back in a public review: “I got a Software Developer job before I ended the bootcamp... and no, I had no diploma or degree to begin with.” If the field required special brains, the roster would look different.
Why the genius stereotype survives (and who it serves)
If ability isn’t the filter, why does everyone believe it is? Because every signal reaching you is filtered for drama. Movies need savants; the median developer debugging a date-formatting bug makes poor cinema. Social feeds surface prodigies algorithmically; the millions of ordinary employed developers post nothing. And working developers themselves perform effortlessness - nobody narrates their week-two despair from three years ago, so you compare your inside (confusion, slowness) against their outside(confidence, jargon) and lose a rigged comparison. The stereotype also quietly serves people: gatekeeping flatters those inside the gate, and “you need a special brain” is a comfortable reason not to start. Recognise the filter, and the evidence underneath it - the actual population of the field - looks like people exactly as ordinary as you suspect yourself of being.
And the timing has never favoured the “average” more. The old filters that DID knock out ordinary people were memorisation grind and the brutal solo stuck-session - and both have been largely patched by AI tutoring, as we’ve detailed in the comeback guide. What the field now rewards - clear thinking, precise communication, judgement about whether things actually work - draws on ordinary adult competence far more than on anything IQ-shaped, which is exactly why employers pay the documented premium to career-switchers who bring it. The bar didn’t drop. It moved onto your home ground.
Retire the question: the two-week test
Here’s the thing about “am I smart enough” - it’s unanswerable from the inside, endlessly re-askable, and it costs you a little every time an AI headline or a friend’s promotion re-opens it. So stop asking it in your head and run the empirical version: two weeks, one hour a day, actually building. The free trial is the packaged test - one signup, no card: real beginner missions on Sigmo, a Socratic AI coach for every stuck moment, and a live Buildroom session with an instructor in the room. Fourteen days later you hold evidence: did the work pull you in, could you explain what you built, was the week-two wobble survivable with support? Either answer wins. Fit confirmed with proof beats years of wondering; fit disconfirmed with proof beats it too - and the Career Compass quiz points somewhere better in two minutes. The only losing move is the one you’ve been making: letting an unanswerable question guard a door you’ve never actually tried.
FAQ
Do you need to be really smart to work in tech?
No - and this comes from people who watch hundreds of beginners cross the line every year: raw intelligence is one of the WEAKEST predictors of who becomes a working developer. The strong predictors are boring and learnable: consistency of hours (the person who shows up daily beats the brilliant sporadic one, every cohort), tolerance for temporary confusion (feeling lost is the curriculum working, and the people who normalise it outlast the people who read it as a verdict), and willingness to build before feeling ready. The genius stereotype describes a tiny research niche and Hollywood; everyday software work is structured, patient problem-solving - closer to assembling furniture with good instructions than to proving theorems.
Why do I feel too average for tech?
Because every signal you’ve received was filtered. Movies show savants, not the millions of ordinary employed developers. Tech Twitter surfaces prodigies, not the median. Job listings describe fantasy candidates. And the developers you know personally tend to perform effortlessness while hiding their years of being confused beginners - nobody posts their week-two despair. Meanwhile you compare your INSIDE experience (confusion, slowness, doubt) against everyone else’s OUTSIDE performance (shipped products, confident jargon). The comparison is rigged. The actual population of working developers is full of former teachers, salespeople, baristas, and self-described "average students" - several of them documented, with names and companies, on our outcomes page.
What actually predicts success in learning to code?
Three things, none of them IQ-shaped. Consistency: protected daily-ish hours beat talent so reliably that we can predict cohort outcomes from attendance patterns alone by week three. Confusion tolerance: everyone feels stupid in weeks two to six - the predictor is whether you interpret that as "the process" (keep going) or "the verdict" (quit); knowing the dip is universal is half the protection. And build-first behaviour: people who make things - badly, early, constantly - outlearn people who study until they feel ready, because "ready" never arrives through study. All three are practices, not gifts. That’s the entire point: the differentiator is available to you.
Has AI made coding easier for average people?
Materially, yes - and specifically at the exact points that used to filter people out. The old filters were memorisation (thousands of syntax details before anything worked) and the brutal stuck-session (a cryptic error, no help, motivation bleeding out at 11pm). AI tutoring removed most of both: syntax is looked up in context, and errors become minutes-long conversations instead of evening-eating walls. What remains - and what employers now pay for - is judgement: clear thinking about what to build and whether it works, which draws on ordinary professional and life skills far more than on any special braininess. The bar didn’t drop; it moved onto ground where "average" people are far stronger than they think.
How do I find out if I can actually do this?
Stop asking the question in your head - it has no answer there - and run the two-week empirical version instead: an hour a day of actually building, with real missions, an AI tutor for stuck moments, and at least one session with a live instructor. Then audit honestly: did the work pull you in? Could you explain what you built? Was week two’s confusion survivable with support? That evidence beats any amount of self-assessment, aptitude quizzing, or asking the internet. The free trial packages exactly this test - one signup, no card - and either outcome wins: fit confirmed with proof, or a question you’ve carried for years finally answered and retired.
The question has guarded the door long enough. Two weeks. One hour a day. Free.
Real missions, a Socratic coach for every stuck moment, an instructor in the room - the empirical answer to a question introspection can never settle. One signup, no card, and fourteen days from now you'll know instead of wonder.
