← Pantomath / Sr. Product Manager
candidate_questions / art_fgWwfBolIu0
Interviewer
Aidan Zebertavage is a Senior Product Manager at Pantomath, where he has been for nearly three years since October 2023. He brings a distinctive background that blends chemical engineering (Clarkson BS, P&G, VEGA, Eccrine Systems), IoT technical evangelism (Losant), EdTech PM work (Abre), and product marketing (Benchmark Gensuite) — all underpinned by an MBA and a Graduate Certificate in Data Analytics from the University of Cincinnati, plus a Firehose full-stack bootcamp. His LinkedIn certifications in Python and command-line tools signal self-directed technical upskilling. As a peer Sr. PM at Pantomath, he will likely probe cross-functional execution, GTM readiness, and how the candidate navigates ambiguity in a data-ops context. Shared context with the candidate includes IBM (both worked there at different times), a strong self-taught technical ethos, and experience bridging deep technical work with product and go-to-market functions.
Questions to ask them (20)
| category | question | why |
|---|---|---|
| interviewer_experience | You've been at Pantomath for nearly three years — which is meaningful tenure for an early-stage data company. What's kept you engaged, and how has the product scope of your role evolved since you joined in late 2023? | Surfaces what's genuinely compelling about the company from someone with skin in the game, and reveals how PM scope and ownership have grown — a proxy for how this new role might evolve. |
| interviewer_experience | Your path to PM is pretty non-linear — chemical engineering, applications engineering at Eccrine, IoT evangelism at Losant, then into product. How has that technical breadth shaped the way you approach product decisions at Pantomath, especially in a data-ops context? | Builds genuine rapport by acknowledging his unique journey, and surfaces how Pantomath values technical depth versus traditional PM backgrounds — directly relevant to how this connectors role will be evaluated. |
| interviewer_experience | You picked up Python, command-line, and full-stack web development through self-directed programs like Firehose and Codecademy alongside your day job. Is that kind of continuous self-directed technical learning something you see across the PM team at Pantomath, or is it more of a personal thing? | Signals the candidate's own commitment to continuous learning while probing whether the culture rewards technical curiosity — important for a role requiring hands-on data engineering depth. |
| role_team_dynamics | For the connectors PM role specifically, what does a strong 30-60-90 look like? Is the expectation to come in and immediately start shipping, or is there a deliberate ramp period to understand the existing connector architecture and customer landscape first? | Sets realistic expectations and reveals whether the company has a structured onboarding process or expects the candidate to self-direct from day one — critical for a technical PM role. |
| role_team_dynamics | How is the connectors team structured today — is this PM role paired with a dedicated engineering squad, or does it operate more as a shared-services model where you're competing for engineering bandwidth across the broader roadmap? | Directly assesses execution leverage and whether the PM will have real ownership or be navigating a resource-constrained matrix — a make-or-break factor for roadmap delivery. |
| role_team_dynamics | The JD mentions replicating real-world customer data environments to validate connector behavior. Is that infrastructure already in place, or is building that test harness part of what this role needs to establish? | Distinguishes between a role that inherits a mature foundation versus one that requires significant groundwork — important for scoping the actual work and setting expectations. |
| role_team_dynamics | What's the biggest unsolved challenge on the connectors roadmap right now — the one that whoever takes this role will need to make meaningful progress on in the first six months? | Gets past polished job description language to understand the real problem the company is hiring to solve, and tests whether the interviewer will be candid about current gaps. |
| technical_environment | The JD calls out Fivetran, dbt, Airflow, Snowflake, Databricks, Tableau, and Power BI as the core ecosystem. Where is Pantomath's connector coverage today — which of those integrations are production-grade and which are still early or on the roadmap? | Surfaces the actual state of the product versus the aspirational list in the JD, and helps the candidate understand where they'd be building versus maintaining. |
| technical_environment | How does Pantomath approach connector observability today — are there standardized metrics for latency, error rates, and adoption across all connectors, or is that instrumentation still being built out? | The JD explicitly calls out defining success metrics for connectors; understanding the current telemetry maturity reveals how much foundational work remains versus iterative improvement. |
| technical_environment | When engineering and product disagree on a technical trade-off — say, build speed versus long-term maintainability of a connector — how does Pantomath typically resolve that tension? Is there a clear decision-making framework or does it depend on the individuals involved? | Reveals the actual decision-making culture and whether the PM role has real technical authority or is primarily a facilitator — directly relevant to the 'make informed trade-offs' requirement. |
| culture_working_style | Pantomath seems to be a relatively lean team. How does the company balance moving fast on new connectors versus maintaining the reliability and observability standards for existing ones — and where does that tension show up most in practice? | Probes the real operational culture around quality versus velocity, and whether the PM will be expected to hold the line on reliability or constantly trade it off for new features. |
| culture_working_style | The JD emphasizes cross-functional leadership — working with GTM, engineering, and customers simultaneously. How autonomous is the PM role at Pantomath in practice? Is there a strong product culture where PMs set direction, or does leadership stay closely involved in roadmap calls? | Assesses the actual autonomy and influence the role carries, which is critical for a senior IC PM evaluating whether they'll have real ownership. |
| culture_working_style | Given your background spans technical evangelism, applications engineering, and product — how does Pantomath's team generally handle situations where a PM pushes back on an engineering estimate or challenges a technical approach? Is that kind of friction welcomed or does it create tension? | Anchors the question in Aidan's own technical credibility to make it feel peer-to-peer, while surfacing whether the culture genuinely supports technically-informed PM pushback. |
| growth_development | Looking at your own trajectory — from applications engineering and technical evangelism into PM — Pantomath seems like a place where technical depth is genuinely valued in product. For someone coming in as Sr. PM for Connectors, what's the realistic growth path from here — toward principal PM, a director track, or something else? | Anchors the growth question in Aidan's own visible career progression to make it feel natural, while gathering real information about the career ceiling in this role. |
| growth_development | Does Pantomath invest in PM development — things like conference budgets, access to industry events, or structured mentorship — or is professional growth more self-directed here? | Practical signal about the company's investment in talent development, which matters for a senior candidate evaluating long-term fit. |
| strategy_vision | Data observability and lineage are called out as preferred experience in the JD. Is Pantomath positioning connectors as purely a data movement layer, or is there a longer-term vision to embed observability and lineage natively into the connector experience itself? | Tests strategic alignment and surfaces whether the connectors roadmap is tactical plumbing or part of a larger platform differentiation story — important for understanding the scope of the role's impact. |
| strategy_vision | The modern data stack is consolidating fast — Databricks acquiring Tabular, Snowflake expanding into pipelines, dbt moving up the stack. How is Pantomath thinking about connector strategy in a world where the platforms themselves are eating the integration layer? | Demonstrates genuine market awareness and surfaces how leadership is thinking about competitive moats — a signal of strategic maturity in the company's product thinking. |
| strategy_vision | What's the one bet Pantomath is making on the connectors side in the next 12 months that you're most excited about — and what would have to be true for it to pay off? | Invites Aidan to speak candidly about forward-looking strategy and reveals both his own conviction in the roadmap and the company's actual strategic priorities. |
| shared_context | We both have IBM on our resumes — you on the production side, me in BI software engineering. IBM in that era was a very different kind of technical environment than a modern data startup like Pantomath. How do you find the pace and technical culture here compares to the more structured environments earlier in your career? | Builds genuine peer rapport through a specific shared reference point, while gathering useful signal about the cultural contrast between Pantomath and larger enterprise environments. |
| shared_context | Your Losant role was all about making IoT APIs and developer tooling approachable through education and documentation — and this connectors role has a similar 'developer experience' thread running through it. Do you find that Pantomath's customers are primarily data engineers who want low-level control, or are there more business-user personas who need the connectors to just work without configuration overhead? | Leverages Aidan's directly relevant Losant experience to open a substantive conversation about the actual user persona split — critical for understanding the product design philosophy the candidate will need to adopt. |
Conversation starters
- I noticed you went through the Firehose full-stack bootcamp and picked up Python and command-line through Codecademy on top of your engineering background — I've done a similar thing building out projects in TypeScript, Go, and PyTorch outside of my day job. It sounds like we both came up through the 'learn by building' school. Did the Firehose program change how you think about product requirements when you're working with engineering teams?
- Your Eccrine Systems work on sweat-based pharmaceutical monitoring is genuinely fascinating — I saw the publications on your profile. Going from biosensor applications engineering to data ops PM is a pretty remarkable pivot. I'd love to hear how you made that transition and what surprised you most about the PM role when you first stepped into it.
- We both have IBM on our resumes — different eras and functions, but I'm curious what you took away from that experience that still shows up in how you work today.
⚠ Handle carefully
- Aidan joined Pantomath in October 2023 — avoid any framing that implies the company has retention issues or that his tenure is unusually short. He's been there nearly three years, which is solid for a startup-stage data company.
- His path to PM is non-traditional (no CS degree, no classic PM pedigree) and he has clearly worked hard to build technical credibility through self-directed learning. Avoid any framing that could read as questioning whether he's 'technical enough' — instead, lean into genuine curiosity about his unique background.
- Pantomath appears to be a relatively early-stage or growth-stage company with limited public profile. Avoid pressing too hard on headcount, funding, or runway in ways that could feel like due diligence interrogation — save those questions for a recruiter or hiring manager conversation.