← Pantomath / Sr. Product Manager
candidate_questions / art_zxfnPDbUpjA
Interviewer
Chuck Mobley is Pantomath's Chief Architect, a role he stepped into in April 2025 after nearly eight years at VNDLY (acquired by Workday for $510M), where he rose from founding Senior Software Engineer to CTO. His most directly relevant achievement is building a 20-integration Workday Connector from concept to production — exactly the connectors domain this role owns. His background spans enterprise API strategy, ISV partner ecosystems, high-scale retail systems at Kroger, and consulting, giving him a broad architecture lens. As Chief Architect he will likely probe technical depth, integration design philosophy, and how Felix thinks about connector reliability and scalability. Shared context includes enterprise API/integration work, developer-facing platform thinking, and experience operating at the intersection of product and engineering.
Questions to ask them (20)
| category | question | why |
|---|---|---|
| interviewer_experience | You built Pantomath's connectors product from the ground up — what was the single hardest architectural decision you made early on that you'd want the person in this role to understand deeply before touching the roadmap? | Surfaces institutional knowledge Chuck holds as Chief Architect and signals that Felix respects the existing foundation rather than arriving with a blank-slate mentality. |
| interviewer_experience | At VNDLY you went from founding engineer to CTO and then navigated a $510M Workday acquisition — how did that experience of building an integration ecosystem under M&A scrutiny shape how you think about connector reliability and security standards here at Pantomath? | Connects directly to Chuck's most formative career moment and invites him to share hard-won lessons about production-grade integrations that will inform how Felix should prioritize. |
| interviewer_experience | You've operated in both startup and large-enterprise environments — Kroger at massive scale, VNDLY as a founding engineer, and now Pantomath. What's the biggest mindset shift you've had to make coming back to a startup-stage company after the Workday years? | Helps Felix understand the cultural operating mode Chuck expects and whether the team is in 'move fast' or 'enterprise-grade rigor' mode — or balancing both. |
| role_team_dynamics | What does success look like for this role at 30, 60, and 90 days — and is there a specific connector or integration problem you'd want me to sink my teeth into first? | Classic but grounded here — Chuck's hands-on architecture background means he likely has a concrete first project in mind, and knowing it helps Felix assess fit and prepare. |
| role_team_dynamics | How is the connectors team structured today — are there dedicated engineers, or does this PM role pull from a shared engineering pool — and how does that team interface with Chuck's architecture function? | Chuck is Chief Architect, so understanding the reporting and collaboration lines between product and architecture is critical to knowing where decision authority lives. |
| role_team_dynamics | What are the two or three connector gaps that customers or prospects are most loudly asking for right now, and what's been blocking them from getting prioritized? | Reveals the immediate backlog pressure and whether blockers are technical, resource, or strategic — giving Felix a realistic picture of the challenge ahead. |
| role_team_dynamics | How does the connectors PM role interact with Go-to-Market and customer success — is there a defined handoff process for launch readiness, or is that something this role would help build? | The JD calls out GTM partnership explicitly; understanding the current maturity of that process tells Felix how much process-building versus execution is expected. |
| technical_environment | When you built the 20-integration Workday Connector at VNDLY, what patterns or abstractions did you establish that you're carrying forward into Pantomath's connector architecture — and where are you deliberately doing things differently? | Directly leverages Chuck's most relevant prior work to understand the technical DNA of the current connector platform and where it's still evolving. |
| technical_environment | How does Pantomath currently handle connector observability — things like error rate tracking, latency monitoring, and alerting on data freshness — and is that an area where you see significant investment needed? | The JD lists observability as a key success metric dimension; understanding the current state tells Felix whether this is a build-from-scratch problem or an optimization problem. |
| technical_environment | Across the modern data stack integrations in scope — Fivetran, dbt, Airflow, Snowflake, Databricks — are there specific API or authentication patterns that have proven particularly painful to maintain at scale, and how is the team approaching those? | Shows Felix's hands-on familiarity with the specific stack and invites Chuck to share real technical pain points that would shape the roadmap. |
| culture_working_style | When there's a disagreement between the PM's product direction and your architectural vision, how does that typically get resolved — and can you give me an example of how that's played out on the team? | Chuck is Chief Architect with deep technical conviction; understanding the real decision-making dynamic between product and architecture is essential before joining. |
| culture_working_style | How much autonomy does the connectors PM have to set roadmap priorities versus needing alignment from engineering leadership or the executive team — and how has that balance evolved as Pantomath has grown? | Helps Felix calibrate whether this is a true ownership role or a coordination role, and whether the autonomy described in the JD matches day-to-day reality. |
| culture_working_style | Pantomath is described as automating data operations — what does the team's day-to-day working rhythm look like: sprint cadences, architecture reviews, how decisions get documented and communicated? | Chuck's background suggests he values structured technical decision-making; understanding the rhythm helps Felix assess whether his working style is a match. |
| growth_development | You've grown from engineer to CTO to Chief Architect across your career — for someone coming into this Senior PM role with a strong technical background, what's the growth path you'd envision, and are there opportunities to move into broader platform or architecture influence over time? | Signals long-term ambition without overreaching, and invites Chuck to share how he thinks about developing technical PMs — relevant given his own trajectory. |
| growth_development | Is there an expectation that the connectors PM will develop deeper expertise in specific parts of the data stack over time, or is breadth across the full integration ecosystem the priority? | Helps Felix understand whether to double down on depth in specific tools or maintain broad coverage — important for planning his own learning roadmap. |
| strategy_vision | Where does Pantomath's connector ecosystem need to be in 18-24 months to support the company's broader data operations automation vision — and what's the biggest strategic bet you're making to get there? | Connects the connectors role to Pantomath's stated mission of automating data operations and helps Felix understand the strategic stakes of the role. |
| strategy_vision | As data observability and lineage platforms become more prominent — companies like Monte Carlo, Atlan, and others — how does Pantomath think about positioning its connector ecosystem relative to those players: complementary, competitive, or something else? | Shows Felix's awareness of the competitive landscape and invites Chuck to share strategic positioning thinking that would directly inform roadmap decisions. |
| strategy_vision | Are there plans to open up a developer or partner ecosystem around connectors — similar to what you built with the ISV partner program at VNDLY — or is the strategy to keep connector development fully internal? | Directly references Chuck's VNDLY ISV work and probes a strategic question about build vs. partner that would significantly shape the PM's scope. |
| shared_context | At Intuit I owned developer platform infrastructure and worked closely with SDK and API strategy — I'm curious how you think about the developer experience for data engineers consuming Pantomath's connectors: is there a self-service or SDK layer, or is it primarily configured through the product UI? | Bridges Felix's Intuit developer platform experience to Pantomath's connector UX, showing relevant depth while gathering concrete product architecture information. |
| shared_context | I spent time at Splunk owning search microservices and metadata infrastructure, which gave me a lot of exposure to the challenges of building reliable, observable data pipelines at scale — how similar or different are the reliability challenges you're facing with Pantomath's connectors compared to what you encountered with the Workday Connector at VNDLY? | Creates a peer-level technical conversation grounded in both Felix's Splunk experience and Chuck's VNDLY connector work, establishing credibility and gathering real signal about the engineering challenge. |
Conversation starters
- I saw you were a founding engineer at VNDLY and took it all the way through a $510M Workday acquisition — that arc from zero customers to enterprise exit is something I find genuinely fascinating. What was the moment you realized the company had something that could scale to that level?
- Your work building the 20-integration Workday Connector caught my attention immediately — I've been on the product side of integration ecosystems at Splunk and Intuit, but I'd love to hear what it was like owning that from the engineering side through an acquisition process.
- I noticed you went from Kroger's retail systems — serving 55 million users with that promotion platform — to a startup environment at VNDLY. That's a pretty significant context switch. I've made similar jumps between large-scale infrastructure and startup product work, and I'm curious what drew you back to the startup world with Pantomath.
⚠ Handle carefully
- Chuck only joined Pantomath in April 2025 — avoid questions that imply deep institutional history or suggest the company has established processes that may not yet exist; frame questions around 'how are you thinking about' rather than 'how does the company currently handle.'
- Chuck's title is Chief Architect, not CTO or CPO — avoid framing questions in ways that assume he owns product strategy or business direction; respect the architectural scope of his role and probe how product and architecture authority is divided.
- Chuck's LinkedIn skills list C#, ASP.NET, and Web Services — these are older-stack indicators that predate the modern data stack. Avoid implying he may not be current on dbt, Airflow, or Snowflake specifics; instead ask open questions that let him define his own depth in those areas.