Inito SSE Interview
- Result
- Offer
- Experience
- 2 years
- Posted
- 14 Jun 2024
Summary
I interviewed for a Staff Software Engineer (Backend) position at Inito over four rounds, which included a coding round focused on system design, a technical discussion, a HLD/LLD round, and a CTO discussion. I was ultimately selected and offered an SDE role, as my years of experience and tech stack were deemed more suitable for that position.
How it went
I was approached by Inito's HR on LinkedIn for a Staff Software Engineer (Backend) role. The entire interview process spanned almost a month and consisted of four distinct rounds.
Round 1: Coding Round
This round lasted two hours and was designed to assess my thinking and understanding capabilities. I was challenged to design a logging system. It was a unique and interesting interview, quite different from the 50+ interviews I've given previously.
Round 2: Technical Discussion Round
This round primarily focused on my resume and past experience. We had an in-depth discussion about my projects and the skills I had acquired. It's crucial to prepare thoroughly regarding one's resume for this stage.
Round 3: HLD + LLD Round
This round began with questions testing my knowledge of HTTP/HTTPS and how authorization mechanisms work. Following this, I was asked to design an application for a parking lot, specifically considering large-scale requirements.
Round 4: CTO Discussion
The final round was a conversation with the CTO, mainly revolving around work culture, my ambitions, and future career goals.
Verdict: I was selected for a position, though I was offered an SDE role instead of the SSE role I applied for, as my years of experience and tech stack were considered more aligned with an SDE profile.
Questions asked (2)
- 01
Design a Logging System
System Design
Design a comprehensive logging system. This round was primarily focused on judging my thinking and understanding capabilities.
- 02
Design a Large-Scale Parking Lot Application
System Design
Design an application for a parking lot, specifically considering requirements for a large-scale deployment. This round also covered knowledge of HTTP/HTTPS and how authorization works.