SafeGraph Software Engineer Interview Questions
& Process

The interview process was pretty straightforward, made sense, and gave a lot of good info. Everyone I talked to was really easy to approach and friendly. It was a good change from places where interviewers seem checked out, deep in their own work, and just rush through asking a question, your answer, and then call it a day.

The process was well-organized and transparent, with ample time to learn about the engineering team and the company. Expectations for the role and interview were clear. I enjoyed it because I got to learn about their product and future roadmap.

First there was a recruiter screen where we talked about a specific project and my role in it. Then I had a take-home challenge with algorithm and React tasks that took about 30 minutes. The final stage was a virtual onsite with 6-8 people. The first meeting with the Engineering Manager was really hostile. While I was introducing myself and explaining my current work, he kept cutting me off mid-sentence, and the whole atmosphere became confrontational. I tried to de-escalate, but it didn't help at all for the rest of the meeting. He was super rushed and disorganized, asking me questions I had already answered. During a system design discussion, he didn't want to hear my thought process, just wanted quick answers. At the end, I asked him what he liked about working at Safegraph, and he mentioned the workload and startup environment, which raised immediate red flags about overworking engineers. The disorganized interview process made it hard to stay focused and discuss things properly. He ended by wishing me good luck on the rest of my interviews, but then I immediately got a cancellation for all my other interviews with them after our meeting. Looking back, I realize I never stood a chance, and the decision wasn't based on my coding skills.