Evidence notes and source map

This site makes a strong case for BASIC because it fits the work software engineers are actually asked to do: clarify, compare, structure, execute, and verify.

It does not claim that a public randomized BASIC-vs-STAR trial exists. The stronger and more defensible claim is task fit:

• STAR is excellent for behavioral storytelling.
• BASIC is excellent for live technical reasoning.
• BASIC is also a strong control layer for AI-assisted research and human + AI interviewing because those environments increase the importance of planning, source selection, evaluation, and verification.

How to read the source IDs

• S1–S17 come from the original research pack.
• W1–W4 are a small 2026 update set added for the website refresh.

Source map

S1 — Sweller, John (1988). Cognitive load during problem solving: Effects on learning.

• URL: https://doi.org/10.1016/0364-0213(88)90023-7
• Why it matters: Classic cognitive load theory paper arguing that conventional problem solving can consume processing capacity needed for schema acquisition.

S2 — Chi, M.T.H., de Leeuw, N., Chiu, M.-H., & LaVancher, C. (1994). Eliciting self-explanations improves understanding.

• URL: https://doi.org/10.1207/s15516709cog1803_3
• Why it matters: Found that generating self-explanations improves understanding, a strong argument for thinking aloud and narrating reasoning.

S3 — Karpicke, J.D., & Blunt, J.R. (2011). Retrieval practice produces more learning than elaborative studying with concept mapping.

• URL: https://doi.org/10.1126/science.1199327
• Why it matters: Shows that retrieval and reconstruction improve meaningful learning more than a common elaborative study technique.

S4 — Hales, B.M., & Pronovost, P.J. (2006). The checklist—a tool for error management and performance improvement.

• URL: https://www.jvsmedicscorner.com/ICU-Miscellaneous_files/The%20checklist%20tool%20for%20error%20management%20Hales%20J%20Crit%20Care%202006.pdf
• Why it matters: Explains why checklists help in stressful, complex work by supporting recall, standardization, verification, and error reduction.

S5 — Tudor, Margaret T. (1992). Expert and novice differences in strategies to problem solve an environmental issue.

• URL: https://doi.org/10.1016/0361-476X(92)90071-6
• Why it matters: Experts were distinguished by strategies such as reasoning, subproblem breakdown, solution development, and exploring implications.

S6 — Amazon Jobs — Interview Loop / behavioral-based questions and STAR.

• URL: https://www.amazon.jobs/content/en/how-we-hire/interview-loop
• Why it matters: Amazon’s official interview guidance separates behavioral-based questions and STAR from the rest of the loop.

S7 — Amazon Jobs — STAR method transcript.

• URL: https://cdn.cms.amazon.jobs/65/09/416982da46e6a00e09498c287266/transcript-star-method-how-to-ace-your-amazon-interview.docx
• Why it matters: Official transcript explicitly defines STAR as a framework to structure answers for behavioral interview questions.

S8 — Amazon Jobs — Software development interview topics.

• URL: https://www.amazon.jobs/content/en/how-we-hire/interview-prep/software-development-topics
• Why it matters: States that most technical interviews require coding and system design whiteboarding and emphasize applying knowledge efficiently.

S9 — Amazon Jobs — SDE II Interview Prep.

• URL: https://www.amazon.jobs/content/en/how-we-hire/sde-ii-interview-prep
• Why it matters: Lists coding and system design as explicit competencies and gives system-design objectives such as practicality, reliability, scalability, and optimization.

S10 — Karat — Technical Interviewing 101.

• URL: https://communications.karat.com/hubfs/For_Candidates/Tech%20Interviews%20with%20Karat_2022.pdf
• Why it matters: Practical candidate guide emphasizing understanding, optimization, testing, simplifying, explaining trade-offs, and speaking up.

S11 — interviewing.io — Does communication matter in technical interviewing? We looked at 100K interviews to find out.

• URL: https://interviewing.io/blog/does-communication-matter-in-technical-interviewing-we-looked-at-100k-interviews-to-find-out
• Why it matters: Data-driven post showing that coding and problem solving dominate technical outcomes more than pure communication score in coding/system design contexts.

S12 — LeetCode Help Center — LeetCode QuickStart Guide.

• URL: https://support.leetcode.com/hc/en-us/articles/360012067053-LeetCode-QuickStart-Guide
• Why it matters: Describes LeetCode’s interview resources, including Explore cards with a structural approach to company interview questions.

S13 — LeetCode — Top Interview 150 study plan.

• URL: https://leetcode.com/studyplan/top-interview-150/
• Why it matters: LeetCode’s curated must-do list for interview preparation across core categories.

S14 — LeetCode — System Design for Interviews and Beyond.

• URL: https://leetcode.com/explore/featured/card/system-design-for-interviews-and-beyond/
• Why it matters: LeetCode course page emphasizing key design concepts and best practices for system design interviews.

S15 — ByteByteGo — How to Ace System Design Interviews.

• URL: https://bytebytego.com/guides/how-to-ace-system-design-interviews-like-a-boss/
• Why it matters: A practical 7-step system design interview process: requirements, capacity, high-level design, database, interfaces, scalability, reliability.

S16 — Van Gog, T., Kester, L., & Paas, F. (2011). Effects of worked examples, example-problem, and problem-example pairs compared to problem solving.

• URL: https://research.ou.nl/ws/files/1026339/Van%20Gog%2C%20Kester%20%26%20Paas%20-%20CEDPSYCH%202010.pdf
• Why it matters: Example study and example-problem sequences often outperform pure problem solving for novices because they reduce unnecessary search.

S17 — Google Careers — Applying to Google (technical interview prep page).

• URL: https://careers.google.com/stories/applying-to-google/
• Why it matters: Public Google interview-prep page (JavaScript-rendered in some browsers) advises technical candidates to answer logically, show how they derived a solution, and verbalize their thinking.

W1 — OpenAI Help Center — Deep research in ChatGPT (updated 2026)

• URL: https://help.openai.com/en/articles/10500283-deep-research
• Why it matters: Explains the modern deep-research flow: choose sources, review a plan, monitor progress, and verify with citations or source links.

W2 — OpenAI — Introducing deep research (2025 launch, 2026 updates)

• URL: https://openai.com/index/introducing-deep-research/
• Why it matters: Shows the evolution of multi-step research with source control and connected data sources.

W3 — Karat — Human + AI technical interview rubrics (2026)

• URL: https://karat.com/resource/human-ai-technical-interview-rubrics/
• Why it matters: Argues that in AI-augmented interviews, process quality, observable behavior, and evaluation of AI output must be scored explicitly.

W4 — Amazon Jobs — SDE II Interview Prep (current)

• URL: https://www.amazon.jobs/content/en/how-we-hire/sde-ii-interview-prep
• Why it matters: Current employer guidance that still separates behavioral STAR answers from technical coding/system-design performance, and stresses robust, well-tested code plus edge-case checking.

What the evidence supports confidently

These sources support the following claims well:

• ordered, explicit problem solving lowers drift and makes reasoning easier to inspect
• verification steps matter in stressful, complex work
• technical interviews reward decomposition, trade-offs, implementation quality, and checking
• STAR is still the standard delivery frame for classic behavioral answers
• AI-assisted work makes process quality and oversight more important, not less

What the evidence does not support directly

• a public head-to-head randomized trial proving BASIC beats STAR in every interview type
• a claim that one framework should replace all others

That is why this site frames BASIC as the best-fit operating model for technical and AI-assisted work, not as a universal answer to every interview question.