OneSignal logo

OneSignal Interview Questions
& Process

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

Based on 42 interview experiences · FREE TO READ

3.7 Rounds average
Average Typical difficulty
50% Positive experience

Which role are you interviewing for?

20 roles · 42 reports

Candidate interview experiences

First-hand accounts from people who interviewed at OneSignal.

Showing 4 of 42
OneSignal logo
OneSignal

Senior Software Engineer

Engineering · a year ago

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

The interview process was split into several steps. First, I had a phone call with a recruiter where we talked about my experience and what OneSignal was looking for. Next, I had a call with one of the engineering managers. We spoke for about an hour and covered my background, the kind of work I'm interested in, and what I'd be looking for in a role. After that, I was invited to two technical interviews. These were more hands-on — I was asked to share my screen and work through a coding challenge or task that was given at the start of each session. I didn’t know exactly what the tasks would be ahead of time, but I was told the general area they’d focus on (like front-end or in-memory databases), which helped me prepare a bit. The final stage was a “virtual onsite.” I had the option to do it remotely and split it over two days, which was really convenient. It involved a series of interviews with different team members from engineering, product and HR. Everyone I spoke to was friendly, and the interview challenges were clearly explained. Throughout the process, the recruiter regularly checked in to see how things were going and was happy to adjust the pace of the interviews based on my schedule, which I really appreciated.

Confirmed questions5 questions
  • Can you walk me through a project you led in a previous role, including the trade-offs you made, why you made those decisions, and what you might do differently if you had the chance to start over?
  • Tell me about your experience and what OneSignal is looking for in a candidate.
  • We discussed my background, the type of work I'm interested in, and what I'd be looking for in a role.
OneSignal logo
OneSignal

Account Executive

Sales · a year ago

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

I went through five rounds of interviews at OneSignal, which included a final presentation. The beginning of the process was good, but it got disappointing at the end. After the last round, they said I'd hear back by the end of the week. I followed up, but they went silent for over a week past that. It felt dismissive after all the work I put in, especially for the final presentation. I ended up withdrawing my application because I got another offer. I told them my feedback hoping they'll be more transparent with future candidates. It's a shame because I was really excited about this job. I hope OneSignal uses this feedback to get better at communicating with candidates.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

OneSignal logo
OneSignal

Staff Engineer

Engineering · a year ago

Staff Easy Negative experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen Onsite Panel
Interview formats
Behavioral Coding Technical Behavioral

Started with a recruiter screen, then an internal recruiter screen with the same questions. Next was a live coding test with a developer and a live platform test with a platform engineer. Then, I interviewed with the head of platform engineering and finally with the head of people. I had to keep asking for feedback and to move forward because it was never given. After all that, they said I didn't have enough technical seniority, even though I passed the technical assessment, four weeks later. The hiring manager seemed really tired and annoyed in one of the last interviews, which was a bummer. I wasn't shocked to get rejected, especially after having to ask for feedback again.

Confirmed questions3 questions
  • Debug issues on a VM with a webserver.
  • Debug issues on a VM with a database.
  • Work through provided platform test scenarios, acknowledging their potential irrelevance to the company's tech stack.
OneSignal logo
OneSignal

Customer Support Engineer

Engineering · more than a year ago

Entry Average Negative experience No offer 7 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Background check Offer
Interview formats
Behavioral Technical Coding

Recruiter reached out about a role, went for a screening, it was a fit. Then a hiring manager chat about motivation, why move companies, interest in OneSignal. Recruiter said it went well, then got a take-home. Did the take-home. Another hiring manager chat. Met the team, 1-on-2 scenarios 3-4 times, each an hour. Then interviewed with the VP and COO, both went well. Final chat with the hiring manager again. This whole thing took 7-8 weeks. Lots of unnecessary interviews. Kept interested because they kept saying I was the strongest candidate, the team wanted me, and could see me as a manager. Felt lied to about why I wasn't hired, got a generic "exec team hasn't chosen anyone because it isn't the right time". Ticked every box and was told so by everyone. They tried to hire my colleagues shortly after, some less qualified. Wouldn't want to work for a company that lies, inflates you, deceives, wastes time, and offers disrespect.

Confirmed questions3 questions
  • What's your interest in OneSignal?
  • What drives you?
  • Have you worked with SDKs or APIs before?

OneSignal Interview Questions

Quoted word for word from OneSignal interview reports.

Build an in-memory database using a partner-coding approach.

Read reports

How would you implement a form submission using vanilla JavaScript?

Read reports

Formats, difficulty and experience

Across all 42 OneSignal interview reports.

Interview formats

Behavioral 41.5%
Technical 26.6%
Coding 16%
Presentation 5.3%
System Design 4.3%

Interview difficulty

Easy 23.8%
Average 59.5%
Difficult 16.7%

Candidate experience

Negative 31%
Neutral 19%
Positive 50%

Reports by job function

Engineering 23
Sales 9
Marketing 3
Analytics 2
Design 2
HR 1