Process
first round: thirty minute recruiter call second round: one hour take home coding exercise third round: one hour live coding with one other engineer and one former accountant recently turned engineer via bootcamp final round: Panel interview
Questions
Basic coding questions and OOP. The team is not very experienced and has trouble understanding/explaining basic programming concepts. Additionally, the coordination was very confusing and poor. Said I needed a backend web framework and to setup an environment on local, neither of which was needed whatsoever. Overall, the people were okay, but process was extremely inaccurate and confusing.
Was this helpful?
Interview Statistics
The following metrics were computed from 14 interview experiences for the Notable Software Engineer role.
Success Rate
Notable's interview process for their Software Engineer roles is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for Notable's Software Engineer interview process.
Notable Work Experiences
- 2.0Grew too fastSoftware Engineer • Former EmployeeJune 19, 2024Pros: Competitive salary and benefits. Flexible working location, at least while I was there.Cons: On-boarding is a mess and their team organization is horrible. It's clear that they grew extremely rapidly, but never dealt with the organizational changes that needed to happen for their new size.
- 2.0Used to be betterSoftware Engineer • Former EmployeeApril 22, 2026Pros: Product solves needs that could really impact many- lots of opportunities for growth- smart, hardworking, and helpful co-workersCons: - product is great, but constant company pivots led to a loss of focus on improving the product and what the company was created for - opportunities for career growth dampened by mediocre compensation and benefits - new leadership shifted the culture too much - tons of layoffs
- 5.0Good place to solve health care problems with engineering and AISoftware Engineer • Former EmployeeFebruary 4, 2026Pros: - Good salary - Good health care and benefits - Collaborative engineering team with a focus on production and feature iteration - Work/life balance is goodCons: Like most engineering orgs, tech debt can accumulate. Legacy code needs more curation and clean up.
