Video summary

From Coding on HackerRank to Working at HackerRank 🔥 | Off-Campus Placement Journey | LogicNLearn

Main summary

Key takeaways

Summary of the video (Off-Campus Placement Journey at HackerRank)

Nupur Singh, a final-year student (batch of 2026) who now works as an FD intern at HackerRank, shares her journey from learning coding to getting hired. She explains what the FD (Forward Deployed Engineer) role involves, how the hiring process works for interns, the assessments/interview rounds she faced, and how her college preparation (DSA + projects + interviews) led to her placement.

1) About the HackerRank FD intern role

  • FD = Forward Deployed Engineer, a mix of:
    • typical software engineering work
    • customer-facing responsibilities
  • The role is described as similar to a startup founder mindset:
    • build features
    • present to customers
    • customize based on customer needs
  • Nupur notes that while open-source is important in some cases, later stages (or other rounds) may focus more on projects and understanding the role.

2) How she got the role (application + selection)

  • She applied through HackerRank’s FD intern career portal.
  • On her first attempt, she was not selected because she didn’t match preferences such as:
    • meaningful open source contributions (e.g., GSoC / GirlScript Summer of Code)
    • plus having a live project generating revenue
  • Later, the CTO reached out after reviewing prior applicants.
  • She reapplied and went through three rounds before receiving the offer.

3) Hiring process and assessment format for FD intern

Nupur describes the typical intern process as:

  • Around September end / October, the opening becomes available.
  • An assessment on HackerRank consisting of three questions:
    1. Coding question (LeetCode-style)
    2. Feature-building question using a repository + AI assistant (build a feature after exploring the repo)
    3. Bug-fix question (identify root cause, fix bugs, optionally use AI, and run tests)
  • After the assessment, recruiters typically follow up in:
    • 3–5 days
    • up to ~1 week if performance is strong

4) Interview rounds for her case (intern FD)

She outlines a process that, in her experience, differed from initial open-source-heavy expectations:

  • Round 1 (CTO)
    • quick screening (about 15–20 minutes)
    • focuses on:
      • projects
      • understanding what she built
      • ability to discuss details truthfully (no bluffing—GitHub may be checked)
    • she mentioned this CTO round was not focused only on open-source, and included discussion of basic projects + college work.
  • Round 2 (Engineering Manager / VP of GTM team, named Rakesh in subtitles)
    • role understanding
    • how she could contribute
    • communication fit and clarity about skills
  • Round 3 (Harry + Rakesh)
    • she had to present a built project using a deck
    • she explained:
      • problem statement
      • why she built it
      • how it helps users
    • follow-up questions covered the project and her technical choices

She also notes that for full-time FD roles, the process is likely longer (more rounds, including deeper technical and peer rounds), while her process was for an intern.

5) Her college placement journey (roller coaster)

Nupur describes how she prepared but still faced setbacks:

  • She started DSA from the first year, but wasn’t consistent early on.
  • During placement season (end of 3rd year), she attended immersions/interviews:
    • she cleared some rounds, but competition was high overall
  • She mentions CGPA ~8.95, and many campus companies required above 9, so she missed “slot one” opportunities.
  • She tried other interviews (e.g., Iron Digital, Bain & Co), but outcomes varied.
  • Ultimately, she received a relevant opportunity in March, and later gained another offer as well.

6) Practice + learning strategy

  • Estimated practice volume:
    • ~530 problems on LeetCode
    • additional practice on Coding Ninjas, HackerRank, GFG
    • total roughly 700+ problems
  • For DSA:
    • preferred language: C++
    • began learning with Love Babbar
    • later switched to Striver for broader coverage (especially graph/DP)
  • She emphasizes that early preparation focused on becoming comfortable with core patterns rather than chasing every new topic randomly.

7) Projects she built (and why they mattered)

Nupur mentions several projects:

  • AI Career Coach (career guidance platform)
    • features included resume-related help, generating MCQ tests, and mock interview support
    • she first used it personally as a tracker and learning tool
  • AI-based agent for HackerRank customer queries
    • treats HackerRank knowledge base as a database
    • uses an LLM to retrieve and generate answers
    • includes a human-in-the-loop step to verify correctness
    • designed to reduce manual effort for internal/customer support

8) Resume-building tips she recommends

Key advice:

  • Do not list anything you cannot justify.
  • Include:
    • GitHub links for projects
    • deployed links if possible
  • If you use metrics, quantify impact with believable numbers and be able to defend them.
  • Keep the resume simple (avoid overly fancy formatting).
  • Put your strongest section near the top—often projects first, which tends to help recruiters/screeners.

9) Advice for students starting in 2nd year (preparation roadmap)

She recommends:

  • Start with DSA fundamentals, since early screening is often coding-based.
  • Pick any web framework you like (it doesn’t matter as much early), but build steadily.
  • Learn how to use AI in your daily workflow, and build AI agents (she views this as an advantage as job markets evolve).
  • Add CS fundamentals, but says it can be learned in a relatively short time.
  • Consider open-source contributions, especially if targeting companies that value it (she regrets not contributing more and strongly suggests doing so).

10) Managing time + consistency

Nupur highlights that her biggest challenge was consistency, especially with college workload.

Her practical approach:

  • If you already have enough DSA grasp, spend time on:
    • solving problems (e.g., maintaining LeadCode-style quotas)
    • learning/working on the tech stack
  • She suggests scheduling classes or structuring study time, and notes that even 1–2 hours/day of independent practice can make a difference.

Speakers (every person mentioned as a speaker)

  1. Nupur Singh
  2. Host / Interviewer (LogicNLearn-style host who asks questions; name not given in subtitles)
  3. CTO (called “CTO himself”; name not given)
  4. Rakesh (VP of GTM team; speaks as interviewer in Round 2/3)
  5. Harry (interviewer in Round 3; speaks as part of the Harry + Rakesh panel)
  6. Shriram sir (mentioned as taking “immersion”; appears as an interviewer/authority in her placement context, but not as dialogue)

Original video