How many interview rounds does Acko General Insurance have for Software Engineers, and what is the loop like?

In aggregate, candidates reported 54 interviews for the Software Engineer role at Acko General Insurance. The process is described as lean and fast-paced, with an emphasis on hands-on coding and architectural thinking rather than long process steps. Expect to collaborate through the technical challenge and be ready to explain how your decisions fit user requirements and long-term maintainability.

How hard are Acko General Insurance Software Engineer interviews, based on candidate-reported difficulty and offer outcomes?

Candidates most commonly reported the difficulty as average for the Software Engineer role at Acko General Insurance. Offer rate is listed as 0% in the provided aggregate experience statistics, so you should treat outcomes as uncertain and focus on performing well in the coding and design components.

What topics does Acko General Insurance test for Software Engineers, especially for machine coding and systems like Splitwise?

Machine coding is a central component, including requirement gathering, modular and extensible code, and code quality like error handling. Commonly tested themes include designing core functionalities like a Splitwise-like application core, expense splitting logic, and settlement or minimized payments. You should also be ready for algorithmic problem solving and application design using a modular architecture.

Does Acko General Insurance Software Engineer interviews include concurrent update scenarios and data store trade-offs?

Yes, concurrent expense updates in a multi-user environment is called out, and a public sample question is "Concurrent Expense Updates." The interview materials also include trade-offs like "In-Memory vs Relational Trade-offs" as a public sample question, which aligns with choosing between an in-memory data store and a relational database.

What compensation should I expect for a Software Engineer role at Acko General Insurance?

The provided materials do not include compensation figures for Acko General Insurance Software Engineers, so I cannot state an accurate base or total pay number from this dataset. You should verify pay directly from the specific job posting and level you apply for.

What should I prioritize when preparing for Acko General Insurance Software Engineer interviews?

Prioritize machine coding that turns requirements into clean, modular, extensible code, and practice requirement gathering to identify edge cases and constraints. Focus on system architecture choices for a financial, stateful application, including how you manage state and structure interfaces. Make sure you can explain trade-offs, especially for concurrency and for in-memory versus relational data storage.

Acko General InsuranceSoftware Engineer

Updated Mar 1, 2026

Acko General Insurance Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Acko General Insurance, newest first and distilled into what to expect across the loop.

Get your personalized Acko General Insurance 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.

Build my free plan

Hot & recentNewest first

6 months ago

After reaching out through a cold email for an SDE-1 role in Bangalore, the process felt short and to the point. I only went through two rounds, and the first was a machine-coding round focused on core functionality for a Splitwise-style problem. The whole thing took about an hour.

I started with a quick requirement-gathering step, and then I had to design the core features for the app—essentially thinking through how the product would work before jumping into implementation details. The prompt was centered on designing Splitwise-like behavior rather than just solving an isolated algorithmic task. I could tell the focus was on structure and completeness.

7 months ago

Average Negative Bengaluru

My Acko interview process felt unusually casual. I remember the interviewer making assumptions early and then moving forward as if those assumptions about what I could do were already true, rather than verifying expectations in a grounded way. It left me with the sense that the conversation wasn’t really designed to assess me fairly.

I didn’t get the feeling that the interviewer was trying to understand my background from first principles or calibrate the interview around my experience. Instead, the structure seemed to follow what the interviewer thought the role or candidate should look like. Overall it was a frustrating experience because the process didn’t feel thoughtfully run.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences

Difficulty, sentiment and outcomes
New reports added every week

See all experiences

Share your 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 consists of two to four rounds, including technical coding, system design, and an HR discussion. Candidates should expect a mix of live coding, design exercises, and discussions about past projects and experiences.

Interview roundsTechnical codingHR discussion

Technical & Coding Focus

Candidates will face a variety of technical challenges, including data structures, algorithms, and system design tasks. The emphasis is often on both problem-solving skills and the ability to communicate thought processes clearly during coding.

Data structuresAlgorithmsSystem design

Behavioral & Values Assessment

The HR round typically explores candidates' backgrounds, career aspirations, and alignment with company values. Expect questions that assess adaptability, problem-solving approaches, and cultural fit.

Behavioral questionsCultural fitCareer aspirations

Interview Atmosphere & Interaction

The interview environment can vary from casual to structured, with some interviewers providing hints and guidance during coding tasks. Candidates may experience a mix of supportive and less structured interactions.

Casual atmosphereSupportive hintsStructured interaction

Feedback & Communication

Candidates often report a lack of timely feedback and transparency regarding their application status and interview outcomes. It is advisable to follow up proactively for updates, especially after the final round.

FeedbackCommunicationTransparency

Expectations on Technical Depth

Candidates should be prepared to demonstrate a solid understanding of both front-end and back-end technologies, as expectations can vary significantly based on the role. Some candidates felt that their technical depth was assessed unevenly.

Technical depthFront-endBack-end