← Pantomath / Sr. Product Manager
candidate_questions / art_q0a5sNh0v40
Interviewer
Bo Brunton is Head of Product Strategy at Pantomath, where he has been for 4.5 years — joining as a PM, growing to Director of Product, and recently stepping into his current head role. Before Pantomath, he spent nearly four years at GE Aviation, including roles as Sr. Data and Information Architect and Enterprise BI Program Leader, giving him direct hands-on data and BI experience that mirrors what this role demands. He also co-founded TadPoL, a startup he describes as an 'incredible solution without a problem' that sharpened his thinking. As Head of Product Strategy, Bo likely cares deeply about strategic fit, technical credibility, and whether a candidate can own a domain end-to-end. Shared context with Felix includes enterprise BI work (Bo at GE Aviation, Felix at IBM BI products and Kaiser Permanente), data architecture, and the founder/builder mindset both have demonstrated.
Questions to ask them (20)
| category | question | why |
|---|---|---|
| interviewer_experience | You've been at Pantomath for over four years and grown from PM to Head of Product Strategy — that kind of trajectory at a single company usually means something clicked early. What was it about Pantomath's problem space that made you want to stay and keep building? | Surfaces what genuinely motivates Bo and what he finds compelling about the company's mission — useful for evaluating cultural fit and understanding what 'doing things that matter' looks like in practice at Pantomath. |
| interviewer_experience | Your time at GE Aviation as a Data and Information Architect and then Enterprise BI Program Leader clearly informs how you think about data products. How much does that hands-on data background shape the bar you set when evaluating candidates or reviewing product decisions today? | Acknowledges Bo's technical roots, builds rapport, and signals that Felix also brings a deep technical foundation — framing the conversation as peer-level rather than candidate-to-evaluator. |
| interviewer_experience | You described TadPoL as an 'incredible solution without a problem' — that's a really honest self-assessment. How did that experience of building something technically compelling but without clear market fit shape how you approach product strategy at Pantomath, especially for something like connectors where the temptation to over-build is real? | Shows Felix read the profile carefully, invites genuine reflection, and signals strategic maturity — the connectors space is full of 'build it and they will come' traps. |
| role_team_dynamics | What does success look like at 30, 60, and 90 days for this role — and how much of that is about shipping versus learning the existing connector landscape and customer base? | Classic but essential — helps Felix understand whether Pantomath wants a quick executor or a thoughtful ramp, and calibrates expectations before accepting an offer. |
| role_team_dynamics | The JD mentions owning both strategy and execution for connectors. How is the current connectors team structured — is there a dedicated engineering pod, or does this PM need to influence across shared engineering resources? | Clarifies the real organizational leverage Felix will have. 'Owning' a roadmap with dedicated resources is very different from influencing a shared team. |
| role_team_dynamics | What's the most pressing unsolved problem on the connectors side right now — is it breadth of integrations, reliability of existing ones, or something more architectural like observability and lineage across the connector layer? | Gets to the actual pain the role is hired to solve, which helps Felix assess whether his background is the right fit and signals he's already thinking in the right problem space. |
| role_team_dynamics | How does the connectors PM interact with Go-to-Market and customer-facing teams today — is there a structured process for surfacing integration requests from the field, or is that something this person would help build? | Clarifies whether Felix is inheriting a mature feedback loop or building one, which significantly affects how he'd spend his first 90 days. |
| technical_environment | When you think about the modern data stack integrations Pantomath has already built — Snowflake, dbt, Fivetran, and so on — what's the current architectural approach for connectors? Are they built on a shared abstraction layer, or are they largely bespoke per integration? | Directly relevant to Felix's technical evaluation of the role. A bespoke-per-integration approach signals significant technical debt; a shared abstraction layer signals a more scalable foundation to build on. |
| technical_environment | The JD mentions replicating real-world customer data environments to validate connector behavior. Is there existing infrastructure for that — staging environments, synthetic data pipelines — or is that largely manual today? | Surfaces a concrete technical challenge Felix would own. If it's manual today, that's a significant investment; if infrastructure exists, Felix can focus on coverage and automation. |
| technical_environment | How does Pantomath handle connector observability today — are there standardized metrics around latency, error rates, and data freshness across integrations, or is that still being defined? | The JD explicitly calls out defining success metrics for connectors. Understanding the current state tells Felix how much foundational work versus iteration he'd be doing. |
| culture_working_style | Your summary says your goal is to do things that matter and leave an impact. How does Pantomath's product culture translate that into day-to-day decision-making — when there's tension between shipping fast and doing something right, how does the team typically resolve it? | Anchors the question in Bo's own stated values, and probes for the real operating culture rather than the aspirational one — critical for a PM who will be making reliability vs. velocity trade-offs constantly. |
| culture_working_style | How does the product team handle disagreement with engineering on technical direction — especially in a domain like connectors where the PM needs to have strong technical opinions? Is there a culture of healthy debate, or does one function typically have the final call? | Felix's background means he'll have real technical opinions. Understanding how disagreement is navigated tells him whether his depth will be an asset or a source of friction. |
| culture_working_style | Pantomath is still a growth-stage company. How much of the PM role here is structured process versus figuring things out as you go — and how has that balance shifted as the company has matured? | Helps Felix calibrate whether his experience building 0-to-1 products (Streamio, Fintellect) and scaling platforms (Intuit) is the right fit for where Pantomath is today. |
| growth_development | You moved from PM to Director to Head of Product Strategy in 4.5 years at Pantomath — that's a meaningful growth path. For someone coming in at the Senior PM level on connectors, what does the growth trajectory typically look like, and what's the ceiling? | Directly relevant to Felix's career calculus. Bo's own path is the most credible data point available on what growth at Pantomath actually looks like. |
| growth_development | The connectors domain sits at the intersection of data engineering and product strategy. Is there an expectation that this PM grows deeper into the data platform strategy over time, or is connectors intended to remain a focused, standalone ownership area? | Helps Felix understand whether this is a role with expanding scope or a well-defined lane — both can be right, but the answer shapes how he'd evaluate the opportunity. |
| strategy_vision | Pantomath is positioned around data observability and lineage. As the modern data stack continues to consolidate — with platforms like Databricks and Snowflake absorbing more of the pipeline layer — how does Pantomath think about the long-term strategic moat for its connector ecosystem? | Tests strategic depth and invites Bo to share Pantomath's competitive thinking. Also signals that Felix has thought about the macro landscape, not just the tactical integration work. |
| strategy_vision | What's the biggest bet Pantomath is making on the connectors side over the next 12–18 months — is it breadth across the stack, deeper semantic integration with specific platforms, or something more novel like AI-assisted connector configuration? | Gets to the actual strategic roadmap and helps Felix assess whether his interests and strengths align with where the company is headed. |
| strategy_vision | How does the connectors roadmap feed into Pantomath's broader product strategy — is it primarily a growth lever for expanding the customer base, a retention driver for existing customers, or something more foundational to the core platform? | Clarifies the strategic importance of the role within the company. If connectors are a growth lever, Felix's GTM experience matters; if foundational, his platform engineering background is the priority. |
| shared_context | You spent time as an Enterprise BI Program Leader at GE Aviation, and I spent several years at IBM working on enterprise BI software products — we've both seen how painful it is when integrations break in production BI environments. How much of Pantomath's connector strategy is shaped by that enterprise reliability bar, versus the more agile 'ship fast and iterate' approach common in SaaS? | Builds genuine peer-level rapport by surfacing shared enterprise BI experience, and probes a real tension in the connectors domain — reliability versus velocity — that Felix will need to navigate. |
| shared_context | Given your data architecture background at GE and my experience building platform infrastructure at Intuit — where we were obsessive about developer experience and self-service — I'm curious how Pantomath thinks about the developer experience for data engineers consuming your connectors. Is that a first-class concern today, or more of an aspiration? | Connects both backgrounds naturally, signals Felix's platform-thinking credentials, and probes whether Pantomath's developer experience investment matches the JD's stated aspiration. |
Conversation starters
- I noticed you were at GE Aviation as a Data and Information Architect right before joining Pantomath — I spent years at IBM working on enterprise BI products and then at Kaiser building data platform infrastructure, so I'm curious what the jump from a large industrial enterprise to an early-stage data startup felt like.
- Your TadPoL description — 'incredible solution without a problem' — really resonated with me. I've been building my own products as a founder and that tension between technical elegance and actual market need is something I think about constantly. Would love to hear more about what you took away from that.
- I saw your summary says your only goal is to do things that matter and leave an impact — that framing is actually why the connectors role caught my attention. The integrations layer is where data products either earn trust or lose it, and I think there's a real opportunity to set a new standard there.
⚠ Handle carefully
- Bo recently transitioned from Director of Product to Head of Product Strategy (May 2025) — avoid any questions that could imply the product org was previously under-led or that strategy was lacking before his promotion. Frame questions about strategic direction as forward-looking.
- TadPoL is described candidly as a startup that didn't find product-market fit. While it's worth referencing as a shared founder experience, avoid dwelling on the failure angle — Bo has already processed it publicly and framed it as a learning. Use it to build rapport, not to probe a wound.
- Pantomath is a growth-stage company and the team is likely small. Avoid questions that presuppose large-company structures (dedicated research teams, formal PM ladders, etc.) — frame questions about process and growth in a way that acknowledges and respects the startup context.