• Worked with talented engineers on a large-scale observability platform. • Opportunity to contribute to real-world production code in Java and Spring. • Gained experience with modern DevOps tools and distributed systems. • Flexible work hours and supportive team culture. • Exposure to product-quality standards and performance-focused design.
• Large company structure can sometimes slow down decision-making. • Onboarding was a bit challenging due to complex internal systems. • Limited room for creativity in highly process-driven areas.
Overall 5 rounds: 2 coding and technical rounds: * LeetCode Easy and Medium questions * Data Structures and Algorithms 2 project and technical rounds: * Project * Microservices, Kafka, Core Java 1 Managerial round
Typical LeetCode questions. They didn't ask much about projects or experience. Looking at the reviews, they asked the same question to design an LRU cache to me. On top of that, the platform they use doesn't have IntelliSense or any way to run the co
The interview process was pretty normal. It consisted of: * One phone interview covering technical and HR aspects. * One onsite interview, which included three interviews with the manager and two with team members.
Overall 5 rounds: 2 coding and technical rounds: * LeetCode Easy and Medium questions * Data Structures and Algorithms 2 project and technical rounds: * Project * Microservices, Kafka, Core Java 1 Managerial round
Typical LeetCode questions. They didn't ask much about projects or experience. Looking at the reviews, they asked the same question to design an LRU cache to me. On top of that, the platform they use doesn't have IntelliSense or any way to run the co
The interview process was pretty normal. It consisted of: * One phone interview covering technical and HR aspects. * One onsite interview, which included three interviews with the manager and two with team members.