Real, anonymous reports from people who interviewed for Software Engineer at AlphaSense, newest first and distilled into what to expect across the loop.
Get your personalized AlphaSense 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.
I went through a fairly long, multi-round loop that started with a recruiter call where the process and logistics were explained, and then moved quickly into team conversations. After that, I had a hiring manager chat followed by a longer architecture session, a coding round, and then additional conversations with product and the CEO. The scheduling felt smooth and the communication was clear, and I actually enjoyed the early rounds since they gave me a good feel for how the team worked.
The architecture interview was the part that threw me off. It was described as a 60-minute session split into two halves: a system deep dive and then system design. When the round started, the introductions ate up about ten minutes, and the deep dive ran long because of lots of follow-up questions. As a result, there wasn’t really any time left for the second half. I walked through a backend, event-driven setup triggered by a single third-party integration without user traffic, but I was pulled toward rollout concepts that sounded more user-facing—things like weighted traffic and canary releases. I tried to answer from an infrastructure angle, but it felt disconnected from the system I’d just presented. The whiteboarding tool also caught me off guard since I hadn’t used it before and wasn’t told about it ahead of time.
5 months ago
Average Positive New York, NY
My process felt straightforward from the start: I had a recruiter call to discuss the role and my background, then a hiring manager interview that focused on my resume and projects. We spent time on what interested me about the company and the kinds of challenges I’d handled before.
After that, the technical portion ran in two long blocks. I did a one-hour code review interview, followed by a one-hour system design interview. Those sessions were presented as the main depth areas of the loop, and the whole arc was fairly concise—recruiter and then hiring manager, then deep technical evaluation across code review and system design.
5 months ago
Easy Negative New York, NY
Communication was the biggest problem for me. I had to keep chasing the recruiter multiple times, and it made everything feel harder than it needed to…
5 months ago
Average Neutral Chicago, IL
My journey was brief. It started with a recruiter call, and then I had a technical discussion with an engineer. In the technical round, I was asked to…
5 months ago
Average Negative India
My interviews were derailed mostly by communication and clarity issues. I ran into situations where key parts of the conversation didn’t land because …
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 a recruiter call, followed by a technical interview with the hiring manager, and then multiple technical rounds including coding and system design. Candidates noted that the scheduling was generally smooth, but some experienced delays and communication issues.
Recruiter callTechnical interviewMulti-round
Technical Evaluation
Candidates faced a mix of coding assessments and system design interviews, often including DSA questions and architecture discussions. The technical rounds varied in depth and focus, with some candidates feeling the evaluations were not aligned with their skills or the expectations set by interviewers.
Coding assessmentSystem designDSA
Communication & Feedback
Communication throughout the interview process was a common pain point, with many candidates reporting delays in responses and a lack of constructive feedback after interviews. Some felt ghosted after completing rounds, leading to frustration and disappointment.
Communication issuesFeedbackGhosting
Interview Format & Duration
Interviews were often short, typically around 30 minutes, which some candidates felt limited their ability to showcase their skills and connect with interviewers. Others noted that longer sessions allowed for deeper discussions but could also lead to time mismanagement.
Short interviewsTime managementInterview format
Cultural Fit & Values
Candidates reported that discussions around cultural fit and values were part of the interview process, particularly in later rounds. Interviewers focused on personality traits and communication skills, which some candidates found to be a significant aspect of their evaluation.
Cultural fitValuesPersonality traits
Take-Home Assignments
Some candidates completed take-home assignments that tested their technical skills, but feedback on these assignments was often vague or lacking. This left candidates feeling uncertain about their performance and the expectations of the role.