Who we are
We're a small US-based research team — engineers and technical educators who spent years on both sides of the interview table. We've conducted hundreds of interviews at companies ranging from early-stage startups to the places everyone recognizes by their colored logos. We've also been the person in the chair, sweating through a whiteboard question we definitely knew the answer to but somehow couldn't articulate under pressure.
That second experience is what started this.
The team is deliberately small. We don't have a marketing department. We don't run cohort-based courses. We're not trying to build a platform. We're researchers who identified a problem, studied it, built a solution, and wanted to share it properly — not behind a paywall or a drip-feed email sequence.
The problem that wouldn't go away
Here's what kept bothering us: the people who failed technical interviews were rarely the ones who lacked knowledge. They were the ones who lacked sequence.
We watched strong engineers — people who ship production systems, debug gnarly concurrency bugs, design real architectures — walk into interviews and crater. Not because they didn't know binary search or couldn't reason about consistency models. Because they panicked. They started coding before understanding the problem. They jumped to solutions before evaluating options. They built without a plan and then spent the last five minutes trying to retrofit one.
The pattern was so consistent it hurt to watch.
And the advice available was almost comically unhelpful. "Think out loud." "Practice more LeetCode." "Be confident." That's like telling someone who's drowning to "swim better." The problem was never effort or intelligence. The problem was process — specifically, the absence of one.
The insight
Somewhere in 2022, during yet another debrief where a clearly qualified candidate got a "no hire" because their solution was correct but their reasoning was invisible, one of us said something that stuck:
"The interviewer can't score what they can't see. And this person did all the thinking — they just did it in the wrong order and kept it in their head."
That was the seed. What if there was a fixed sequence — not a rigid script, but a reliable order of operations — that worked across different types of technical challenges? Something that made the thinking visible by default? Something that matched how engineers actually reason when they're at their best, just... made explicit?
We started digging. We looked at cognitive load theory. Chunking research. Expert-novice studies in problem solving. The literature on structured reasoning under time pressure. We interviewed engineers who consistently performed well in interviews and mapped their process. We found that the high performers weren't smarter — they just had a sequence they defaulted to. And those sequences, despite surface differences, shared a remarkably similar skeleton.
Decompose. Evaluate. Plan. Execute. Verify.
We compressed that into five steps, gave them names that were easy to remember, and called it BASIC: Breakdown, Assess, Structure, Implement, Check.
Testing it
We didn't publish it immediately. We spent months testing it with real candidates preparing for real interviews. We used it in mock sessions. We tracked what changed. The results weren't subtle:
- Candidates who used BASIC spent more time on Breakdown and Assess — and less time backtracking during Implement.
- Interviewers reported that BASIC-trained candidates were easier to evaluate. Their reasoning was visible. The signal was clearer.
- The framework transferred across problem types. It worked for LeetCode, system design, behavioral questions, and (later, as tools evolved) AI-assisted research tasks.
- Most importantly: people could learn it in a week and start applying it immediately. It wasn't a 12-week bootcamp. It was a mental model.
The transfer part surprised us. We expected it to be strongest for coding interviews. But the structure — understand the problem, evaluate options, plan, execute, verify — turned out to be universally applicable to any high-stakes, time-boxed, ambiguous task. Which is basically every interview and most meaningful research work.
Why this site exists
We could have written a book. We almost did. But the problem with books is they're static, and interview preparation evolves. New patterns emerge. AI tools change research workflows. The way companies interview shifts every couple of years.
So we built a living knowledge base instead. The 500+ blog posts aren't filler content — they're individual theory cards and practice breakdowns, each one mapping a specific concept or pattern to a specific BASIC step. The docs are the opinionated core. The diagrams exist because we kept drawing the same explanations on whiteboards and eventually decided to make them permanent.
Everything on this site is free. No accounts. No newsletter gates. No "premium tier." We built this because we wanted it to exist in the world, and because we've seen what happens when smart people have access to a good process: they stop losing interviews they should have passed.
About the name
People sometimes ask if "BASIC" is a reference to the programming language. It's not — though we appreciate the coincidence. The name came from trying to describe what the framework does: it gives you the basic operating system for structured thinking. Not the advanced version. Not the expert version. The basic one — the one that works reliably under pressure, every time, without requiring you to be brilliant.
That's the whole point. You don't need to be the smartest person in the room. You need to be the most organized thinker in the room. BASIC is how.
What we're working on
The site continues to grow. We're expanding the research card library, adding more pattern-specific breakdowns for coding interviews, and updating the AI-assisted research section as tools evolve. If you're interested in the research behind the framework, the evidence notes page is the most honest accounting we can give of where the claims come from.
If you have questions, feedback, or want to share how BASIC worked (or didn't work) for you, we read everything. Reach out through the channels listed below.
Basic Framework is a project by an independent research team based in the United States. We are not affiliated with any specific company, recruiting firm, or educational institution. The framework is free to use, share, and adapt.