
Derived from 1 submission for ALL. Format details may vary across different teams or locations.
The SDE-2 role at Zeta is designed for engineers with 2-4 years of experience, focusing on intermediate to advanced problem-solving in DSA, system design (HLD and LLD), and project deep dives. Candidates are expected to demonstrate practical implementation skills, architectural thinking, and adaptability to feedback. The role may occasionally be downleveled from SDE-3 based on performance, particularly in design rounds.
Focus: Data Structures and Algorithms (DSA) Format: 1-hour session with two medium-level questions. Evaluation Criteria:
Questions Asked:
Source: LeetCode Discussion
Focus: Current project and system architecture Format: 1-hour deep dive into the candidate’s past or current project. Evaluation Criteria:
Key Topics Covered:
Source: LeetCode Discussion
Focus: Designing scalable and testable systems Format: 2-hour session to design a Stock Brokering system with REST API implementation. Evaluation Criteria:
Key Requirements:
Outcome: The candidate provided a design but could not complete a running implementation.
Source: LeetCode Discussion
Focus: High-Level Design (HLD) and REST API Design Format: 1-hour session with a VP to assess fitment. Evaluation Criteria:
Key Topics Covered:
Source: LeetCode Discussion
The candidate successfully cleared all interview rounds for the SDE-2 role at Zeta (Directi) and received an offer. The role was initially intended for SDE-3 but was downleveled to SDE-2 due to experience considerations and mixed feedback from the LLD round. The compensation was matched to the SDE-3 band, with a potential promotion to SDE-3 in a few months.
A 1-hour round focused on Data Structures and Algorithms (DSA). Two medium-level questions were asked, one from Dynamic Programming and another from Graphs requiring BFS traversal. The interviewer assessed the candidate's thought process and accuracy. Both questions were solved within 50 minutes.
A 1-hour round involving a deep dive into the candidate's current project. Discussions covered high-level design, system architecture, tech stack, distributed cache, consistency, concurrency, and Java callbacks with real-life scenarios.
A 2-hour round focused on Low-Level Design (LLD). The candidate was asked to design a Stock Brokering system with REST API implementation for two high-level requirements. The design needed to be testable via Postman and involved threads, concurrency, and Java callbacks. The candidate provided a design using use cases, class relationships, design patterns, and SOLID principles but could not complete a running implementation.
A 1-hour round with a VP to assess fitment. The interviewer focused on REST API design and High-Level Design (HLD) for YouTube, including API design for video upload, search, comments, and retrieval. The candidate also designed the HLD and REST MVC architecture for YouTube.