Pelatro Software Engineer Interview Experience (September 2026)

I recently interviewed for the Engineer‑Development role at Pelatro, Bengaluru. The process consisted of four rounds covering Core Java, problem-solving, SQL, debugging, project experience, and behavioral questions.

Interview Timeline Day 1‑Onsite: First two technical rounds at the company's office. Day 2 & 3‑Online: Hiring Manager and HR rounds, conducted online on separate days, one day after another.

Round 1: Technical Interview (Onsite)

This round focused on Core Java, coding, SQL, debugging, and logical reasoning.

Questions included:

• Write an SQL query to identify records that were created or updated.
• How would you debug a thread that runs for a long time?
• Explain Set, HashMap, and the contract between equals() and hashCode().
• Sort a string of numbers based on the sum of digits at odd positions, without using Collections or another array.
• Solve a horse-and-rope logical puzzle.
• Why do we need abstract classes when interfaces can have methods with implementations since Java 8?

Result: Cleared.

Round 2: Technical Interview (Onsite)

This round focused on logical problem-solving and validating my technical experience.

Questions included:

• Given two chessboard positions, determine whether they are the same color.
• Questions based on my resume and previous project experience.

Result: Cleared.

Round 3: Hiring Manager (Online)

This round focused on practical engineering scenarios, project ownership, debugging, and problem-solving.

Questions included:

• Explain how I achieved an 80% reduction in root‑cause analysis (RCA) issues.
• Why was I looking for a job change?
• An API is expected to respond in 5 ms but takes 5 seconds. How would I investigate the issue step by step?
• Find the maximum product of three integers in an array, considering negative numbers as well.

Result: Cleared.

Round 4: HR Interview (Online)

The final round covered behavioral scenarios and general HR discussions.

Topics included:

• How would you handle a release when two out of four team members are on leave?
• Compensation expectations.
• Notice period and availability.
• General questions about my experience and background.

Result: Selected.

Key Takeaways

• Focus strongly on Core Java: Be comfortable with collections, HashMap, equals() and hashCode(), multithreading, and problem‑solving.
• Spring Boot was not a major focus in my interview: Based on my interview experience, much of the technical discussion centered on Core Java and Pelatro's own technologies.
• Practice coding problems with constraints: Some questions restrict the use of built-in data structures, so understand the underlying logic rather than relying only on library methods.
• Prepare your resume thoroughly: Be ready to explain project decisions, measurable improvements, and your individual contributions.
• Practice debugging and real‑world scenarios: Be able to explain a structured, step‑by‑step approach instead of jumping straight to a solution.
• Communicate your reasoning clearly: The interviewer is interested in how you approach a problem, not just the final answer.

Overall, my experience involved a mix of Core Java fundamentals, coding, logical reasoning, practical debugging, and behavioral questions. For candidates preparing for a similar role, I would prioritize Core Java and problem‑solving, while also learning about the company's technology stack.