Fivetran Product Manager Interview Questions
& Process

I interviewed for a PM role. The discussion seemed to need deep expertise in data architecture and data lineage, which is typically handled by data architects, compliance leads, and senior cross-functional leadership. The conversation covered long-term, complex initiatives (6 months to 3 years) in midsize to large orgs, including data flow architecture, domestic and international legal/compliance (like GDPR), user behavior around data access and visibility, and business model design. It was a 30-min PM screen with little context, but it quickly moved to solving high-level, real-world client feedback. It felt like they were seeking answers and not vetting candidates, asking me to brainstorm client pain points they're actively addressing. I should have checked Glassdoor reviews first. There's a feeling this role might not be fully staffed or defined, and the interview felt more like idea mining than a structured evaluation. I hope the team clarifies the role, aligns expectations, and avoids fishing for strategic input during hiring.

The interview process felt a bit disorganized with unclear communication. My initial phone screener wasn't very professional in how they communicated, and the system used to track the interviews kept changing the manager listed for each round, which made it hard to know who to contact before and after each stage. I had a particularly rough time during the product sense round. The interviewer asked a broad question, and when I tried to get some clarification, I received no helpful feedback, essentially being told to make my own assumptions. When I asked about the scope of expansion they were looking for, the response was 'whatever you want it to be.' While I started explaining my approach based on assumptions, I was interrupted mid-answer to explain how their products work. After I did that, I was asked the original question again. It felt like I was guessing what the interviewer wanted. Instead of trying to understand my problem-solving method, they seemed to have a specific solution in mind and weren't interested in hearing my own approach. This left a bad impression, and I wouldn't want to work for or be managed by someone who isn't open to understanding different perspectives or problem-solving strategies. If Fivetran is aiming for aggressive growth, being receptive to candidates with innovative growth ideas would be a good start.

The interview process started with a couple of calls with the hiring manager and the technical recruiter to go over the role's responsibilities. Then, I had a technical challenge focusing on SQL and a final virtual interview with five team members from analytics, product, and engineering. The whole process took about two months, a bit longer than usual because the role was new and the company was in the middle of raising Series C. Even with the extended timeline, I really enjoyed getting to know the hiring manager and learning about the company, the job expectations, and the overall culture.