Backend Engineer Interview Experience - New York, New York
Process
I applied online. The process took 4 weeks.
A phone interview followed by a take home assignment. Then after the take home assignment another 3-4 rounds of technical interviews, then interview with C-level employee. In my honest opinion, I think they should cut rounds of interviews to 3 because they're not FAANG. For their tier they should just do 3. Once they reach FAANG tier maybe then they can do 5-6 interviews. I rejected offer because they kept low-balling me in salary.
Questions
Q. Design a backend REST API service.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Notable Backend Engineer role in New York, New York.
Success Rate
Notable's interview process for their Backend Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very negative feelings for Notable's Backend Engineer interview process in New York, New York.
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.
- 5.0Important job at inspiring companyIntegration Engineer • Former EmployeeJanuary 12, 2026Pros: There was tons of challenging work and a great team.Cons: Projects are ambiguous and require a lot of hand holding.
- 5.0you will be challenged, but also rewardedML Engineer • Former EmployeeOctober 5, 2021Pros: You'll work on highly impactful products that are loved by customers. Able to take ownership of product features end-to-end (design, develop, implement, deploy, test, QA). Very small amount of bureaucracy, teams can move fast and implement functionalities in the way that they see fit (given high level objectives and not step by step instructions). Open collaborations across teams (design, product, implementation, engineering, ops)Cons: If you like a lot of structure and direction, you may struggle to find your footing. The company moves very fast in terms of product development, processes and technology. There will be pressure to deliver and perform at a high level.
