Tekion offer

tekion logo
tekion
SDE-1Rejected
October 9, 202516 reads

Summary

I interviewed at Tekion for an SDE-1 role through three offline rounds covering machine coding, low-level design, and managerial topics, which ultimately led to an offer. However, I rejected the offer due to a salary negotiation disagreement.

Full Experience

I recently went through an interview process with Tekion for an SDE-1 position, which consisted of three offline rounds.

Round 1 (45 min to code): Machine Coding

I was tasked with designing a file management system and implementing fully functional methods for cp, mv, mkdir, and pwd.

Round 2 (1 hour round): Low-Level Design (LLD)

I had to design a parking lot system, focusing on outlining all the necessary methods and classes. This round also included several follow-up questions:

  • How to make the system fast while fetching empty slots.
  • A deep dive on Redis cache, including questions about why it cannot be used in place of a primary database.
  • A discussion on Parallelism vs. Concurrency.
  • Some questions derived from my resume.

Round 3 (30 min): Managerial

This round involved discussions about my current project and the components of a movie ticket booking system from a High-Level Design (HDL) perspective. I was also asked which database I would choose for such a system (e.g., MySQL, MongoDB, Cassandra, etc.) and had to explain the CAP theorem in relation to my chosen database, specifically identifying which aspect wouldn't be possible.

After these rounds, I received a call within a week, indicating I was shortlisted. The salary negotiation and the final offer letter took an additional three weeks. I was offered an SDE-1 role with a base salary of 29 LPA, 4000 units of ESOPs (which I found to be of no use), and a joining bonus of 2 LPA. I attempted to negotiate for a 32 LPA base, but it didn't go well, leading me to ultimately reject the offer.

Interview Questions (8)

Q1
Design File Management System
Data Structures & Algorithms

Design a file management system and implement fully functional code for the following methods:

  • cp (copy files/directories)
  • mv (move files/directories)
  • mkdir (make directory)
  • pwd (print working directory)
Q2
Design Parking Lot
System Design

Design a parking lot system. The task was to code the outline of all necessary methods and classes.

Q3
Optimize Empty Slot Fetching in Parking Lot
System Design

Follow-up question to the parking lot design: How would you make the system fast while fetching empty slots?

Q4
Deep Dive on Redis Cache
System Design

A deep dive discussion on Redis cache, including questions like why it cannot be used in place of a primary database.

Q5
Parallelism vs. Concurrency
Other

Explain the differences between Parallelism and Concurrency.

Q6
Components of Movie Ticket Booking System (HDL)
System Design

Discuss the components of a movie ticket booking system from a High-Level Design (HDL) perspective.

Q7
Database Choice for Ticket Booking System
System Design

Which database would you choose for a movie ticket booking system (e.g., MySQL, MongoDB, Cassandra, etc.) and why?

Q8
Explain CAP Theorem and DB Choice
System Design

Explain the CAP theorem and identify which aspect (Consistency, Availability, Partition Tolerance) would not be possible in the database you chose for the ticket booking system.

Discussion (1)

Share your thoughts and ask questions

Join the Discussion

Sign in with Google to share your thoughts and ask questions

Sort by:
Rahul Yadav

Thanks for sharing. Could you share your work experience and how you applied ?