J'ai postulé en ligne. J'ai passé un entretien chez OneSignal en mars 2026
Entretien
Applied on Mar 2026 (email team, Canada remote).
Recruiter was very friendly and kind. Helped me a lot through out the process . Very responsive.
Inteview questions are average and interviewers were very friendly and helpful. Got all the way to deep dive coding challenge. I thought I did fairly well.
Until then she responded within a day. but this time she didn't and I knew I didn't get it. She sent me a rejection email a week after.
She offered to give me a feedback and I said yes but unfortunately she didn't get back to me.
I wish I could hear back for feedback so I can be better next time, however, I must admit it has been one of the best/fun interview processes in terms of settings, topic.
1
Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer chez OneSignal
J'ai passé un entretien chez OneSignal (San Francisco, CA)
Entretien
Overall it was good , there was a recruiter interview then deep coding .i awaited response for the assessment for a while but hopefully they get back to me soon.
J'ai postulé en ligne. J'ai passé un entretien chez OneSignal en mars 2026
Entretien
Completed four rounds of interviews for a senior engineering position (including a final round, multi-hour virtual onsite): system design, frontend coding, values, and was scheduled for a SQL critical thinking round.
Interviewers themselves were professional and the recruiter was helpful and responsive throughout the scheduling phase. I was told the system design round went well.
The final SQL round was cancelled the morning of, reportedly due to an internal incident. It was never rescheduled. After the cancellation, all communication from the company stopped completely. I sent two polite follow-up emails over the course of a week asking about next steps. No response to either.
Five hours of interviews. PTO used. Significant prep time invested. Zero closure. Not a rejection, not an acknowledgment, not a "we've decided to move forward with another candidate." Just silence.
I don't take issue with not getting the role, that's part of the process. But ghosting candidates after this level of time investment is unprofessional and disrespectful, regardless of how competitive the market is. A two-sentence rejection email takes less than a minute to send. Choosing not to send one tells candidates exactly how the company views their time.
If you're considering interviewing here, go in with open eyes. The technical process itself is reasonable, but be prepared for the possibility that you'll be left hanging at the end with no answer, regardless of how many rounds you completed.
Questions d'entretien [1]
Question 1
The recruiter tells you roughly what each interview will consist of prior to each one.
1. Initial technical round - create an in-memory database.
2. Hiring manager - dive into your background and projects you've worked on.
3. System design - design a frequency capping system. (to limit notifications pushed to a given amount per a given time period)
4. Frontend - React/Typescript - use the public Pokemon API (aka PokeAPI) to create a "Who's that Pokemon?" basic implementation. Display the Pokemon's image, take in a submitted text input, show 'correct'/'incorrect' feedback.
5. Behavioral - questions like "How have you affected culture at your previous roles?", "How have you dealt with a difficult colleague?", etc.
6. SQL - this one was cancelled but I was told it would be a SQL murder mystery so I assume similar to https://mystery.knightlab.com/