A
ASSPL - KarnatakaSoftware Engineer
Updated Aug 27, 2026

ASSPL - Karnataka Software Engineer Interview Experiences 2026

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

Get your personalized ASSPL - Karnataka 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
1 week ago
Average Positive Seattle, WA

After applying, I went through an assessment and then a small loop that felt pretty standard for an SDE interview. The first big step was an online assessment with two LeetCode-style problems. A short time later, I had a 45-minute video interview that started with resume review, then moved into one coding question, and ended with time for my questions.

What stood out was how much the later rounds emphasized communication and fit. In the offline/online portions, I discussed my resume alongside a coding round and a general discussion, and the overall focus leaned more toward my projects and how I approached problems. I also remember being told the process could take a while between steps—OA came first, and then the interview landed later—so it wasn’t instant feedback.
1 week ago
Easy Positive Bothell, WA

The process felt unusually light. I didn’t even have a separate recruiter call—after I emailed to schedule an interview day, I ended up doing two back-to-back rounds, each about 45 minutes. The format was consistent across both sessions: half technical and half behavioral.

For the technical parts, I was given LeetCode-style questions, one medium and one easy, and I had to work through them live. The behavioral halves leaned on Amazon-style leadership principles, so the conversation wasn’t just about what I built, but about how I thought, handled tradeoffs, and made decisions.

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

Online Assessment

The interview process begins with an online assessment that typically consists of two LeetCode-style coding problems, often under time constraints. Candidates should prepare for a mix of problem difficulties, including both medium and hard challenges.

LeetCodeCoding problemsTime constraints

Technical Interviews

Following the assessment, candidates participate in back-to-back technical interviews that include coding questions and discussions about time complexity and optimization. It's crucial to clearly articulate thought processes and reasoning while solving problems.

DSATime complexityOptimization

Behavioral Evaluation

Behavioral questions are integrated throughout the interview process, often focusing on Amazon's leadership principles. Candidates should be prepared to use the STAR method to articulate their experiences and demonstrate ownership and decision-making skills.

Leadership principlesSTAROwnership

Interview Structure & Flow

The interview process is structured with multiple rounds, typically blending technical and behavioral components in each session. Candidates should expect a mix of interview formats, including purely behavioral rounds and technical rounds with behavioral interludes.

Structured interviewsMixed formatsBack-to-back rounds

Communication Emphasis

Throughout the interviews, there is a strong emphasis on communication skills, particularly in explaining thought processes during coding tasks. Candidates should practice articulating their reasoning clearly and effectively under pressure.

Communication skillsArticulationPressure handling

Overall Difficulty & Reflection

Candidates report varying levels of difficulty, with some finding the process more challenging than expected due to the need for speed and correctness. Reflecting on the experience, many suggest focusing on both technical proficiency and behavioral depth to improve chances of success.

DifficultySelf-reflectionTechnical vs. behavioral