
Lumenalta Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 64 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Lumenalta.
Software Engineer
I started with a recruiter call. Then I had two take home tests for a mobile and javascript fullstack role. After passing both, I did a live coding interview with another developer. I got good feedback on the tests and coding interview. They didn't have a project for me then, so they put my profile in 'active' and said they'd let me know about projects. It's been 3 months with vague communication from the recruiter about potential projects. I'm now questioning if they're just after resume/salary info or if they hired someone else without telling me.
- Fix a React app for the fullstack take home test.
- Write a Node.js script to download files.
- Write a SQL script to query some data.
Software Engineer
First, there was a recruiter interview, which was more like a chat to get a feel for your background, skills, what you're looking for, your English level, and salary expectations. They also use this time to tell you about the company and its culture. Second, a tech assessment, which was a coding challenge tailored to what you and the recruiter discussed in terms of skills and programming language. Mine was in Javascript and involved fixing a real-world application with broken unit tests, plus some extra tasks like implementing a debounce function. Third, an HR Manager interview, which was similar to the recruiter chat but dug deeper into your soft skills, career goals, past experiences, and how you handle problems. Finally, they sent an offer with a project brief and a contract, and then we negotiated.
- Can you describe your most interesting project?
- Describe a conflict situation you experienced.
Software Engineer
In summary, I'd suggest avoiding this company if you can. I went through several interview stages and then got an email saying I wasn't a good fit for their open positions. It's strange because they invite people to multiple stages if they're not a good fit. After the first interview, they mentioned having many open roles and that my skills aligned with their needs. I passed a technical coding challenge and was invited to a follow-up round, which was a general discussion about the technologies, frameworks, and stacks I've used. Honestly, if someone's skills don't match your expectations, you should be able to tell in the first or second interview or technical test. It's not right to waste people's time, energy, and effort just to reject them for a weak reason. It's funny how these companies claim to be professional, but their actions don't reflect that. They tell you to research their hiring process before interviews, but they don't even stick to their own stages. At least update your templates and websites. If you do get to the interview stage, be prepared to hear a lot about their $1500 yearly self-improvement allowance, which they seem very proud of. It's not a significant amount, especially considering it's yearly and there are no bonuses. The only positive aspect I can mention is that the interviewers were friendly.
- What are your basic technical questions regarding the technologies or frameworks that you worked on?
- Can you complete an off screen coding challenge?
- Are there any personal/behavioral questions?
Lumenalta Software Engineer Interview Questions
Quoted word for word from Lumenalta interview reports.
“How can one optimize build time and size in webpack?”
Read reports →“Can you explain the Rabin Karp algorithm and provide examples of its use?”
Read reports →“Given a task to build Restful API services using Golang and write unit tests for it, ensure all tests pass.”
Read reports →“What are the ways to fetch data from the backend?”
Read reports →“Can you explain what the event loop is and describe its functionality?”
Read report →“Solve a JavaScript Async Parallel Programming coding task within a 1h 30m time limit.”
Read report →“Solve a problem using DevSkiller, covering Ruby on Rails and MySQL querying.”
Read report →“Tell me about your travel plans for the next 9 months.”
Read report →“Could you solve a bunch of bugs and issues inside of a code project?”
Read report →Formats, difficulty and experience
Across all 64 Lumenalta interview reports.