Supportive colleagues but lack of good leadership
Supportive colleagues but lack of good leadership
Great colleagues. The office in Cambridge is very nice. You can make quick career progression.
Pay and benefits are poor.
The technical debt is ingrained in the company.
Senior leadership are not approachable, and decision making is not collaborative.
A large number of “senior” engineers have only worked here and don’t have enough expertise or experience to make good decisions or drive company culture.
Huge lack of quality assurance.
Improve processes in place and make senior leaders more approachable. Reduce technical debt - less focus on pure feature development.
Additional Ratings
Was this helpful?
Luminance AI Interview Experiences
Software Engineer
The first interview was just a quick chat with some very small system design questions, like how to improve an API, what to take into account when designing an API, and a barcode question.
Software Engineer
First round interview: light chat and a few quick technical questions. Second round interview: more chatting, a bit more technical, but mostly trying to learn about me, then a longer programming exercise.
Software Engineer
Mostly very standard. 5 minutes of introduction, followed by 15 minutes of solving a coding question, followed by 15 minutes of solving a puzzle on the whiteboard, followed by a couple of STAR questions. The puzzle was a pretty weird abstraction of
Software Engineer
April 30, 2026The first interview was just a quick chat with some very small system design questions, like how to improve an API, what to take into account when designing an API, and a barcode question.
Software Engineer
Cambridge, EnglandMay 1, 2025First round interview: light chat and a few quick technical questions. Second round interview: more chatting, a bit more technical, but mostly trying to learn about me, then a longer programming exercise.
Software Engineer
Cambridge, United KingdomMay 11, 2025Mostly very standard. 5 minutes of introduction, followed by 15 minutes of solving a coding question, followed by 15 minutes of solving a puzzle on the whiteboard, followed by a couple of STAR questions. The puzzle was a pretty weird abstraction of
