HackerOne logo

HackerOne Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 31 interview experiences · FREE TO READ

3.6 Rounds average
Average Typical difficulty
83.9% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at HackerOne.

Showing 3 of 31
HackerOne logo
HackerOne

Software Engineer

Engineering · nearly a year ago

Senior Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Technical screen Technical screen Offer
Interview formats
Behavioral Technical Coding System Design

So the whole thing kicked off with a recruiter chat, then I talked to the hiring manager who asked about my background and some behavioral stuff to see if I'd fit in. After that, I had to do a technical test on HackerRank for Rails. Then came a live pair programming session, which was pretty cool and tough. The last technical part was a system design interview about real-world scenarios, and then we talked about the offer. Everyone was super professional and helpful throughout, making sure to understand my background and getting interviews set up when I was free. The recruiter was great at keeping me in the loop and making sure everything ran smoothly.

Confirmed questions1 question
  • Tell me about a difficult yet interesting problem you've tackled in past projects. What was your strategy, and what insights did you gain?
HackerOne logo
HackerOne

Software Engineer

Engineering · a year ago

Mid Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

First, I had a recruiter screen, then I spoke with the hiring manager. After that, there was a technical screen with an engineer, and finally, I had a chat with another engineer. Everyone was really nice and friendly, which helped me relax, especially during the technical part. It felt more like a collaboration than other tech screens I've done; it didn't feel like they were trying to trick me. The people organizing it were also super helpful and flexible when I needed to reschedule. They kept me updated quickly and clearly at every step.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

HackerOne logo
HackerOne

Software Engineer

Engineering

Entry Average Neutral experience No offer 5 rounds
Interview process
Recruiter call Phone screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding

I emailed the company and heard back in about a week. It took another two weeks of back and forth to set up the phone screen because responses were slow. The phone screen covered culture, philosophy, and tools, and HackerOne was very communicative. It then took another two weeks to get confirmation for the in-person interview, again due to slow responses. The in-person part involved lunch, two 1.5-hour pairing sessions where I mostly drove adding features to their existing codebases, and two 1-hour discussions about social/culture aspects. HackerOne asked for references a few days after, which I provided promptly. I followed up three times over three weeks, getting minor updates each time, likely delayed because the last follow-up was around Christmas/New Year's. I got a call two weeks later to inform me they weren't moving forward.

Confirmed questions2 questions
  • Can you discuss your previous work experiences?
  • What are your thoughts on different organizational structures?

HackerOne Software Engineer Interview Questions

Quoted word for word from HackerOne interview reports.

Can you implement the CRUD operations for a dictionary data type?

Read reports

How do you align non-technical executives on technical objectives?

Read report

They asked a systems design question: how would you design twitter? I received this question via email beforehand.

Read report

Implement a multi-stage question in 45 minutes on the HackerRank tool.

Read report

Formats, difficulty and experience

Across all 31 HackerOne interview reports.

Interview formats

Behavioral 35%
Technical 27.5%
Coding 22.5%
System Design 10%
Presentation 2.5%

Interview difficulty

Easy 12.9%
Average 80.6%
Difficult 6.5%

Candidate experience

Negative 9.7%
Positive 83.9%
Neutral 6.5%