Real, anonymous reports from people who interviewed for Software Engineer at Accion Labs, newest first and distilled into what to expect across the loop.
Get your personalized Accion Labs 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.
My interview was derailed by repeated communication failures, starting with scheduling chaos. The interview was postponed just hours before the agreed time, and I agreed to shift it to the next day. On the new day, I joined a Microsoft Teams meeting and waited to be let in. I was admitted after the scheduled time, but the person who brought me into the meeting immediately left without saying anything.
I ended up sitting alone for the full duration of what should have been a 30-minute interview, with no one showing up to actually conduct the session. I contacted HR while I was waiting to understand what was happening, but I got no response at all. Even after the fact, there was no explanation or follow-up from HR—just silence.
5 months ago
Easy Negative India
The first thing that made my interview feel poorly structured was how disconnected the questions were from realistic engineering work. I went through what I understood to be multiple levels of interview, and the pattern repeated instead of improving.
Early on, one question was essentially a prompt to write a poem to demonstrate my English proficiency. Later, questions asked about how many letters are in the English alphabet—framed more like a repeated basic trivia check across the rounds. I found it hard to take the process seriously, especially since the role and the evaluation didn’t feel aligned with performance engineering or actual software work.
5 months ago
Average Positive Bengaluru
My interview journey was very concept-driven and stayed anchored in core software engineering. After the initial scheduling, I went through four round…
> 1 year
Difficult Negative Pune
My HR round didn’t follow the format I was told. I was informed it would be an HR conversation, but when I arrived at the office, they jumped straight…
> 1 year
Difficult Negative Pune
My interview setup was four rounds that mapped to different technical lenses. I went through L1 and L2 rounds focused on in-depth backend and frontend…
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
Communication & Scheduling Issues
Candidates frequently reported significant communication failures, including last-minute cancellations and lack of follow-up after interviews, which led to frustration and a negative impression of the company’s respect for their time.
scheduling chaoslack of follow-upcommunication failures
Technical Interview Structure
The technical interviews varied widely in structure, with some candidates experiencing disjointed questions that felt disconnected from real engineering tasks, while others found the rounds to be coherent and focused on relevant technical skills.
The perceived difficulty of the interviews ranged from easy to demanding, with some candidates feeling that the questions were trivial or poorly aligned with the role, while others found them to be appropriately challenging and comprehensive.
Behavioral and managerial rounds were often described as inconsistent, with some candidates encountering rude or dismissive interviewers, which negatively impacted their overall experience and perception of the company culture.
Candidates expressed dissatisfaction with the follow-up process after interviews, particularly regarding offer communications, where many experienced delays, lack of clarity, or unprofessional behavior from HR.
offer communicationHR follow-upprofessionalism
Technical Focus Areas
The interviews covered a range of technical topics, including core programming languages, system design, and project architecture, with some candidates noting a strong emphasis on practical application and problem-solving skills.