← Pantomath / Sr. Product Manager
candidate_questions / art_I1foj2FEwkU
Interviewer
Sreevatsan Raman is the VP of Engineering at Pantomath, joining in February 2026 — making him a very recent addition to the company. Before Pantomath, he spent nearly 7 years at Google as an Engineering Leader owning a portfolio of GCP data integration services including BigQuery Data Transfer Service, Cloud Data Fusion (enterprise ETL), and BigQuery Data Prep. Prior to Google, he was Head of Engineering at Cask Data (acquired by Google), where he led development of CDAP, an OSS data analytics application framework. His background is deeply rooted in data integration, ETL/ELT pipelines, and distributed systems — meaning he will likely probe deeply on technical architecture, connector design, API patterns, and production reliability. Shared context with the candidate includes: both have worked extensively with BigQuery and GCP data infrastructure, both have Hadoop/distributed systems exposure (Sreevatsan at Klout/Yahoo, Felix at IBM/Kaiser), and both have experience building developer-facing platforms at scale.
Questions to ask them (20)
| category | question | why |
|---|---|---|
| interviewer_experience | You spent nearly seven years at Google owning BigQuery Data Transfer Service, Cloud Data Fusion, and Data Prep — that's a remarkably broad portfolio of data integration products. What drew you to Pantomath after that experience, and what problem here felt compelling enough to make the move? | Understand his personal conviction about Pantomath's mission, which signals what he'll prioritize and what he'll hold the connectors PM accountable to. Also builds rapport by acknowledging the weight of his Google tenure. |
| interviewer_experience | At Cask Data you led engineering on CDAP, an open-source framework for data analytics applications, and then Google acquired the company and folded it into Cloud Data Fusion. What did you learn from navigating that acquisition and scaling an OSS integration framework inside a hyperscaler that you're now bringing to Pantomath? | Surfaces lessons he'll apply to Pantomath's connector ecosystem — particularly around OSS vs. proprietary trade-offs, partner ecosystem management, and scaling integrations — while demonstrating deep research into his background. |
| interviewer_experience | You joined Pantomath in February 2026, which is relatively recent. What's been the biggest surprise — positive or challenging — in the first few months as you've gotten under the hood of the engineering org? | Gathers candid intelligence about the current state of engineering, technical debt, team maturity, and organizational dynamics without asking anything leading. Also helps calibrate what 'good' looks like to him right now. |
| role_team_dynamics | For the connectors PM role specifically, what does success look like at 30, 60, and 90 days? I want to understand whether you're expecting someone to come in and immediately drive roadmap decisions, or whether there's a deliberate ramp period to understand the existing connector architecture first. | Critical for evaluating fit and setting expectations. Also signals whether the team has a structured onboarding plan or expects the PM to self-direct from day one. |
| role_team_dynamics | How is the connectors engineering team structured today — are there dedicated engineers for specific integration categories like warehouses versus orchestration tools, or is it a shared pool? And how does the PM interface with that team day-to-day? | Reveals team size, specialization depth, and whether the PM will have dedicated engineering bandwidth or be competing for resources — directly affects execution velocity. |
| role_team_dynamics | What are the one or two connector-related problems that are most urgent right now — the ones that, if this hire solves them in the first six months, you'd consider the role a clear success? | Cuts through job description language to understand the actual burning problems. Signals what the interviewer personally cares about and where political capital is being spent. |
| role_team_dynamics | How does the connectors PM role interact with the broader product organization — is there a CPO or Head of Product this role reports to, and how does connector roadmap prioritization get balanced against the core platform roadmap? | Clarifies reporting structure, political dynamics, and whether connectors is treated as a first-class product surface or a supporting function — important for evaluating scope and autonomy. |
| technical_environment | Given your Cloud Data Fusion background — where you were building enterprise ETL connectors at Google scale — how does Pantomath's current connector architecture compare in terms of maturity? Are we talking about a well-established framework that needs optimization, or more of a greenfield build-out? | Anchors the question in his direct expertise to get a candid technical assessment. Helps the candidate understand whether this is a scaling problem or a foundational architecture problem — very different roles. |
| technical_environment | How does Pantomath handle connector reliability and observability today — are there established SLOs, alerting pipelines, and error-rate dashboards, or is defining that framework part of what this PM would own? | The JD explicitly calls out reliability, observability, and error rates as PM responsibilities. Understanding the current state reveals how much foundational work remains versus iterative improvement. |
| technical_environment | When a customer's data environment involves a complex stack — say Fivetran ingesting into Snowflake, dbt transforming, and Airflow orchestrating — how does Pantomath's connector layer handle metadata and lineage across those hops today? Is that a solved problem or an active area of investment? | Tests the depth of the current product and surfaces where the connectors PM will have the most technical design work to do. Also demonstrates the candidate's fluency with the exact stack mentioned in the JD. |
| culture_working_style | You've led engineering teams across very different environments — a scrappy OSS startup at Cask, a hyperscaler at Google, and now a growth-stage company at Pantomath. How would you describe the engineering culture here, and how do you think about the right balance between moving fast and maintaining the production-grade reliability standards the connectors role demands? | Surfaces the real operating tempo and quality bar. The JD emphasizes 'production-grade' and 'strict standards' — understanding how that plays out in practice versus aspiration is critical. |
| culture_working_style | When a PM and an engineering lead disagree on a technical approach — say the PM wants to prioritize a high-demand connector that engineering thinks will be brittle at scale — how does that get resolved on your team? What does healthy disagreement look like here? | Reveals decision-making authority, psychological safety, and whether the PM role has genuine technical influence or is expected to defer to engineering on architecture calls. |
| culture_working_style | How much direct customer and partner access does the connectors PM have? I'm thinking about things like joining technical discovery calls with a Snowflake or Databricks integration partner, or replicating a customer's pipeline environment to validate connector behavior — is that expected and encouraged, or does it go through a different channel? | The JD explicitly calls out replicating customer environments and partner requirements. Understanding whether the PM has direct access or is mediated through sales/CS reveals how grounded the role will be in real-world signal. |
| growth_development | You've grown from Head of Engineering at a startup through Engineering Leader at Google and Databricks to VP of Engineering here. For a Senior PM who wants to grow toward a Director or Head of Product track over the next few years, what does that path look like at Pantomath, and is there organizational appetite to build that out? | Evaluates long-term growth trajectory and whether Pantomath has the organizational maturity to support PM career development — important for a candidate at the Staff/Senior level. |
| growth_development | Given that this role sits at the intersection of product and data engineering, are there opportunities to deepen technical contributions — for example, contributing to connector architecture design, participating in engineering design reviews, or even prototyping integration patterns — or is the expectation that the PM stays on the product side of the line? | The candidate has genuine data engineering depth and wants to use it. Understanding whether the role rewards that depth or constrains it to traditional PM activities is critical for fit and satisfaction. |
| strategy_vision | Pantomath operates in the data observability and lineage space, which has seen significant consolidation — Monte Carlo, Atlan, Alation, and others are all competing for similar real estate. How does the connectors ecosystem serve as a strategic moat for Pantomath, and where do you see it in two to three years? | Tests whether leadership has a clear, differentiated vision for connectors as a competitive advantage versus treating it as table-stakes infrastructure. Also signals how much strategic influence the PM will have. |
| strategy_vision | With Databricks continuing to expand its lakehouse platform — including Spark Declarative Pipelines, which you worked on directly — and Snowflake pushing deeper into data engineering, how is Pantomath thinking about the risk that the major cloud platforms absorb the observability and lineage use cases that connectors currently serve? | Anchors the question in his Databricks experience to signal research depth. Forces a candid conversation about competitive positioning and platform risk — critical for understanding the long-term viability of the connectors roadmap. |
| strategy_vision | Are there specific integration categories — maybe AI/ML pipeline tools, reverse ETL, or streaming platforms — that are on the near-term roadmap but haven't been publicly announced yet, where this PM would have significant greenfield ownership? | Surfaces where the most exciting and high-impact work will be, and whether the role has genuine 0-to-1 ownership opportunities versus primarily maintaining and extending existing connectors. |
| shared_context | I spent several years at Intuit working with BigQuery for telemetry and usage analytics across our developer platform, and I also led a GCP-to-AWS migration for Mailchimp's microservices. Given your deep background building BigQuery Data Transfer Service and Cloud Data Fusion at Google, I'm curious — from your vantage point, what are the most common failure modes you saw enterprises hit when integrating into BigQuery that Pantomath's connectors are specifically designed to prevent? | Builds genuine peer-level rapport by connecting the candidate's BigQuery and GCP experience to Sreevatsan's direct ownership of those products. Demonstrates technical credibility while gathering product intelligence. |
| shared_context | We both have roots in distributed systems work — you were building Hadoop-based data infrastructure at Klout and Yahoo, and I was doing similar work at IBM on BI platforms and later at Kaiser on large-scale SOA infrastructure. As data platforms have shifted from on-prem Hadoop clusters to cloud-native lakehouses, how has that architectural shift changed what 'good' connector design looks like in your view — and how does that inform what you're building at Pantomath? | Establishes a shared technical history and invites a substantive engineering conversation that positions the candidate as a peer rather than just an interviewee. Also surfaces his architectural philosophy for connectors. |
Conversation starters
- I was reading about Cloud Data Fusion and the Cask CDAP acquisition — it's a fascinating story of an OSS data integration framework getting absorbed into GCP. I actually used BigQuery extensively at Intuit for developer platform telemetry, so I have some firsthand experience with the ecosystem you were building. I'd love to hear what that transition from Cask to Google was like from the inside.
- I noticed you were on the Spark Declarative Pipelines team at Databricks before joining Pantomath — that's a product I've been watching closely given how it's reshaping pipeline authoring. What pulled you from Databricks to Pantomath so quickly? It sounds like the opportunity here was compelling.
- Your background spans the full arc of the modern data stack — from Hadoop and MapReduce at Klout and Yahoo, through enterprise ETL at Cask and Google, to lakehouse pipelines at Databricks. I find that kind of longitudinal perspective really rare. I'm curious what you see as the most underappreciated shift in how data engineers actually work today versus five years ago.
⚠ Handle carefully
- Sreevatsan's tenure at Databricks was only 9 months (April–December 2025) before joining Pantomath in February 2026. Avoid asking anything that could imply instability or suggest the short stint was involuntary — frame any Databricks questions around the work itself, not the duration.
- Pantomath is a growth-stage company and Sreevatsan is a very new VP of Engineering (7 months). Avoid questions that imply the engineering org is immature or that suggest you're skeptical of the company's technical foundation — he may still be in the process of assessing and reshaping it himself, and pointed questions could feel like pressure on his still-forming tenure.
- The competitive landscape question around Databricks and Snowflake absorbing observability use cases is high-value but sensitive — frame it as genuine strategic curiosity rather than skepticism about Pantomath's viability, especially since Sreevatsan just made a career bet on the company.