interview_prep_doc / art_o4BUsTv-Zgw

Content

{
  "markdown": "# Pantomath Interview Prep\n## Questions to Ask Aidan Zebertavage\n\n---\n\n## 1. Interviewer Summary\n\nAidan Zebertavage is a Senior Product Manager at Pantomath, where he has been since October 2023 \u2014 nearly three years. His path to product is anything but conventional: chemical engineering roles at P&G and GE, applications engineering in biotech and industrial sensing, a Technical Evangelist position at Losant (an IoT platform), and PM roles at Abre (EdTech) before landing at Pantomath. He holds an MBA and a Graduate Certificate in Data Analytics from UC Cincinnati, plus a full-stack engineering bootcamp credential. His LinkedIn certifications in Python, CLI, and AI signal someone who actively upskills on the technical side \u2014 by choice, not obligation.\n\nAs a **peer Sr. PM**, Aidan is not a hiring manager evaluating you from above. He is more likely assessing whether you'd be a strong collaborator and technical peer \u2014 someone he'd want in the room when debating connector architecture trade-offs or writing a meaty PRD. Expect him to probe your **technical depth on integrations and data pipelines**, your **cross-functional execution style**, and how you navigate ambiguity in a 0\u21921 environment.\n\nThere is meaningful shared context here worth using naturally:\n\n- **IBM** appears on both your backgrounds \u2014 you in BI software engineering (mid-2000s), Aidan as an intern, different eras and divisions\n- Both of you took a **hands-on engineering path into product leadership** \u2014 a genuine common thread\n- Your **developer SDK and platform work at Intuit** maps well to his **Technical Evangelist experience at Losant** \u2014 both sit at the intersection of technical depth and developer communication\n\nThis conversation will likely feel more collegial than evaluative. Thoughtful questions that invite Aidan to reflect on his own experience \u2014 rather than generic \"tell me about the company\" questions \u2014 will build the most authentic rapport and still surface the signal you need.\n\n---\n\n## 2. Best Questions to Ask Aidan\n\n---\n\n### A. Interviewer Experience and Rapport\n\n**Question 1.**\n> **\"You came into Pantomath from Abre, which was an EdTech platform \u2014 pretty different domain from data operations. What was the draw to Pantomath specifically, and what's kept you engaged for nearly three years?\"**\n\n**Why this is a good question:** This surfaces what Aidan finds genuinely compelling about the company and product \u2014 far more authentic than a recruiter pitch. It also signals that you've studied his background and aren't asking a generic \"tell me about Pantomath\" opener.\n\n---\n\n**Question 2.**\n> **\"Your background spans chemical engineering, IoT evangelism, biotech applications, and now data operations PM \u2014 that's a pretty rare combination. How has that technical breadth shaped the way you approach product decisions at Pantomath, especially when you're deep in connector architecture trade-offs?\"**\n\n**Why this is a good question:** This invites Aidan to reflect on his own superpower, which builds genuine rapport. It also gives you a real window into how technical the PM culture is day-to-day \u2014 not the version in the job description, but the version a peer lives.\n\n---\n\n**Question 3.**\n> **\"I noticed you completed the Firehose full-stack bootcamp and have been actively picking up Python and CLI skills alongside your PM work. Is that kind of continuous technical upskilling something you do independently, or is it something the team culture at Pantomath actively encourages?\"**\n\n**Why this is a good question:** This probes whether the company invests in technical growth or whether Aidan is self-driven \u2014 an important signal for a role that explicitly requires staying current on a fast-moving data stack. It also opens a natural conversation about learning culture without asking a blunt \"do you have a training budget\" question.\n\n> *Softened framing if you want to make it feel less like an audit:* \"I ask because I've been deliberate about staying hands-on \u2014 building out RL workbenches, doing my own evals work \u2014 and I'm curious whether that kind of thing is something people do on their own or whether there's a culture around it here.\"\n\n---\n\n### B. Role and Team Dynamics\n\n**Question 4.**\n> **\"For this connectors PM role specifically, what does success look like at 30, 60, and 90 days \u2014 and how much of that is discovery and ramp versus owning and shipping?\"**\n\n**Why this is a good question:** At a growth-stage company, \"ramp time\" can mean two weeks or six months. This role sounds like it needs someone moving fast, and the answer will tell you whether Pantomath has thought through the onboarding arc or expects you to hit the ground running from day one.\n\n---\n\n**Question 5.**\n> **\"The JD mentions replicating real-world customer data environments to validate connector behavior. Is there already infrastructure for that \u2014 staging environments, sandbox tenants, test data sets \u2014 or is building that part of the charter?\"**\n\n**Why this is a good question:** This is a practical, technically grounded question that signals you've read the JD carefully and thought about what the work actually involves. The answer reveals how mature the connectors practice is and whether you'd be iterating on existing systems or building foundational tooling from scratch.\n\n---\n\n**Question 6.**\n> **\"How is the connectors team structured relative to the broader engineering org? Is there a dedicated connectors engineering squad, or does this PM role coordinate across shared platform teams?\"**\n\n**Why this is a good question:** Team topology matters enormously. Owning a roadmap against a dedicated engineering squad is a fundamentally different job than coordinating across shared platform resources \u2014 and the answer shapes how you'd need to operate from day one.\n\n---\n\n**Question 7.**\n> **\"The JD calls out working with GTM on launch readiness and technical enablement. How tight is that loop today \u2014 are there established launch playbooks for connectors, or is that still being built out?\"**\n\n**Why this is a good question:** This gauges operational maturity and whether you'd be inheriting process or creating it. Given your experience building developer documentation and SDK enablement at Intuit, this is a space where you can add immediate value \u2014 and knowing the current state helps you frame that.\n\n---\n\n### C. Technical Environment\n\n**Question 8.**\n> **\"When you're evaluating a new connector to build \u2014 say, a new orchestration tool or a warehouse integration \u2014 what does the technical feasibility process look like today? Is there a formal architecture review, or is it more of a PM-engineering whiteboard conversation?\"**\n\n**Why this is a good question:** This reveals how technical decision-making actually works at Pantomath and how much autonomy the PM has versus engineering gatekeeping. It also invites Aidan to describe a real process rather than a hypothetical one.\n\n---\n\n**Question 9.**\n> **\"The JD mentions observability as a key success metric \u2014 adoption, reliability, latency, error rates. What's the current instrumentation story? Are connectors emitting structured telemetry today, or is building that observability layer part of what this role needs to drive?\"**\n\n**Why this is a good question:** This is directly relevant to your background in telemetry and observability at Splunk and Intuit (ICE platform, BigQuery usage analysis). The answer signals how much foundational work remains and whether your specific experience maps to an immediate need.\n\n---\n\n**Question 10.**\n> **\"Pantomath sits in the data lineage and observability space \u2014 how does the connectors layer interact with the core lineage graph? Is connector metadata feeding lineage automatically, or is that integration still a work in progress?\"**\n\n**Why this is a good question:** This tests depth of product architecture knowledge while surfacing a real technical challenge the candidate would likely own. It also demonstrates that you've thought about Pantomath's product holistically, not just the connectors slice in isolation.\n\n---\n\n### D. Culture and Working Style\n\n**Question 11.**\n> **\"Pantomath sounds like it's still in a high-growth, relatively early stage. How does the team handle the tension between moving fast on new connectors versus maintaining reliability on existing ones \u2014 is there a formal process, or is it more judgment-driven?\"**\n\n**Why this is a good question:** This is a real daily tension in connectors work \u2014 and the answer tells you a lot about how the team operates under pressure. It also signals that you understand the operational reality of owning a connectors ecosystem, not just building new ones.\n\n---\n\n**Question 12.**\n> **\"When a PM and an engineering lead have a genuine disagreement about technical direction \u2014 say, build vs. buy on a connector, or prioritizing a new integration over hardening an existing one \u2014 how does that typically get resolved here?\"**\n\n**Why this is a good question:** This reveals whether PMs have real authority and voice in technical decisions or whether they're primarily order-takers. Given the JD's emphasis on making \"informed, technical decisions,\" the answer matters for how you'd actually operate in the role.\n\n---\n\n**Question 13.**\n> **\"How much of your work as a Sr. PM at Pantomath is async versus synchronous collaboration? I'm trying to get a feel for the day-to-day rhythm \u2014 heavy Slack and doc culture, or more whiteboard and live working sessions?\"**\n\n**Why this is a good question:** A practical working-style fit question that surfaces real information about how the team operates \u2014 especially relevant given your background spanning remote-first environments and in-person technical collaboration.\n\n---\n\n### E. Growth and Development\n\n**Question 14.**\n> **\"You've grown at Pantomath over roughly three years \u2014 what's driven that progression, and are there clear paths for Sr. PMs to grow into principal or director-level roles as the company scales?\"**\n\n**Why this is a good question:** Anchoring this in Aidan's own trajectory makes it feel genuine rather than a generic career-ceiling question. It also gathers real intel about whether there's a defined growth path or whether advancement is informal and dependent on company growth.\n\n---\n\n**Question 15.**\n> **\"Given how fast the modern data stack is evolving \u2014 new orchestration tools, AI-native pipelines, semantic layers \u2014 how does Pantomath invest in keeping the PM team current? Is there budget for conferences, training, or dedicated learning time?\"**\n\n**Why this is a good question:** This signals that you value staying technically sharp \u2014 which aligns directly with the role's requirements \u2014 while gathering real information about L&D investment. Given your own track record of continuous technical upskilling (NeurIPS, RL workbenches, teaching at De Anza), this question is authentic coming from you.\n\n---\n\n### F. Strategy and Vision\n\n**Question 16.**\n> **\"The connectors ecosystem in the modern data stack is sprawling \u2014 hundreds of potential integrations. What's Pantomath's current philosophy on prioritization: depth on a curated set of tier-1 integrations, or breadth to cover the long tail?\"**\n\n**Why this is a good question:** Gets at strategic direction and reveals whether there's a coherent connectors thesis or a reactive, customer-driven backlog. The answer will tell you a lot about how much strategic latitude the connectors PM actually has.\n\n---\n\n**Question 17.**\n> **\"With AI-native data tools starting to blur the lines between ingestion, transformation, and observability, how is Pantomath thinking about where connectors fit in a world where some of these pipeline steps might get abstracted away?\"**\n\n**Why this is a good question:** This demonstrates forward-looking thinking about the space and surfaces how leadership is stress-testing the product strategy against real market shifts. It's the kind of question a technically credible PM asks \u2014 not a generalist.\n\n---\n\n**Question 18.**\n> **\"What's the biggest unsolved problem in the connectors domain that this hire is expected to make a dent in within the first year?\"**\n\n**Why this is a good question:** Direct and high-signal. This cuts through job description language to understand the actual burning problem \u2014 and whether your background is the right fit for it. It also signals that you're outcome-oriented, not just process-oriented.\n\n---\n\n### G. Shared Context\n\n**Question 19.**\n> **\"I saw IBM on both our backgrounds \u2014 you interned there and I spent several years there in BI software engineering. Different eras and very different parts of the company, but I'm curious: did that experience shape how you think about enterprise-scale technical products at all, or was it more of a stepping stone?\"**\n\n**Why this is a good question:** A genuine rapport-building moment grounded in a real shared data point. Opens a human conversation that breaks interview formality without feeling forced. Let him characterize the experience on his own terms.\n\n---\n\n**Question 20.**\n> **\"Your Losant Technical Evangelist role is interesting to me \u2014 I've done a fair amount of developer-facing work and SDK tooling, and that role sits right at the intersection of technical depth and communication. Did that experience influence how you write PRDs or engage with engineering at Pantomath?\"**\n\n**Why this is a good question:** Connects your developer platform background (Intuit SDKs, Splunk SPL) with Aidan's evangelist experience \u2014 builds credibility and surfaces shared philosophy on developer experience. It's a peer-to-peer question, not a candidate-to-interviewer one.\n\n---\n\n## 3. Best Conversation Starters\n\nUse one of these in the first 60\u201390 seconds to set a collegial, peer tone.\n\n### Option 1 \u2014 The Technical-to-PM Path\n> \"I noticed you came up through applications engineering and technical evangelism before moving into product \u2014 I took a similar path through software engineering and platform infrastructure before landing in PM. I'm curious how you think about that technical foundation showing up in your day-to-day product work at Pantomath.\"\n\n### Option 2 \u2014 Developer Experience Overlap\n> \"Your Losant role caught my eye \u2014 building technical education materials for an IoT platform is a pretty unique way to develop product instincts. I spent time building developer SDKs and documentation at Intuit, so I feel like we might have a similar appreciation for the developer experience side of things.\"\n\n### Option 3 \u2014 IBM Callback\n> \"I saw IBM on your profile \u2014 I was there in the BI software engineering group back in the mid-2000s. Very different era and part of the company, but always interesting to find that overlap.\"\n\n---\n\n## 4. Topics to Handle Carefully\n\n### Aidan's Domain Pivot from EdTech to Data Operations\n**The risk:** Implying \u2014 even accidentally \u2014 that he lacks deep data domain expertise because his most recent pre-Pantomath role was in EdTech.\n\n**The reality:** His UC Cincinnati Data Analytics certificate, active Python/CLI upskilling, and nearly three years at Pantomath suggest he's been deliberate about closing any domain gap. He likely doesn't see it as a gap at all.\n\n**Ask this instead of anything that implies a knowledge deficit:**\n> \"You've clearly been deliberate about building your data domain depth \u2014 the analytics certificate, the technical upskilling. Has that background in adjacent domains actually given you a different lens on data problems than someone who came up purely through data engineering?\"\n\n---\n\n### Pantomath's Stage and Career Ceiling\n**The risk:** Questions that imply instability, slow growth, or a limited career ceiling \u2014 Aidan has been there nearly three years and is clearly committed. Framing that questions the company's trajectory could land as dismissive of a choice he's proud of.\n\n**Ask this instead:**\n> \"You've been at Pantomath for nearly three years \u2014 that's meaningful tenure at a growth-stage company. What's made it worth staying and building here versus moving to a larger platform?\"\n\n---\n\n### Over-Romanticizing His Non-Traditional Path\n**The risk:** Projecting your own career narrative onto his in a way that feels like you're making his story about you. His path from chemical engineering to IoT to PM is genuinely interesting \u2014 let him own the framing.\n\n**Softening phrasings to reuse:**\n- *\"I'm curious how you'd characterize that...\"*\n- *\"I don't want to put words to it \u2014 how do you think about that arc?\"*\n- *\"What's your read on how that shaped you?\"*\n\n---\n\n## 5. Best Questions to Prioritize During the Call\n\nIf the conversation moves fast and you only get five questions in, make them these:\n\n1. **Question 18 \u2014 The biggest unsolved problem.** *\"What's the biggest unsolved problem in the connectors domain that this hire is expected to make a dent in within the first year?\"* \u2014 Cuts through JD language to the real job.\n\n2. **Question 4 \u2014 30/60/90-day success.** *\"What does success look like at 30, 60, and 90 days \u2014 and how much is discovery versus owning and shipping?\"* \u2014 Sets expectations and reveals pace.\n\n3. **Question 6 \u2014 Team topology.** *\"Is there a dedicated connectors engineering squad, or does this PM coordinate across shared platform teams?\"* \u2014 Shapes everything about how you'd operate.\n\n4. **Question 9 \u2014 Observability instrumentation.** *\"Are connectors emitting structured telemetry today, or is building that observability layer part of the charter?\"* \u2014 Directly maps to your Splunk and Intuit telemetry background; reveals scope.\n\n5. **Question 12 \u2014 PM authority in technical disagreements.** *\"When a PM and an engineering lead have a genuine disagreement about technical direction, how does that typically get resolved here?\"* \u2014 Reveals whether PMs have real voice or are order-takers.\n\n---\n\n## 6. Suggested Call Flow\n\nUse this as a loose guide \u2014 adapt to how the conversation naturally moves.\n\n### Opening (first 2\u20133 minutes) \u2014 Establish Peer Rapport\nStart with a conversation starter, not a question. Let the first exchange be human.\n\n> \"I noticed you came up through applications engineering before moving into product \u2014 I took a similar path through software engineering at IBM and Kaiser before landing in PM. I'm curious how you think about that technical foundation showing up in your day-to-day work at Pantomath.\"\n\n---\n\n### After He's Described His Background \u2014 Deepen the Technical Thread\nThis is the natural moment for Questions 2 or 20.\n\n> \"Your Losant Technical Evangelist role is interesting to me \u2014 I've done a fair amount of developer-facing SDK work, and that role sits right at the intersection of technical depth and communication. Did that experience influence how you write PRDs or engage with engineering at Pantomath?\"\n\n---\n\n### When Discussing the Role \u2014 Go Practical and Specific\nShift to Questions 4, 5, 6, and 9 here. These signal you've read the JD carefully and are thinking about the actual work.\n\n> \"The JD mentions replicating real-world customer data environments to validate connector behavior \u2014 is there already infrastructure for that, or is building it part of the charter?\"\n\n---\n\n### Near the End \u2014 Strategy and Vision\nQuestions 16, 17, and 18 land best once rapport is established and the conversation has warmed up.\n\n> \"What's the biggest unsolved problem in the connectors domain that this hire is expected to make a dent in within the first year?\"\n\n---\n\n### Closing \u2014 Leave on a Forward-Looking Note\n> \"This has been a genuinely useful conversation \u2014 I appreciate the candor. I'll be honest: the combination of the technical depth this role requires and the stage Pantomath is at is exactly the kind of environment I've been looking for. Is there anything about my background you'd want me to dig into further before we wrap up?\"\n\n---\n\n## 7. Final Recommended Question Set\n\nIf time is short and you need to pick four to six questions, use these:\n\n1. What's the biggest unsolved problem in the connectors domain that this hire is expected to make a dent in within the first year?\n2. What does success look like at 30, 60, and 90 days \u2014 and how much of that is discovery versus owning and shipping?\n3. Is there a dedicated connectors engineering squad, or does this PM coordinate across shared platform teams?\n4. Are connectors emitting structured telemetry today, or is building that observability layer part of the charter?\n5. When a PM and an engineering lead have a genuine disagreement about technical direction, how does that typically get resolved here?\n6. What's Pantomath's current philosophy on connector prioritization \u2014 depth on tier-1 integrations, or breadth to cover the long tail?\n\n---\n\n## 8. Strong Closing Line\n\n> \"I've spent the last several years building developer-facing platforms and telemetry infrastructure at scale \u2014 and what draws me to this role is that it's one of the few PM seats where that technical depth is the job, not just a nice-to-have. Based on what you've shared today, I think there's a real fit here, and I'm genuinely excited about what this team is building.\"\n\n---\n\n## 9. Final Reminder\n\nThis conversation should demonstrate:\n\n- **Technical peer credibility** \u2014 you've built pipelines, owned telemetry, shipped developer SDKs; you're not a generalist asking surface-level questions\n- **Genuine curiosity about Aidan's experience** \u2014 not just the company, but how he specifically navigates the role\n- **Strategic thinking about the connectors space** \u2014 you've thought about prioritization, observability, and where AI is reshaping the data stack\n- **Self-awareness about what you bring** \u2014 your Splunk, Intuit, and IBM background maps directly to what this role needs; let that come through naturally\n- **Collegial tone** \u2014 this is a peer conversation, not a panel interview; match his energy and let it feel like two technical PMs talking shop",
  "source_artifact_id": "art_bcVyGbkTqPU",
  "source_kind": "candidate_questions",
  "doc_type": "questions_to_ask"
}