Real, anonymous reports from people who interviewed for Software Engineer at Castlight, newest first and distilled into what to expect across the loop.
Get your personalized Castlight Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After the recruiter reached out, I ended up going through a fairly technical process that felt geared toward a full-stack role. I had medium-level DSA questions, and then the harder part was system design where the conversation went beyond surface-level diagrams into deeper design decisions and REST API thinking. I also got questions tied to what I had done previously—things like frameworks, specifically Spring and Spring Boot, plus Angular.
The overall vibe was practical: they weren’t just checking buzzwords, they wanted me to connect the interview questions back to how I’d actually built things. The difficulty landed in the medium range, and the process felt structured around coding + design + the web/app stack I’d worked with. I didn’t leave feeling like I’d been tricked by edge cases; it was more about whether I could reason clearly across algorithms, APIs, and system architecture. Ultimately I wasn’t offered the role, but the experience was still aligned with the skills I expected them to evaluate.
> 1 year
Difficult Positive Hyderābād
My process started with multiple technical evaluation rounds—roughly three to four depending on what they wanted to cover—and it felt noticeably more intense than an average screen. The focus was heavy on DSA and technical problem-solving, and it wasn’t just verbal; I could be asked to write down queries during technical rounds.
After the technical portion, there was a follow-up discussion with an HR manager. Across the whole journey, the sequence and pacing made it clear they were taking the evaluation seriously, but I didn’t end up getting an offer. What stayed with me most was how much of the interview time was spent on getting to the details in the technical rounds, rather than anything casual or purely conversational.
> 1 year
Average Negative Bengaluru
My path started through a payroll company intermediary: they gave me an assessment and an initial interview, and once I was shortlisted, the process m…
> 1 year
Easy Positive Hyderābād
My interview experience felt easygoing compared to what I expected. The panel made me comfortable right away, and that helped me answer their question…
> 1 year
Average Positive Hyderābād
I went through a process that felt pretty straightforward once I understood the pattern. It started with coding and fundamentals across four technical…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Technical Evaluation Rounds
Candidates typically go through multiple technical rounds focused on data structures and algorithms (DSA), coding exercises, and system design discussions. The rounds are structured to progressively assess technical skills and problem-solving abilities, often requiring candidates to write code or queries during the interviews.
DSACoding exercisesSystem design
Behavioral and HR Discussions
After the technical assessments, candidates usually engage in discussions with HR or hiring managers, where they may address fit and company culture. The tone of these conversations can vary significantly, impacting candidates' overall impressions of the process.
HR discussionCompany cultureBehavioral questions
Interview Atmosphere and Tone
The atmosphere during interviews can range from high-pressure to relaxed and conversational, influencing candidates' performance. Positive interactions often lead to a better demonstration of skills, while negative experiences can leave candidates feeling judged or uncomfortable.
Candidates frequently report issues with communication throughout the process, particularly regarding follow-up after interviews. Delays in feedback and lack of clarity about next steps can lead to frustration and a negative impression of the company's professionalism.
CommunicationFeedback delaysProfessionalism
Process Length and Structure
The interview process can feel lengthy and disorganized, with some candidates experiencing multiple rounds without clear progression or timely updates. While some found the structure clear initially, many noted that the process often stalled or became confusing as it progressed.
Process lengthStructureOrganization
Expectations vs. Reality
Candidates often enter the process with certain expectations based on initial recruiter interactions, but these can shift dramatically during interviews, particularly regarding role fit and compensation discussions. Discrepancies between what was communicated and the actual experience can lead to dissatisfaction.