>
8th Light
8th Light Software Engineer Interview Guide 2026
Complete 8th Light Software Engineer interview guide. Prepare for the craftsmanship-focused process, pairing interviews, test-driven development exercises, and the apprenticeship model of a software consultancy.
5 min read
Updated Sep 2026
5
Rounds6
Categories5 min
ReadTL;DR
8th Light is a software consultancy built on the software craftsmanship movement, and its interview is unlike any big-tech loop, no LeetCode gauntlet, instead a conversation-driven process centered on how you actually write software. Expect an initial screen, a technical conversation about your journey and practices, and a hands-on stage, historically a take-home coding challenge reviewed in depth, plus pairing sessions where you write code test-first with an 8th Light crafter. Clean code, test-driven development, refactoring judgment, and the ability to discuss design trade-offs articulately carry the process. The company runs a famous apprenticeship for earlier-career developers and hires experienced crafters directly. Consultant polish matters, you will sit with clients, and the timeline runs 3 to 6 weeks.
3-6 weeks
Sample Questions
Build tic-tac-toe with an unbeatable computer player
The classic 8th Light take-home shape, minimax is the algorithmic core, but tests-first design, clean abstractions, and commit discipline are the actual evaluation.
Pair with me to add a new rule to your take-home game
A requirement change probing whether your design absorbs extension gracefully, conducted test-first with collaboration quality graded.
Walk me through refactoring this smelly code
Identify duplication and misplaced responsibility, name the refactorings, and proceed in safe, test-protected steps while narrating.
How do you test code that talks to a database?
Test doubles, dependency inversion, and the boundaries between unit and integration tests, applied practice rather than theory recital.
A client insists on skipping tests to hit a deadline. What do you do?
The consulting-professionalism scenario, honest trade-off communication, negotiated scope, and protecting long-term code health with client trust intact.
What have you deliberately practiced recently?
The craftsmanship culture's core question, katas, books, side projects, and feedback loops, evidence of an active learning practice.
About the Interview Process
8th Light's process evaluates the practices big-tech interviews ignore. Rather than timed algorithms, you demonstrate sustained quality, a take-home built with tests and care, then defended in review, and pairing sessions where crafters watch how you decompose problems, name things, respond to feedback, and keep tests green. Conversations explore your learning practice and consulting aptitude, since crafters embed with client teams and often mentor client developers. The apprenticeship path uses the same process with potential weighted over polish.
Initial Screen
Background, motivation, and path fit, experienced crafter versus apprenticeship. Expect real conversation rather than checkbox screening.
Technical Conversation
Discussion of your practices and history, how you test, refactor, learn, and collaborate, with follow-ups probing depth behind claimed habits.
Take-Home Challenge
A scoped coding exercise, classically a game or small system like tic-tac-toe done exceptionally well, evaluated on tests, design, naming, and commit discipline.
Pairing Session(s)
Extend your take-home or tackle a new problem pairing with a crafter, TDD expected, collaboration and responsiveness to feedback graded alongside the code.
Final Conversations
Values, consulting scenarios, and logistics with leadership, mutual assessment of fit for a culture that takes its principles seriously.
Timeline
3 to 6 weeks depending on take-home turnaround and pairing scheduling. Communication is personal and thoughtful throughout.
Tips
Let tests drive your take-home design visibly, reviewers read your commit history, and a test-first narrative in the commits is compelling evidence.
In pairing, verbalize your options before choosing, the session grades collaborative thinking, not typing speed.
When reviewers challenge a decision, engage rather than defend, updating your design gracefully is exactly the crafter behavior they hire for.
Ask about apprenticeship mentoring and client rotation, informed questions about the model signal genuine fit.
What they test
8th Light evaluates software quality as a practiced discipline. The take-home is deliberately simple in scope so that excellence shows in execution, a tic-tac-toe with a clean domain model, tests that read as specifications, and commits that tell a design story beats a feature-stuffed submission every time. Reviews then probe whether you understand your own choices, why this abstraction, what would change with a new requirement, where the design is weakest.
Pairing sessions test the collaborative layer, can you think aloud, share the keyboard, write the test before the code, and treat your pair's suggestions as material to build with. Candidates who pair rigidly or defensively struggle regardless of code quality, the company sells collaborative crafters to clients, and the session simulates the product.
The apprenticeship and the consulting model
8th Light's apprenticeship is a paid program where apprentices study TDD, design, and consulting skills under a mentor before joining client work as crafters, one of the industry's most deliberate on-ramps, and its interview weighs learning trajectory over current polish. Showing a genuine practice loop, books read, katas done, feedback sought, matters more than years of experience for that path.
For experienced hires, remember the consultancy context, crafters embed with client teams, often inheriting legacy codebases and modeling better practices from within. Stories about improving code quality diplomatically, teaching without condescension, and delivering under real client constraints map exactly to the job. Compensation sits at consultancy-market rates below product-company peaks, with the trades being mentorship density, principled culture, and variety of work.
Leveling & Compensation
| Level | Title | YoE | Total Comp (USD/yr) |
|---|---|---|---|
Apprentice | Apprentice Crafter | 0-2 yrs | $50k - $80k |
Crafter | Software Crafter | 2-6 yrs | $85k - $140k |
Principal | Principal Crafter / Technical Lead | 6+ yrs | $120k - $190k |
Apprentice Crafter
Studies TDD, design, and consulting skills full-time under mentorship, progressing through a structured curriculum toward crafter readiness.
Software Crafter
Delivers quality software on client engagements, pairs and mentors, and represents the company's practices with clients.
Principal Crafter / Technical Lead
Leads client engagements and technical direction, develops crafters, and carries pre-sales and architecture responsibility.
How to Stand Out
Behavioral Focus Areas
Craftsmanship: pride in well-made software and deliberate practice
Humility: learning in public, feedback welcomed and applied
Communication: consultants explain and teach as part of the job
Mentorship: the apprenticeship culture runs on teaching
Professionalism: sustainable pace, honest estimates, client trust
1.
Practice TDD until the red-green-refactor rhythm is natural, pairing sessions expect tests first, and retrofitting the habit live is visible.
2.
Polish a take-home to craftsmanship standards, small commits, expressive names, tests as documentation, and a README explaining your design decisions.
3.
Review SOLID principles and refactoring vocabulary, discussing why code is clean matters as much as writing it.
4.
Prepare to pair genuinely, think aloud, invite input, and respond warmly to suggestions, collaboration quality is the explicit rubric.
5.
Read some craftsmanship canon, Clean Code, The Pragmatic Programmer, or Sandi Metz, the shared vocabulary appears throughout the process.
6.
Bring consultant readiness, stories of explaining technical trade-offs to non-engineers and handling client-style pressure.
Related Courses
Recommended Resources
FAQ
Is there really no algorithm interview?
There is no timed LeetCode round. Algorithmic thinking appears organically, an unbeatable game player needs minimax, but the evaluation centers on tests, design, naming, and collaboration. Preparation time goes to TDD practice and katas, not problem grinding.
What languages can I use?
Your choice for take-homes and pairing, the principles are language-agnostic, and crafters work polyglot across client stacks including Ruby, Python, TypeScript, Java, Elixir, and more. Choose the language where your craftsmanship shows best.
Who should apply to the apprenticeship?
Career changers, bootcamp graduates, and early-career developers with demonstrated learning drive. The bar is trajectory and coachability plus baseline programming ability, and the program's alumni network speaks to its quality. Experienced developers skip straight to crafter interviews.
How does consultancy life compare to a product company?
You trade single-product depth for engagement variety, heavy mentorship, and a culture that treats code quality as identity. Client work means adapting to others' codebases and constraints, deeply educational, occasionally frustrating, and the interview's consulting scenarios preview it honestly.
Comments
