Interview Process: 3 Rounds · Role: Backend/Software · Outcome: Offer Declined The interview process was certainly memorable — the kind you take notes on so you can narrate it dramatically later. Round 1 – Founder A solid start. We spoke about my background, ongoing work, and then slowly transitioned into a design masterclass. I was asked to: Design a highly available & scalable notification system Explain security considerations for a cloud-based code editor I was also asked a few questions about their own product — which made me reflect on whether this was an interview or market research. Overall, intense but engaging. Round 2 – Technical Round This was a 30-minute sprint of questions that felt like a countdown timer was visible only to the interviewer. Topics included: Sorting algorithms Node.js, MongoDB (sharding, TTL index) SSE vs Polling Load balancing, Clusters, Worker Threads OAuth, JWT AWS Elastic IP It felt less like a conversation and more like a verbal rapid-fire quiz show, minus the prize money. Interaction was minimal, enthusiasm was optional, but the questions kept coming. Round 3 – AI & Tech This round explored AI integrations and architectural thinking. Technically relevant, but by this point, I was half expecting a lightning round sound effect after every question. Why I Declined The expectations seem to exceed not just bandwidth but possibly laws of physics (especially for a fully remote role). The team environment hinted toward "you build it, deploy it, monitor it, fix it, scale it, repeat" — all before lunch. HR communication had a familiar startup pattern: responsive only when the plot demanded it. Summary If your career goal is to speed-run startup experience, fast-track learning, and collect side quests disguised as responsibilities — this may be perfect. If you're looking for structured guidance, collaborative discussions, or the luxury of breathing between tasks — maybe keep scrolling. The company regularly posts job openings, which feels like a marketing initiative with a recruitment side quest. Hard to say which is primary. Pros ✔ Massive learning potential ✔ Exposure to system design, backend, AI ✔ Founder-level interactions Cons ✖ Extremely high expectations vs team size ✖ Interview felt like a one-sided technical exam ✖ HR communication could audition for a “Seen at 9:41 PM” role Advice to Candidates Join if you want growth by fire. Prepare if you want to be challenged. Reconsider if you also enjoy peace.