← Back to Directory

HackerRank

Mid-sized

Screna has 3 HackerRank interview write-ups. The most reported round is the system design round (2).

3 interview notes · updated Jun 2026

HackerRank·Software Engineer·Online Assessment (OA)

May 2026
Online assessment for a Software Engineer role at HackerRank. One algorithmic problem that looks deceptively simple until k gets huge and you realize brute force is going to time out badly.
  • There are n friends numbered 1 to n. Each friend i passes the ball to receiver[i] every second, starting from friend 1. Given a potentially very large integer k, which friend holds the ball after exactly k seconds?

“My first instinct was just simulate it, which works fine until you see k can be something like a billion.”

View Post

HackerRank·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at HackerRank for a software engineer role. The whole thing centered on building an internal integration tool from scratch, and they wanted you to go pretty deep on every layer, not just sketch a box diagram and call it done.
  • Design an internal integration tool end-to-end. Walk through requirement clarification, data modeling, backend architecture, and frontend approach.
  • How would you approach database design for this service, considering data volume, filtering needs, and scalability?
  • For the Node.js backend, how would you structure the architecture and what trade-offs would you consider?
  • How do you decide between client-side and server-side rendering for an internal tool, and how does that affect the full-stack data flow?
  • What system-level trade-offs would a senior engineer need to reason through when building and scaling a service like this?

“This felt like one question but was really four interviews stitched together.”

View Post

HackerRank·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at HackerRank for a software engineer role. The whole session was basically one big URL shortener question with the interviewer peeling back layers the entire time.
  • Design a URL shortening service like bit.ly or TinyURL. Walk through your requirements, capacity estimates, and high-level architecture.
  • How would you encode the short URL codes, and how do you handle collisions? Compare a base62 encoding approach versus hashing.
  • Which data store would you choose for this system, and how would you handle sharding and caching?
  • How would you handle cache invalidation, especially for URLs with expiration or that get deleted?
  • How would you add rate limiting and abuse prevention to this service?

“I started with functional requirements which felt fine, but I fumbled a bit on the capacity math.”

View Post