My process was fairly clean and professional: after an initial step that set expectations, I ended up in a technical round focused on how I approach problems, not just whether I could recite facts. The interviewer pushed me to explain my thinking as I worked through Python topics, and the scope included data pipelines and how to structure things around retrieval-style architecture.
As the conversation continued, we also shifted into system-level territory. I remember covering system design in a fairly direct way, including REST API implementation details, plus fundamentals across databases and deployment concerns. Along the way, I was asked about SQL and NoSQL choices, Python data types, and how a serverless-style API gateway and web server approach might be set up. The interview felt like it had real engineering context—clear questions, smooth flow, and a focus on whether my answers mapped to practical outcomes.
5 months ago
Average Negative Dublin, Dublin
I went through multiple stages that felt mismatched from the start. I first interviewed with a manager, and then I was asked to prepare a presentation on cloud architecture. I was expecting the conversation to stay grounded in the role I was interviewing for, but the questions that followed drifted into building LLM-focused work.
Honestly, it was the most unprofessional interview experience I’d had. The topics didn’t align well with what I understood about the job, and the whole flow left me feeling like the process wasn’t coordinated or thoughtfully targeted.
6 months ago
Average Neutral Bengaluru
Before any real technical work, my experience started with an HR connection that gathered my background and checked the basics from my resume. Schedul…
6 months ago
Easy Positive Bengaluru
My experience was two technical rounds that stayed tightly focused on Salesforce development. The conversations revolved around Lightning Web Componen…
> 1 year
Difficult Positive Gurgaon, Haryana
My interview took a pretty different shape than I expected. Instead of a typical question-and-answer coding session, they gave me random scenarios and…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with an HR call to set expectations, followed by a series of technical rounds that may include a mix of coding, system design, and managerial discussions. Candidates noted that the overall structure felt organized and the timeline was clearly communicated.
HR callTechnical roundsTimeline
Technical / Coding Screen
Candidates experienced a variety of technical assessments, including coding challenges that focused on problem-solving and real-time reasoning rather than rote memorization. The difficulty level varied, but many found the questions to be coherent and relevant to the role.
Interviews often delved deeply into specific technologies relevant to the role, such as Power BI, Salesforce, and Python, with candidates expected to demonstrate practical knowledge and implementation details. This included discussions on data pipelines, system design, and recent updates in the tech stack.
Power BISalesforcePython
Behavioral & Values Assessment
Candidates reported that interviewers assessed not only technical skills but also behavioral aspects, such as communication style and problem-solving approach. The ability to articulate thought processes and engage in discussions was emphasized.
Behavioral questionsCommunicationProblem-solving
Variability in Interview Quality
Experiences varied significantly, with some candidates encountering unprofessional or mismatched interview formats that did not align with their backgrounds. Others felt the interviews were well-structured and relevant, highlighting a lack of consistency in evaluation.
Interview qualityConsistencyProfessionalism
Outcome Reflections
Many candidates left the interviews without offers, reflecting on the experience as constructive despite the outcome. Common takeaways included the importance of preparation and the need for alignment between the interview process and the candidate's experience.