
Raisin Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 12 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Raisin.
Lead Software Engineer
Started with a friendly recruiter call that laid out a pretty demanding process: a technical screen, reviewing a 'student's' code for a PR, then doing my own mini-project to create a PR, a demo interview, a sprint planning role play, and finally a chat with the hiring manager. Honestly, this is a ton of work for what's actually just a two-year contract, with a review only at 1.5 years. HR said most people get extended, but that's not exactly solid security, especially after all these steps. Another red flag was that the job kept getting reposted while I was interviewing, making it seem like they weren't serious about hiring externally or maybe it's just a formality for internal candidates. The first tech interview started nice but quickly became a 'trivia' session, asking theoretical questions about tech specs that felt like traps, trying to get me to second-guess myself. They also focused on tiny implementation details that are usually automated or caught by linters. It felt more like they wanted memorization than practical seniority. The scope was also unclear – I'd be responsible for four domains, a mobile team, and rotating stakeholders, but couldn't get a straight answer on priorities. Vague answers usually mean a 'crunch' culture. Given the compensation and contract type, it just didn't make sense with that level of responsibility. The code challenge was the most annoying part, a two-parter: first, review code from a 'student' that looked like it was done in under 30 minutes, making their mentoring claims questionable. Then, write my own code for a feature. My feedback on the 'student' code was pedantic, saying I 'struggled' with their internal libraries, which is weird for a Lead role where picking up a library takes minutes. They also critiqued my approach to multi-language support and performance, ironically things their own app seems to lack or do poorly. The whole process felt rigged, like you needed insider knowledge. For a fixed-term, in-office contract, the pedantry and lack of clarity make this a place I wouldn't recommend, not even for their products. It feels like they want to look like they're hiring externally but might be favoring internal moves instead of truly collaborating with new talent.
No confirmed questions were included in this interview report.
Software Engineer
My interview experience with Raisin was quite disappointing. It began with an HR screening, then a follow-up round with an engineering lead to check on cultural and technical fit. After that, I had a live coding interview. I did well and solved all the problems, and the interviewer seemed positive. But then, radio silence. I didn't hear back, so I sent a follow-up email. Six days later, I got a rejection saying they were going with other candidates who were a 'better fit,' with no real explanation. It felt unprofessional given how they present themselves, especially since candidates put in a lot of effort.
- What context-specific questions were asked about the shared coding problem during the live VS Code session, focusing on improving Node.js application performance, working with promises, and identifying asynchronous code bottlenecks or optimizations?
Software Engineer
The hiring process was super welcoming and supportive, I felt valued right away. The steps were structured well, efficient, and designed thoughtfully. Each stage felt practical and clear, making it a smooth and positive experience that shows the company cares about its people.
- Do you have any feedback regarding the hiring process?
Raisin Software Engineer Interview Questions
Quoted word for word from Raisin interview reports.
“Could you build a system that takes in XML and JSON data, reconciles it, and then sends out the outcome?”
Read reports →“Could you provide scenario-based questions on REST API Security Protocols?”
Read reports →“What are your thoughts on Authentication and Authorization?”
Read reports →“Can you discuss Load testing?”
Read reports →“What context-specific questions were asked about the shared coding problem during the live VS Code session, focusing on improving Node.js application performance, working with promises, and identifying asynchronous code bottlenecks or optimizations?”
Read report →“Can you describe a programming challenge related to restful microservices?”
Read report →“Can you discuss architecture questions and how to improve overall? Back up statements with logic”
Read report →“Could you answer Core Java Questions, with basics twisted in a scenario, where you need to improve?”
Read report →“What makes you want to join our company?”
Read report →Formats, difficulty and experience
Across all 12 Raisin interview reports.