← Pantomath / Sr. Product Manager
candidate_questions / art_bcVyGbkTqPU
Interviewer
Aidan Zebertavage is a Senior Product Manager at Pantomath, where he has been since October 2023 — nearly three years. He brings a non-traditional but deeply technical path to product: chemical engineering at P&G and GE, applications engineering in biotech and industrial sensing, a Technical Evangelist role at Losant (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 active hands-on upskilling. As a peer Sr. PM, he will likely probe technical depth on connectors/integrations, cross-functional execution style, and how the candidate navigates ambiguity in a 0→1 environment. Shared context includes IBM (both worked there, different eras), a strong technical-to-PM career pivot narrative, and hands-on engineering backgrounds that evolved into product leadership.
Questions to ask them (20)
| category | question | why |
|---|---|---|
| interviewer_experience | You came into Pantomath from Abre, which was an EdTech platform — pretty different domain from data operations. What was the draw to Pantomath specifically, and what's kept you engaged for nearly three years? | Surfaces what Aidan finds genuinely compelling about the company and product, which is more authentic than a recruiter pitch. Also signals you've studied his background and aren't asking a generic 'tell me about Pantomath' question. |
| interviewer_experience | Your background spans chemical engineering, IoT evangelism, biotech applications, and now data operations PM — 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? | Invites him to reflect on his own superpower, builds rapport, and gives you a window into how technical the PM culture actually is day-to-day. |
| interviewer_experience | 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? | Probes whether the company invests in technical growth or whether Aidan is self-driven — important signal for a technically demanding PM role. |
| role_team_dynamics | For this connectors PM role specifically, what does success look like at 30, 60, and 90 days — and how much of that is discovery and ramp versus owning and shipping? | Clarifies expectations and pace. At a growth-stage company, 'ramp' can mean two weeks or six months, and this role sounds like it needs someone moving fast. |
| role_team_dynamics | The JD mentions replicating real-world customer data environments to validate connector behavior. Is there already infrastructure for that — staging environments, sandbox tenants, test data sets — or is building that part of the charter? | Practical signal about how mature the connectors practice is and whether you'd be building foundational tooling versus iterating on existing systems. |
| role_team_dynamics | 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? | Understanding team topology is critical — owning a roadmap against a dedicated team is very different from coordinating across shared resources. |
| role_team_dynamics | The JD calls out working with GTM on launch readiness and technical enablement. How tight is that loop today — are there established launch playbooks for connectors, or is that still being built out? | Gauges operational maturity and whether the candidate would be inheriting process or creating it. |
| technical_environment | When you're evaluating a new connector to build — say, a new orchestration tool or a warehouse integration — 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? | Reveals how technical decision-making actually works and how much autonomy the PM has versus engineering gatekeeping. |
| technical_environment | The JD mentions observability as a key success metric for connectors — 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? | Directly relevant to the candidate's background in telemetry (Splunk, Intuit ICE) and signals how much foundational work remains. |
| technical_environment | Pantomath sits in the data lineage and observability space — 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? | Tests depth of product architecture knowledge while surfacing a real technical challenge the candidate would likely own. |
| culture_working_style | 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 — is there a formal process, or is it more judgment-driven? | Surfaces how the team balances velocity and quality, which is a real daily tension in connectors work. |
| culture_working_style | When a PM and an engineering lead have a genuine disagreement about technical direction — say, build vs. buy on a connector, or prioritizing a new integration over hardening an existing one — how does that typically get resolved here? | Reveals decision-making culture and whether PMs have real authority or are order-takers. |
| culture_working_style | 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 — heavy Slack/doc culture, or more whiteboard and live working sessions? | Practical working-style fit question, especially relevant if the candidate is remote or has strong preferences. |
| growth_development | You've grown from PM to Sr. PM at Pantomath over roughly three years — 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? | Anchors the question in Aidan's own trajectory, making it feel genuine rather than generic, while gathering real intel on growth ceiling. |
| growth_development | Given how fast the modern data stack is evolving — new orchestration tools, AI-native pipelines, semantic layers — how does Pantomath invest in keeping the PM team current? Is there budget for conferences, training, or dedicated learning time? | Signals the candidate values staying technically sharp, which aligns with the role's requirements, while gathering real info about L&D investment. |
| strategy_vision | The connectors ecosystem in the modern data stack is sprawling — 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? | Gets at strategic direction and reveals whether there's a coherent connectors thesis or reactive customer-driven backlog. |
| strategy_vision | 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? | Demonstrates forward-looking thinking about the space and surfaces how leadership is stress-testing the product strategy against market shifts. |
| strategy_vision | What's the biggest unsolved problem in the connectors domain that this hire is expected to make a dent in within the first year? | Direct, high-signal question that cuts through job description language to understand the actual burning problem — and whether the candidate's background is the right fit for it. |
| shared_context | I saw IBM on both our backgrounds — 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? | Genuine rapport-building moment grounded in a real shared data point. Opens a human conversation that breaks interview formality. |
| shared_context | Your Losant Technical Evangelist role is interesting to me — 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? | Connects the candidate's developer platform background (Intuit SDKs, Splunk SPL) with Aidan's evangelist experience — builds credibility and surfaces shared philosophy on developer experience. |
Conversation starters
- I noticed you came up through applications engineering and technical evangelism before moving into product — 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.
- Your Losant role caught my eye — 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.
- I saw IBM on your profile — 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.
⚠ Handle carefully
- Aidan's domain pivot from EdTech (Abre) to data operations (Pantomath) is significant — avoid implying he lacks deep data domain expertise, as his UC Cincinnati Data Analytics certificate and active technical upskilling suggest he's been deliberate about closing that gap.
- Pantomath appears to be a relatively early-stage company and Aidan has been there nearly three years — avoid questions that could imply instability, slow growth, or limited career ceiling, as he's clearly committed and may be sensitive to framing that questions the company's trajectory.
- Aidan's non-traditional path (chemical engineering → biotech → IoT → PM) is a strength, but avoid over-romanticizing it in a way that feels like you're projecting your own narrative onto his — let him characterize it on his own terms.