interview_prep_doc / art_KTfLRKMqBgA

Content

{
  "markdown": "# Fivetran Interview Prep\n## Questions to Ask Doug Valenta\n\n---\n\n## 1. Interviewer Summary\n\nDoug Valenta is a Senior Engineering Manager at Fivetran (promoted from Engineering Manager in March 2026), based in Portland, OR. He has been at Fivetran for roughly a year and a half \u2014 meaning he arrived during a period of significant company evolution and has navigated the early stages of the Fivetran\u2013dbt Labs integration firsthand.\n\nBefore Fivetran, Doug spent two and a half years as an Engineering Manager at Census, a data activation and reverse-ETL company that sits squarely in the modern data stack. That background makes him an unusually well-calibrated interviewer for this role: he understands ELT pipelines, the enterprise data infrastructure ecosystem, and the PM\u2013engineering partnership that makes or breaks platform work.\n\nHis technical fingerprints are broad and hands-on:\n\n- **Event-driven microservices and distributed systems**\n- **GCP, CI/CD, and cloud-native infrastructure** (including data pipeline work at Nike using Kinesis, SQS, and Lambda)\n- **Brownfield platform evolution** \u2014 he has a recurring career pattern of inheriting complex systems and driving architectural improvement\n- **Building cultures of quality** \u2014 he has written about CI/CD accountability and engineering craft as leadership priorities\n\nAs an Engineering Manager (not a PM or executive), Doug will be evaluating Felix primarily as a **future engineering partner**. He wants to know: Can this PM navigate technical complexity without needing hand-holding? Will they bring clarity to ambiguous platform problems? Can they earn trust with engineers quickly? And will they be a force multiplier on cross-functional alignment, or another source of friction?\n\nThis conversation is likely to feel more like a **peer technical dialogue** than a traditional behavioral screen. Doug will respect questions that demonstrate genuine curiosity about the platform's real state \u2014 not polished corporate enthusiasm. Thoughtful questions here do double duty: they gather signal about the role *and* demonstrate the PM instincts Doug is looking for in a partner.\n\nFelix has meaningful shared context to draw on: platform infrastructure at Intuit (675M+ engagements, GCP-to-AWS migration, microservice CI/CD at scale), search and observability product work at Splunk, and a deep familiarity with the modern data stack that mirrors Doug's own background. That overlap is a genuine asset \u2014 use it to create dialogue, not to lecture.\n\n---\n\n## 2. Best Questions to Ask Doug Valenta\n\n---\n\n### A. Interviewer Experience and Rapport\n\n**Question 1**\n\n> **\"You came to Fivetran from Census, which sits on the other side of the data movement equation \u2014 activating data out of the warehouse rather than moving it in. What surprised you most about how Fivetran's engineering culture or platform challenges differed from what you'd seen at Census?\"**\n\n**Why this is a good question:** It anchors the conversation in Doug's specific career arc, signals that Felix has done real homework on the modern data stack, and invites a candid contrast that reveals genuine cultural and technical texture. The answer will tell Felix a lot about what kind of environment he's actually walking into \u2014 not the version in the job description.\n\n---\n\n**Question 2**\n\n> **\"Your background has a recurring theme of inheriting systems that needed significant architectural evolution \u2014 the brownfield work at Apex, the data platform rewrite at Act-On. Is there a similar 'inherited complexity' story on the Enterprise Platform team that this PM role would be stepping into?\"**\n\n**Why this is a good question:** This is one of the highest-signal questions on the list. Whether this is a greenfield vision role or a brownfield remediation mandate changes the day-one playbook completely. Drawing on Doug's own career pattern makes it feel like genuine curiosity rather than a gotcha.\n\n---\n\n**Question 3**\n\n> **\"You've been at Fivetran through what sounds like a significant moment \u2014 the combination with dbt Labs is mentioned prominently in the job description. What's it been like navigating that transition from an engineering leadership perspective, and how has it shaped what the platform team is focused on right now?\"**\n\n**Why this is a good question:** Acknowledges a major company event without implying anxiety or instability. Invites Doug to share his lived experience of the integration and surfaces how the merger is actively reshaping platform priorities \u2014 which directly affects what Felix would be working on from day one.\n\n> *Softer framing if the topic feels sensitive:* \"I imagine the integration creates both exciting opportunities and some real complexity for platform teams \u2014 I'd love to hear how it's showing up in practice from where you sit.\"\n\n---\n\n### B. Role and Team Dynamics\n\n**Question 4**\n\n> **\"For the Enterprise Platform PM role specifically, what does a strong 30-60-90 look like from your vantage point as the engineering manager? Where do you most want a new PM to be spending their time in the first quarter?\"**\n\n**Why this is a good question:** Gets concrete expectations from the engineering partner \u2014 not just the hiring manager \u2014 which often differ significantly. Doug's answer will reveal where the real gaps are and what \"hitting the ground running\" actually means to the person Felix would work with most closely.\n\n---\n\n**Question 5**\n\n> **\"How is the Enterprise Platform engineering team structured today \u2014 are engineers organized around the security/governance surface, the observability surface, and workspace configuration as separate squads, or is it more fluid than that?\"**\n\n**Why this is a good question:** Team topology directly affects how Felix would organize his roadmap and where he'd need to invest relationship capital first. This is a practical, PM-instinct question that signals Felix is already thinking about execution, not just strategy.\n\n---\n\n**Question 6**\n\n> **\"What's the biggest friction point between product and engineering on the platform team right now \u2014 is it prioritization, requirements clarity, scope creep from enterprise customers, something else?\"**\n\n**Why this is a good question:** A candid, self-aware question that signals Felix wants to walk in with eyes open. Doug's answer will reveal where the PM needs to add the most immediate value \u2014 and whether the friction is structural or interpersonal.\n\n> *Softer framing if needed:* \"Every PM\u2013engineering partnership has its rough edges \u2014 I'd rather understand them upfront than discover them at month three.\"\n\n---\n\n**Question 7**\n\n> **\"The job description mentions 'tight feedback loops' as a feature of this role. Concretely, how does the platform team get signal from enterprise customers \u2014 is there a structured customer advisory board, embedded solutions engineers, direct Slack channels? What's working well and what's still being built out?\"**\n\n**Why this is a good question:** Tests whether the feedback loop infrastructure actually exists or is aspirational. Shows Felix has thought carefully about the PM's discovery motion \u2014 a core competency for this role \u2014 and isn't just accepting the job description at face value.\n\n---\n\n### C. Technical Environment\n\n**Question 8**\n\n> **\"Your background spans event-driven microservices, GCP, and CI/CD \u2014 and the role touches APIs, backend systems, and observability tooling. What does the platform's observability stack look like today, and where are the biggest gaps a PM would be helping to close?\"**\n\n**Why this is a good question:** Connects Doug's technical depth to a specific domain in the role, signals Felix's own technical fluency (observability was central to his Splunk work), and surfaces the actual problem space rather than the aspirational one.\n\n---\n\n**Question 9**\n\n> **\"For the security and governance surface \u2014 things like RBAC, audit logging, SSO \u2014 how mature is the current implementation, and is the roadmap more about hardening what exists or building net-new capabilities for enterprise segments you haven't fully served yet?\"**\n\n**Why this is a good question:** Distinguishes between a \"fix it\" mandate and a \"build it\" mandate \u2014 two very different roles with different skill demands and success metrics. This is a question only a PM with real enterprise platform experience would think to ask.\n\n---\n\n**Question 10**\n\n> **\"Given the dbt Labs integration, are there near-term platform initiatives where Fivetran's and dbt's infrastructure need to converge \u2014 shared auth, unified workspace config, joint observability \u2014 and would this PM be involved in scoping that work?\"**\n\n**Why this is a good question:** Shows awareness of the merger's technical implications and probes whether the role has cross-company platform scope, which would significantly change its complexity, visibility, and career upside.\n\n> *Note:* Keep this framed as curiosity about opportunity, not concern about organizational chaos.\n\n---\n\n### D. Culture and Working Style\n\n**Question 11**\n\n> **\"You've written about building 'cultures of quality' and championing CI/CD accountability across your teams. How does that show up in how the platform engineering team approaches shipping \u2014 are there strong norms around testing, feature flags, and gradual rollouts for enterprise customers?\"**\n\n**Why this is a good question:** Connects directly to language in Doug's own professional writing, signals that Felix values engineering craft, and surfaces the team's actual quality culture versus the aspirational version. It also shows Felix has done genuine research.\n\n---\n\n**Question 12**\n\n> **\"When a PM and an engineering lead disagree on scope or approach for a platform feature \u2014 especially something with security implications where the stakes are high \u2014 how does that typically get resolved on your team? Is there a clear decision-making framework or is it more contextual?\"**\n\n**Why this is a good question:** A candid question about conflict resolution that reveals the PM's actual authority and how much Doug values PM judgment versus engineering judgment. The answer will tell Felix a lot about the real power dynamics on the team.\n\n---\n\n**Question 13**\n\n> **\"The role is hybrid out of Oakland and you're in Portland \u2014 how does the team handle the reality of a distributed setup, especially for the kind of tight PM-engineering collaboration the role description emphasizes?\"**\n\n**Why this is a good question:** Practical and important. Surfaces whether Doug's remote-distributed experience has translated into strong async norms or whether the Oakland in-office days create a two-tier dynamic that could affect Felix's working relationship with the engineering team.\n\n---\n\n### E. Growth and Development\n\n**Question 14**\n\n> **\"You've grown from individual contributor to Staff Engineer to Engineering Manager across several companies \u2014 you've clearly been intentional about your own development. For a Senior PM on the Enterprise Platform team, what's the realistic growth path \u2014 is there a Principal PM track, a path toward platform GM ownership, or something else?\"**\n\n**Why this is a good question:** Acknowledges Doug's own career arc authentically and signals that Felix is thinking long-term. It also surfaces whether Fivetran has a defined senior IC PM ladder \u2014 a real data point for evaluating the offer.\n\n---\n\n**Question 15**\n\n> **\"Given that Fivetran and dbt Labs are actively integrating, do you see opportunities for platform PMs to take on expanded scope as the combined product surface grows \u2014 or is the expectation to go deep on a defined domain?\"**\n\n**Why this is a good question:** Probes whether the merger creates genuine upside for ambitious PMs or introduces org uncertainty that could constrain scope. Framed as curiosity about opportunity, not anxiety about stability.\n\n---\n\n### F. Strategy and Vision\n\n**Question 16**\n\n> **\"The job description mentions 'AI-first opportunities' as something the PM should have an eye toward. From your engineering perspective, where do you see the most credible near-term AI leverage points on the Enterprise Platform \u2014 is it in observability, in configuration automation, in governance tooling, somewhere else?\"**\n\n**Why this is a good question:** Invites Doug to share his technical intuition on AI rather than the marketing version. Felix's own AI background \u2014 from the RL post-training workbench to the aeval platform \u2014 gives him genuine standing to engage with whatever Doug shares here.\n\n---\n\n**Question 17**\n\n> **\"Enterprise platform work often has a tension between building for the long-term architectural vision and shipping incremental value to unblock sales or retain at-risk accounts. How does the team currently balance that \u2014 and is there a framework or is it negotiated deal by deal?\"**\n\n**Why this is a good question:** A sophisticated question that demonstrates Felix understands the core enterprise PM tradeoff. The answer reveals whether the team has a principled operating model or is in reactive mode \u2014 a major signal about the role's day-to-day reality.\n\n---\n\n**Question 18**\n\n> **\"As Fivetran scales to serve larger and more complex enterprise accounts, what's the platform capability you personally think is most underbuilt relative to where the company needs to be in two to three years?\"**\n\n**Why this is a good question:** Invites Doug's candid engineering perspective on the biggest gap. This is often the most honest signal about what the PM will actually be working on \u2014 and it's the kind of question that earns respect from a technically-minded engineering manager.\n\n---\n\n### G. Shared Context and Peer Rapport\n\n**Question 19**\n\n> **\"You spent time at Census doing reverse-ETL and data activation \u2014 I've done a lot of work on the platform and developer tooling side at Intuit and Splunk, thinking about how data moves and gets operationalized across large organizations. From your Census experience, what patterns in how enterprises actually use data activation informed how you think about Fivetran's platform needs?\"**\n\n**Why this is a good question:** Builds genuine peer rapport by connecting Doug's Census background to Felix's platform infrastructure experience at Intuit and Splunk. Creates a real dialogue between two people who have both been in the modern data stack trenches \u2014 rather than a one-way interview dynamic.\n\n---\n\n**Question 20**\n\n> **\"Your profile mentions building data pipelines at Nike using Kinesis, SQS, and Lambda \u2014 event-driven, cloud-native infrastructure. At Intuit I worked on scaling a platform to 675M engagements and led the Mailchimp GCP-to-AWS migration. It sounds like we've both wrestled with the messy reality of cloud-native data infrastructure at scale. What aspects of that experience do you find most relevant to the challenges the Enterprise Platform team is tackling right now?\"**\n\n**Why this is a good question:** Establishes technical peer credibility by referencing a specific, overlapping experience from both Doug's profile and Felix's resume. This is the kind of question that shifts the conversation from interview to genuine peer exchange \u2014 exactly the dynamic that earns trust from an engineering manager evaluating a future PM partner.\n\n---\n\n## 3. Best Conversation Starters\n\nUse one of these in the first 60\u201390 seconds to set a collaborative, peer tone before the formal questions begin.\n\n### On the Census\u2013Fivetran Arc\n\n> \"I noticed you were at Census before Fivetran \u2014 I've spent a lot of time thinking about the data movement and activation space from the platform infrastructure side, so I'm genuinely curious what drew you to Fivetran specifically and what the transition between those two companies felt like from an engineering culture standpoint.\"\n\n### On Building Cultures of Quality\n\n> \"Your summary mentions building cultures of quality in distributed teams \u2014 that resonates with me from my time at Intuit where we were trying to establish CI/CD norms across 30+ product SKUs. I'd love to hear how you've approached that at Fivetran given the scale of the customer base here.\"\n\n### On Cloud-Native Data Infrastructure\n\n> \"The Nike data pipeline work you did with Kinesis and Lambda caught my eye \u2014 I did something similar at Intuit migrating Mailchimp's infrastructure and scaling throughput from 6K to 50K TPS. It sounds like we've both been in the trenches with cloud-native data infrastructure at scale; I'm curious how that background shapes how you think about what the Enterprise Platform team needs to build next.\"\n\n---\n\n## 4. Topics to Handle Carefully\n\n### Doug's Tenure and Institutional Knowledge\n\n**The risk:** Doug has been at Fivetran for roughly 16 months and was just promoted in March 2026. Questions that imply he lacks full context on long-standing platform decisions \u2014 or that probe for signs of instability \u2014 could land as inadvertently dismissive of his experience.\n\n**Ask this instead:**\n> \"I know the platform has a lot of history \u2014 are there decisions or architectural choices that predate your time here that you've had to get up to speed on quickly?\"\n\n**Softening phrases to reuse:**\n- \"From your vantage point since joining...\"\n- \"As someone who's seen the platform evolve over the past year or so...\"\n- \"I imagine there's a lot of institutional context to absorb...\"\n\n---\n\n### The dbt Labs Merger\n\n**The risk:** The integration is clearly ongoing and significant. Questions framed around organizational chaos, job security, or \"what happens to your team\" will signal anxiety rather than strategic curiosity \u2014 and may put Doug in an uncomfortable position.\n\n**Ask this instead:**\n> \"The combination with dbt Labs sounds like it creates some genuinely interesting platform opportunities \u2014 where do you see the most exciting technical overlap from an engineering perspective?\"\n\n**Softening phrases to reuse:**\n- \"I imagine the integration creates some interesting new surface area...\"\n- \"From what I've read, the two companies have complementary infrastructure...\"\n- \"It sounds like an exciting moment to be building platform...\"\n\n---\n\n### Scope of Doug's Authority\n\n**The risk:** Doug is an Engineering Manager, not a PM, product executive, or recruiter. Questions about compensation, headcount decisions, product strategy above the team level, or hiring timelines put him in an awkward position and signal that Felix hasn't thought carefully about who he's talking to.\n\n**Ask this instead:** Keep strategy questions anchored in Doug's engineering perspective and team-level observations. For anything above that level, note it as a question for the hiring manager or recruiter.\n\n> \"From your engineering perspective, how does the team think about...\" is almost always a safe frame.\n\n---\n\n## 5. Best Questions to Prioritize During the Call\n\nIf time is limited or the conversation flows quickly, these five questions will generate the most useful signal \u2014 and make the strongest impression.\n\n1. **Question 2 \u2014 Inherited Complexity:** Is this greenfield vision work or brownfield remediation? The answer changes everything about the day-one playbook.\n\n2. **Question 6 \u2014 Biggest PM\u2013Engineering Friction Point:** The most honest signal about where the PM needs to add value immediately \u2014 and what Doug actually needs from a partner.\n\n3. **Question 9 \u2014 Security/Governance Maturity:** Hardening vs. net-new building are fundamentally different mandates. This question shows enterprise platform fluency.\n\n4. **Question 17 \u2014 Long-Term Vision vs. Incremental Delivery:** Reveals whether the team has a principled operating model or is in reactive mode \u2014 a major signal about day-to-day reality.\n\n5. **Question 18 \u2014 Most Underbuilt Capability:** Doug's candid engineering take on the biggest gap is often the most honest preview of what the PM will actually own.\n\n---\n\n## 6. Suggested Call Flow\n\n### Opening (first 2\u20133 minutes) \u2014 Establish Peer Rapport\n\nStart with a conversation starter, not a formal question. Let Doug talk first.\n\n> \"Before we get into the formal questions, I wanted to say \u2014 I noticed you were at Census before Fivetran, and I've spent a lot of time on the platform infrastructure side of the data stack at Intuit and Splunk. I'm genuinely curious what the transition felt like from your perspective.\"\n\n### After Discussing Background \u2014 Anchor in the Real State of the Platform\n\nOnce Doug has shared some context about his background and the team:\n\n> \"That's really helpful context. I'd love to understand the actual state of the platform \u2014 is there an 'inherited complexity' story here, similar to some of the brownfield work in your background, or is this more of a greenfield build?\"\n\n*(Question 2)*\n\n### When Discussing the Role \u2014 Get Concrete on Expectations\n\n> \"From your vantage point as the engineering manager, what does a strong 30-60-90 look like for this PM? Where do you most want someone spending their time in the first quarter?\"\n\n*(Question 4)*\n\n### When Discussing the Team \u2014 Surface the Real Friction\n\n> \"What's the biggest friction point between product and engineering on the platform team right now? I'd rather understand that upfront than discover it at month three.\"\n\n*(Question 6)*\n\n### Near the End \u2014 Invite Candor on Strategy\n\n> \"As Fivetran scales to serve larger enterprise accounts, what's the platform capability you personally think is most underbuilt relative to where the company needs to be in two to three years?\"\n\n*(Question 18)*\n\n### Closing \u2014 Leave on a Forward-Looking Note\n\n> \"This has been a genuinely useful conversation \u2014 it sounds like there's real, meaty platform work to do here, and the engineering partnership you're describing is exactly the kind of environment where I do my best work. Is there anything about my background or experience you'd want me to address before we wrap up?\"\n\n---\n\n## 7. Final Recommended Question Set\n\nIf the call runs short or Doug drives the conversation, have these four to six questions ready to deploy in any order:\n\n1. **Is this a greenfield vision role or a brownfield remediation mandate?** *(Question 2)*\n2. **What does a strong 30-60-90 look like from your engineering perspective?** *(Question 4)*\n3. **What's the biggest PM\u2013engineering friction point on the team right now?** *(Question 6)*\n4. **For security and governance \u2014 are we hardening what exists or building net-new for enterprise segments you haven't fully served?** *(Question 9)*\n5. **How does the team balance long-term architectural vision against incremental delivery pressure from enterprise accounts?** *(Question 17)*\n6. **What's the platform capability you personally think is most underbuilt for where Fivetran needs to be in two to three years?** *(Question 18)*\n\n---\n\n## 8. Strong Closing Line\n\n> \"I've spent the last several years building platform infrastructure that engineers actually want to use \u2014 from scaling Intuit's ICE platform to 675M engagements to shipping developer SDKs that cut onboarding from weeks to minutes. What excites me about this role is that it sits at exactly the intersection I care about most: enterprise-grade reliability, developer experience, and the kind of platform work that compounds over time. I'd love the chance to bring that to Fivetran's Enterprise Platform team.\"\n\n---\n\n## 9. Final Reminder\n\nThis conversation should demonstrate that Felix is:\n\n- **A genuine peer, not a supplicant** \u2014 Doug is evaluating a future engineering partner, not a subordinate; match his technical register\n- **Curious about the real state of the platform**, not just the aspirational version in the job description\n- **Grounded in the modern data stack** \u2014 the Census/Fivetran/Splunk/Intuit overlap is real shared context; use it\n- **Self-aware about the PM\u2013engineering dynamic** \u2014 questions about friction, decision-making, and working style signal maturity\n- **Forward-looking on AI and platform strategy** \u2014 the RL workbench and AI platform experience are genuine differentiators; let them surface naturally\n- **Prepared to ask, not just answer** \u2014 the quality of Felix's questions will do as much work as any answer he gives",
  "source_artifact_id": "art_7DkvLau1vYE",
  "source_kind": "candidate_questions",
  "doc_type": "questions_to_ask"
}