Hey Everyone!

I recently went through the interview process for Software Development Engineer I (Data) role at Safe Security, and wanted to share my experience:

Profile

Education: B.tech from Tier-2 college.
YOE: 1.6

Interview Process:

Applied on the careers page and after 2 weeks got a mail from recruiter for interview scheduling.

Total Rounds: 4
Mode: Virtual
Compensation Breakdown: https://leetcode.com/discuss/post/7345538/safe-security-sde-i-data-by-anonymous_us-0j3o/

Initial Screening (15 Mins)

A short Google Meet covering why I’m looking for a change and the scale of systems I’ve worked on.
Then the recruiter started asking CS fundamentals—placement-style questions like TCP vs UDP, SQL vs NoSQL, basic OS concepts. Easy to answer. He also asked how hardworking I am on a scale of 0-10.

Technical Round 1 with a Senior Engineer (60 Mins)

First ~35 mins: Deep discussion on data-engineering fundamentals & technologies. He asked situational questions like “Which approach would you choose for X latency/throughput constraints?” and trade-offs around cost vs latency vs durability.
Had an in-dept discussion around these questions

Last ~20 mins:

DSA: Longest Common Subsequence (Complete optimized code and complexity analysis)

SQL: “Return list of users who have actually spent > 10,000 in total” — basic joins + GROUP BY + HAVING.

Technical Round 2 with Manager (60 Mins)

“How would you rate your hardworking level on a scale of 1–10?”
(Their expectation is basically 10. The question itself signals what they consider a norm.)

Deep dive into your past projects: challenges, trade-offs, what you owned.

Random quick question: “What happens when we type google.com?” — networking + DNS + TLS handshake + CDN caching.

System design: Parking lot system — focused on functional & non-functional requirements, database design (table schemas, indexes), which DB to choose (RDBMS vs NoSQL), and the layout of tables.

Situational data-pipeline design: Design a pipeline for high throughput (both read & write scaled) — expected to discuss partitioning, sharding, message queuing, batching, backpressure, scaling read replicas, cache strategies, and monitoring.

HR alignment + CEO connect

HR validated behavioral answers and nudged some responses on a 15 mins call before CEO connect.

Final ~30 min with CEO: quick intro, tech experience, achievements, family background, pride moment, and behavioral questions. Very conversational.

The Offer

Compensation was strong and the role aligned well with my interests.
But after comparing the interview experiences with what people publicly share about the company, I realized that the day-to-day environment wouldn’t align with the kind of work-life balance I want.
I’m extremely dedicated when needed, but I also value boundaries, and I didn’t feel SAFE would allow that. Hence rejected the offer.