interview_prep_doc / art_TIoUJmDoc3U

Content

{
  "markdown": "# Pantomath Interview Prep\n## Questions to Ask Sreevatsan Raman \u2014 VP of Engineering\n\n---\n\n## 1. Interviewer Summary\n\n**Sreevatsan Raman** joined Pantomath as VP of Engineering in February 2026, making him roughly seven months into the role at the time of this interview. His tenure is recent enough that he is likely still actively assessing and reshaping the engineering organization \u2014 keep that in mind when asking anything that could feel like a critique of the current state.\n\nBefore Pantomath, Sreevatsan spent nearly seven years at Google as an Engineering Leader owning a portfolio of GCP data integration products:\n\n- **BigQuery Data Transfer Service** \u2014 managed, scheduled data ingestion into BigQuery from first- and third-party sources\n- **Cloud Data Fusion** \u2014 Google's enterprise ETL/ELT service, built on the open-source CDAP framework\n- **BigQuery Data Prep** \u2014 self-service data preparation and transformation tooling\n\nPrior to Google, he was **Head of Engineering at Cask Data**, where he led development of CDAP, an open-source data analytics application framework. Google acquired Cask and folded CDAP into Cloud Data Fusion \u2014 giving him firsthand experience navigating an acquisition and scaling an OSS integration framework inside a hyperscaler. He also had a brief stint at **Databricks** (approximately nine months, April\u2013December 2025) working on Spark Declarative Pipelines before joining Pantomath.\n\nHis background is deeply rooted in **data integration, ETL/ELT pipelines, distributed systems, and developer-facing platform engineering**. Expect him to probe hard on technical architecture, connector design patterns, API reliability, and production observability. This will not be a soft product conversation \u2014 he will want to see genuine data engineering depth.\n\n**Shared context worth leaning into:**\n\n- You both have extensive hands-on experience with **BigQuery and GCP data infrastructure** \u2014 you used BigQuery at Intuit for developer platform telemetry and led the Mailchimp GCP-to-AWS migration; he built the products you were using\n- You both have roots in **distributed systems and large-scale data infrastructure** \u2014 his at Klout/Yahoo on Hadoop, yours at IBM on BI platforms and at Kaiser on SOA infrastructure\n- You both have experience building **developer-facing platforms at scale** \u2014 his on the integration framework side, yours on the SDK/DevPortal/platform infrastructure side at Intuit\n\nThis is a conversation between two people who have lived inside the modern data stack from different angles. The best questions will feel like peer-level technical dialogue, not a candidate asking a hiring manager for information.\n\n---\n\n## 2. Best Questions to Ask Sreevatsan Raman\n\n---\n\n### A. Interviewer Experience and Rapport\n\n**Question 1**\n\n> **\"You spent nearly seven years at Google owning BigQuery Data Transfer Service, Cloud Data Fusion, and Data Prep \u2014 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?\"**\n\n**Why this is a good question:** Understanding his personal conviction about Pantomath's mission tells you what he will prioritize and what he will hold the connectors PM accountable to. It also builds genuine rapport by acknowledging the weight of his Google tenure \u2014 this isn't a throwaway compliment, it's a real signal that you've done your homework.\n\n---\n\n**Question 2**\n\n> **\"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 \u2014 and what from that experience are you now bringing to Pantomath?\"**\n\n**Why this is a good question:** This surfaces the lessons he will apply to Pantomath's connector ecosystem \u2014 particularly around OSS versus proprietary trade-offs, partner ecosystem management, and what breaks when you scale integrations from startup to enterprise. It also demonstrates that you understand the arc of his career, not just his last job title.\n\n---\n\n**Question 3**\n\n> **\"You joined Pantomath in February 2026, which is relatively recent. What's been the biggest surprise \u2014 positive or challenging \u2014 in the first few months as you've gotten under the hood of the engineering org?\"**\n\n**Why this is a good question:** This is one of the highest-signal questions on the list. It gathers candid intelligence about the current state of engineering, technical debt, team maturity, and organizational dynamics \u2014 without asking anything leading or presumptuous. It also respects that he may still be forming his own assessment, which makes him more likely to answer honestly.\n\n> *Softened framing if the conversation calls for it:* \"I imagine the first few months in a new VP role involve a lot of discovery \u2014 what's been the most interesting thing you've uncovered so far?\"\n\n---\n\n### B. Role and Team Dynamics\n\n**Question 4**\n\n> **\"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.\"**\n\n**Why this is a good question:** This is critical for evaluating fit and setting realistic expectations on both sides. It also signals whether the team has a structured onboarding plan or expects the PM to self-direct from day one \u2014 two very different working environments.\n\n---\n\n**Question 5**\n\n> **\"How is the connectors engineering team structured today \u2014 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?\"**\n\n**Why this is a good question:** Reveals team size, specialization depth, and whether the connectors PM will have dedicated engineering bandwidth or be competing for resources across the platform. This directly affects execution velocity and how much of the role is roadmap strategy versus resource negotiation.\n\n---\n\n**Question 6**\n\n> **\"What are the one or two connector-related problems that are most urgent right now \u2014 the ones that, if this hire solves them in the first six months, you'd consider the role a clear success?\"**\n\n**Why this is a good question:** This cuts through job description language to surface the actual burning problems. The answer tells you what Sreevatsan personally cares about and where organizational energy is being spent \u2014 far more useful than anything written in a JD.\n\n---\n\n**Question 7**\n\n> **\"How does the connectors PM role interact with the broader product organization \u2014 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?\"**\n\n**Why this is a good question:** Clarifies reporting structure, political dynamics, and whether connectors is treated as a first-class product surface or a supporting function. The answer reveals how much autonomy and strategic influence the role actually carries.\n\n---\n\n### C. Technical Environment and Architecture\n\n**Question 8**\n\n> **\"Given your Cloud Data Fusion background \u2014 where you were building enterprise ETL connectors at Google scale \u2014 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?\"**\n\n**Why this is a good question:** Anchoring the question in his direct expertise makes it feel like a peer conversation rather than a candidate fishing for information. The answer tells you whether this is a scaling problem or a foundational architecture problem \u2014 two very different roles with very different risk profiles.\n\n> *Softened framing if needed:* \"I know you're still relatively new here, so even a directional sense would be helpful \u2014 is the connector framework something you inherited in solid shape, or is there significant architectural work ahead?\"\n\n---\n\n**Question 9**\n\n> **\"How does Pantomath handle connector reliability and observability today \u2014 are there established SLOs, alerting pipelines, and error-rate dashboards, or is defining that framework part of what this PM would own?\"**\n\n**Why this is a good question:** 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 \u2014 and whether the PM will be building the measurement system or optimizing against one that already exists.\n\n---\n\n**Question 10**\n\n> **\"When a customer's data environment involves a complex stack \u2014 say Fivetran ingesting into Snowflake, dbt transforming, and Airflow orchestrating \u2014 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?\"**\n\n**Why this is a good question:** Tests the depth of the current product and surfaces where the connectors PM will have the most technical design work to do. It also demonstrates fluency with exactly the stack named in the JD \u2014 Fivetran, Snowflake, dbt, Airflow \u2014 without being a recitation of the job posting.\n\n---\n\n### D. Culture and Working Style\n\n**Question 11**\n\n> **\"You've led engineering teams across very different environments \u2014 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?\"**\n\n**Why this is a good question:** Surfaces the real operating tempo and quality bar. The JD uses language like \"production-grade\" and \"strict standards\" \u2014 understanding how that plays out in practice versus aspiration is critical before accepting an offer.\n\n---\n\n**Question 12**\n\n> **\"When a PM and an engineering lead disagree on a technical approach \u2014 say the PM wants to prioritize a high-demand connector that engineering thinks will be brittle at scale \u2014 how does that get resolved on your team? What does healthy disagreement look like here?\"**\n\n**Why this is a good question:** 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. Given that this role explicitly requires data engineering depth, understanding how that depth is actually used in practice matters.\n\n---\n\n**Question 13**\n\n> **\"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 \u2014 is that expected and encouraged, or does it go through a different channel?\"**\n\n**Why this is a good question:** The JD explicitly calls out replicating customer environments and working with partner requirements. Understanding whether the PM has direct access or is mediated through sales and CS reveals how grounded the role will be in real-world signal \u2014 and how much of the data engineering background will actually get used.\n\n---\n\n### E. Growth and Development\n\n**Question 14**\n\n> **\"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?\"**\n\n**Why this is a good question:** Evaluates long-term trajectory and whether Pantomath has the organizational maturity to support PM career development. At the Staff/Senior level, this is a reasonable and expected question \u2014 it signals ambition without being presumptuous.\n\n---\n\n**Question 15**\n\n> **\"Given that this role sits at the intersection of product and data engineering, are there opportunities to deepen technical contributions \u2014 for example, participating in connector architecture design reviews, or even prototyping integration patterns \u2014 or is the expectation that the PM stays on the product side of the line?\"**\n\n**Why this is a good question:** Your background is genuinely technical \u2014 you've built production pipelines, worked hands-on with BigQuery, and shipped developer infrastructure at scale. Understanding whether the role rewards that depth or constrains it to traditional PM activities is critical for both fit and long-term satisfaction.\n\n---\n\n### F. Strategy and Competitive Vision\n\n**Question 16**\n\n> **\"Pantomath operates in the data observability and lineage space, which has seen significant consolidation \u2014 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?\"**\n\n**Why this is a good question:** 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 connectors PM will actually have on company direction.\n\n---\n\n**Question 17**\n\n> **\"With Databricks continuing to expand its lakehouse platform \u2014 including Spark Declarative Pipelines, which you worked on directly \u2014 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?\"**\n\n**Why this is a good question:** Anchoring this in his Databricks work signals genuine research depth and positions you as a peer who tracks the space. It also forces a candid conversation about competitive positioning and platform risk \u2014 critical for understanding the long-term viability of the connectors roadmap.\n\n> *Softened framing to avoid sounding skeptical:* \"I ask this as someone who finds the space genuinely exciting \u2014 I'm curious how you think about where Pantomath's connectors create durable differentiation as the platforms keep expanding.\"\n\n---\n\n**Question 18**\n\n> **\"Are there specific integration categories \u2014 maybe AI/ML pipeline tools, reverse ETL, or streaming platforms \u2014 that are on the near-term roadmap but haven't been publicly announced yet, where this PM would have significant greenfield ownership?\"**\n\n**Why this is a good question:** 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. Given your track record of 0-to-1 builds, this is a natural fit question.\n\n---\n\n### G. Shared Technical Context\n\n**Question 19**\n\n> **\"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 \u2014 what are the most common failure modes you saw enterprises hit when integrating into BigQuery that Pantomath's connectors are specifically designed to prevent?\"**\n\n**Why this is a good question:** This is the highest-rapport question on the list. You were a user of the exact products he built \u2014 that's a genuine peer connection, not a manufactured one. It demonstrates technical credibility, gathers real product intelligence, and positions the conversation as a dialogue between two practitioners rather than an interview.\n\n---\n\n**Question 20**\n\n> **\"We both have roots in distributed systems work \u2014 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 \u2014 and how does that inform what you're building at Pantomath?\"**\n\n**Why this is a good question:** Establishes a shared technical history and invites a substantive engineering conversation that positions you as a peer. It also surfaces his architectural philosophy for connectors \u2014 which is exactly the philosophy you'll be working within if you take this role.\n\n---\n\n## 3. Best Conversation Starters\n\nUse one of these to open the conversation naturally before moving into questions.\n\n### On the Cask/CDAP Story\n\n> \"I was reading about Cloud Data Fusion and the Cask CDAP acquisition \u2014 it's a fascinating story of an open-source 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.\"\n\n---\n\n### On the Databricks Chapter\n\n> \"I noticed you were on the Spark Declarative Pipelines team at Databricks before joining Pantomath \u2014 that's a product I've been watching closely given how it's reshaping pipeline authoring. What pulled you from Databricks to Pantomath? It sounds like the opportunity here was compelling.\"\n\n---\n\n### On the Longitudinal View of the Data Stack\n\n> \"Your background spans the full arc of the modern data stack \u2014 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.\"\n\n---\n\n## 4. Topics to Handle Carefully\n\n### The Short Databricks Tenure\n\nSreevatsan spent approximately nine months at Databricks (April\u2013December 2025) before joining Pantomath in February 2026. **Do not** ask anything that implies the short stint was involuntary, or frame it as a pattern of instability.\n\n> **Ask this instead:** \"I noticed you were working on Spark Declarative Pipelines at Databricks \u2014 what was that experience like, and how does that work inform how you're thinking about pipeline-native integrations at Pantomath?\"\n\nFocus on the *work*, not the *duration*.\n\n---\n\n### The New VP in a Growth-Stage Company\n\nSreevatsan is seven months into a VP of Engineering role at a growth-stage company. He may still be actively assessing and reshaping the engineering org. Questions that imply the engineering foundation is immature \u2014 or that suggest skepticism about the company's technical credibility \u2014 could land as pressure on a tenure he's still establishing.\n\n> **Ask this instead:** \"As someone who's led engineering at very different scales, what's your approach to building the right foundation here \u2014 especially for something as reliability-sensitive as connectors?\"\n\nUseful softening phrases to keep handy:\n- *\"Even a directional sense would be helpful...\"*\n- *\"I imagine you're still in discovery mode on some of this...\"*\n- *\"From what you've been able to assess so far...\"*\n\n---\n\n### The Competitive Landscape Question\n\nAsking directly whether Databricks or Snowflake will eventually absorb Pantomath's use cases is high-value intelligence \u2014 but it can read as skepticism about a career bet Sreevatsan just made. Frame it as strategic curiosity, not concern.\n\n> **Ask this instead:** \"I find the competitive dynamics in this space genuinely fascinating \u2014 I'm curious how you think about where Pantomath's connectors create durable differentiation as the major platforms keep expanding their native capabilities.\"\n\n---\n\n## 5. Best Questions to Prioritize During the Call\n\nIf time is limited or the conversation moves quickly, these five questions will give you the most signal per minute.\n\n| # | Question | Why It Matters |\n|---|----------|----------------|\n| 1 | **What drew you to Pantomath after Google?** (Q1) | Reveals his personal conviction and what he'll hold the connectors PM accountable to |\n| 2 | **What does success look like at 30/60/90 days?** (Q4) | Sets real expectations and reveals whether there's a structured ramp or a sink-or-swim dynamic |\n| 3 | **What are the one or two most urgent connector problems right now?** (Q6) | Cuts through JD language to the actual burning priorities |\n| 4 | **How mature is the connector architecture today?** (Q8) | Tells you whether this is a scaling problem or a foundational build \u2014 very different roles |\n| 5 | **BigQuery failure modes question** (Q19) | Highest-rapport, highest-credibility question \u2014 establishes you as a peer, not just a candidate |\n\n---\n\n## 6. Suggested Call Flow\n\nA natural sequence for a 45\u201360 minute conversation.\n\n**Opening \u2014 establish rapport (first 5 minutes)**\n\n> \"I was reading about Cloud Data Fusion and the Cask CDAP acquisition \u2014 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.\"\n\n---\n\n**After he shares his background \u2014 go deeper on the Pantomath decision**\n\n> \"What drew you to Pantomath after that experience, and what problem here felt compelling enough to make the move?\"\n\n---\n\n**When discussing the role \u2014 anchor in the real work**\n\n> \"What are the one or two connector problems that are most urgent right now \u2014 the ones where, if this hire solves them in the first six months, you'd consider it a clear success?\"\n\n---\n\n**When discussing the technical environment \u2014 peer-level technical dialogue**\n\n> \"Given your Cloud Data Fusion background, how does Pantomath's current connector architecture compare in terms of maturity \u2014 well-established framework, or more of a greenfield build-out?\"\n\n---\n\n**Near the end \u2014 strategy and fit**\n\n> \"How does the connectors ecosystem serve as a strategic moat for Pantomath, and where do you see it in two to three years?\"\n\n---\n\n**Closing \u2014 leave on a collaborative note**\n\n> \"This has been a genuinely useful conversation \u2014 I came in with a strong interest in the role and I'm leaving with a clearer picture of where the real work is. Is there anything about my background you'd like me to speak to more specifically before we wrap up?\"\n\n---\n\n## 7. Final Recommended Question Set\n\nIf you only have time for four to six questions, use these.\n\n1. **What drew you to Pantomath after your Google tenure, and what problem here felt compelling enough to make the move?**\n2. **What does success look like at 30, 60, and 90 days for this role?**\n3. **What are the one or two connector problems most urgent right now \u2014 the ones that would make this hire a clear success in the first six months?**\n4. **How mature is the connector architecture today \u2014 well-established framework or more of a greenfield build-out?**\n5. **I used BigQuery extensively at Intuit for developer platform telemetry \u2014 what are the most common failure modes you saw enterprises hit when integrating into BigQuery that Pantomath's connectors are specifically designed to prevent?**\n6. **How does the connectors ecosystem serve as a strategic moat for Pantomath over the next two to three years?**\n\n---\n\n## 8. Strong Closing Line\n\n> \"I've spent the last several years at the intersection of developer platform infrastructure and data engineering \u2014 building the SDK and telemetry layer at Intuit, working hands-on with BigQuery and GCP, and leading a cloud migration for Mailchimp's microservices. What excites me about this role is that it asks for exactly that combination: genuine data engineering depth in service of a product strategy. Based on what you've shared today, I think there's a real opportunity to build something durable here \u2014 and I'd love to be part of that.\"\n\n---\n\n## 9. Final Reminder\n\nThis conversation should demonstrate that you are:\n\n- **A practitioner, not just a PM** \u2014 you have built pipelines, worked with production data systems, and used the exact tools this role requires\n- **A peer to engineering leadership** \u2014 your questions should feel like dialogue between two people who have lived inside the modern data stack, not a candidate gathering information\n- **Genuinely curious about the hard problems** \u2014 the best questions show you care about the connector architecture challenges, not just the job title\n- **Strategically aware** \u2014 you understand the competitive landscape and have a point of view on where connectors create durable differentiation\n- **Grounded and specific** \u2014 every question you ask should connect to something real in your background or in his, not generic PM interview questions dressed up in data vocabulary",
  "source_artifact_id": "art_I1foj2FEwkU",
  "source_kind": "candidate_questions",
  "doc_type": "questions_to_ask"
}