Real, anonymous reports from people who interviewed for Software Engineer at AllianceBernstein, newest first and distilled into what to expect across the loop.
Get your personalized AllianceBernstein 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 a quick résumé review, I jumped into a coding-focused interview delivered over Zoom. The session lasted about an hour, and the interviewer also spent some time giving context about what the role would actually involve. The coding part wasn’t overly elaborate in my case, and the overall difficulty felt average—more like practical exercises than anything insanely tricky.
Once the coding question was done, the conversation shifted into open-ended questions where I had to talk through my background and thought process. I walked away feeling it was a reasonable, friendly exchange, but the overall recruiting timeline felt slow and drawn out. Communication also didn’t feel especially proactive, which made the process drag even when the interview itself went fine.
> 1 year
Average Positive Nashville, TN
My process started with a Zoom conversation that was mostly a background walkthrough plus high-level coding questions grounded in the company’s database technologies. It was an hour, and it felt like they were trying to gauge how I approached coding while thinking about data and systems, not just whether I could recite definitions.
After that, I had another interview with a developer that was more technical—basic SQL work came up alongside a puzzle. The SQL part landed closer to an intermediate level for me, but the puzzle was genuinely difficult and also felt a bit unclear in how it was framed, which threw me off more than the database question did.
> 1 year
Difficult Positive Pune
My interview journey had a surprisingly structured progression. It started with an aptitude-style round—verbal and data interpretation mixed with tech…
> 1 year
Difficult Negative United States
The first thing that wore me down was the pacing and coordination. I went through multiple rounds where scheduling took a lot of effort—there were ema…
> 1 year
Average Neutral Nashville, TN
I began with a recruiter touchpoint and then moved into a phone screening that covered the usual behavioral stuff—why I wanted the role and why I was …
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 & Rounds
The interview process typically includes multiple stages, starting with a recruiter call, followed by technical and behavioral interviews with managers and VPs. Candidates can expect a lengthy sequence that may involve up to six rounds, including both phone and onsite interviews.
Candidates should prepare for a mix of technical questions focusing on coding, data structures, SQL, and problem-solving puzzles. The technical interviews often emphasize practical coding skills rather than theoretical knowledge, and clarity in problem framing is crucial.
Coding skillsSQLProblem-solving
Behavioral Questions
Behavioral interviews are a significant part of the process, often assessing motivation for the role and alignment with company values. Candidates should be ready to discuss their background and experiences using structured formats like STAR.
BehavioralSTARMotivation
Communication & Feedback
Candidates have noted that communication throughout the process can be slow and not very proactive, leading to a drawn-out experience. Feedback may not always align with earlier impressions, which can create frustration.
CommunicationFeedbackTimeline
Interview Environment
The overall atmosphere during interviews is generally friendly and constructive, with interviewers aiming to understand candidates' thought processes. However, some candidates have experienced logistical challenges that detracted from the experience.
Candidates have reported that the scheduling and pacing of interviews can be cumbersome, often involving significant back-and-forth communication. This can lead to a feeling of the process being more about logistics than decision-making.