← anthropic / Product Manager, Developer Productivity
candidate_questions / art_YbbossWh6U8
role
model
anthropic/claude-sonnet-4.6
created
2026-05-19T20:32
Interviewer
Based on the LinkedIn URL provided, the specific profile content for Lucas Gonzalez Pagliere was not accessible in the pasted text — only the URL was shared without profile details. As a result, questions anchored to his specific career journey, tenure at Anthropic, prior roles, or stated expertise cannot be fabricated. The questions below are grounded in the role description and the candidate's background, with interviewer-specific anchors left as structural placeholders that should be filled in once the actual profile content is reviewed. Shared context between Felix and the interviewer cannot be confirmed without profile data.
Questions to ask them (20)
| category | question | why |
|---|---|---|
| interviewer_experience | What drew you to this particular team at Anthropic, and what's kept you engaged as the company has scaled so rapidly? | Opens a genuine dialogue about their personal journey and what they find meaningful — surfaces retention signals and what they value in the org. |
| interviewer_experience | How has your own role evolved as Anthropic's engineering organization has grown? I'm curious what problems looked very different at, say, 200 engineers versus where you are today. | Reveals how the org has matured, what growing pains looked like, and implicitly what this PM role will inherit. |
| interviewer_experience | What's the most counterintuitive thing you've learned about developer productivity in an AI-first engineering environment — something that surprised you compared to how you'd thought about it before joining Anthropic? | Invites candid reflection and surfaces genuine institutional knowledge that isn't in any job description. |
| role_team_dynamics | If I were to look back at the end of my first 90 days and call it a strong start, what would I have accomplished — and what would the team say about how I showed up? | Gets concrete on near-term expectations and reveals what 'good' looks like culturally, not just deliverable-wise. |
| role_team_dynamics | The JD mentions partnering with Infrastructure, Inference, Research, and Product Engineering — four very different stakeholder groups with competing priorities. How does the team currently navigate prioritization conflicts across those groups, and where does this PM role have the most leverage? | Surfaces real political dynamics and whether the PM has genuine authority or is primarily a coordinator. |
| role_team_dynamics | What's the current state of the developer productivity engineering team — headcount, how it's structured, and how embedded is the PM in day-to-day engineering decisions versus operating at a higher strategic layer? | Clarifies the operating model and whether this is a strategic or execution-heavy role. |
| role_team_dynamics | What's the single biggest unsolved problem on the developer productivity roadmap right now — the one that, if this new PM cracks it in year one, would be genuinely transformative for Anthropic's engineering velocity? | Reveals the real mandate beneath the polished JD language and helps Felix assess fit with his strengths. |
| technical_environment | The JD references build and CI infrastructure running across multiple cloud providers, plus accelerator toolchain management for GPUs, TPUs, and Trainium. How mature is the current build system — are we talking greenfield design decisions, or inheriting and scaling something already in production? | Felix has deep CI/CD and platform scaling experience at Intuit; this calibrates whether his 0-to-1 or scale-up skills are more immediately relevant. |
| technical_environment | How is Claude currently integrated into the internal developer workflow — is it primarily IDE-level autocomplete, or are there already agentic workflows where Claude is autonomously generating, testing, or reviewing code in CI pipelines? | The JD describes a 'fundamental shift' toward AI agents — understanding the current baseline helps Felix assess how far along the vision is versus aspirational. |
| technical_environment | On the metrics side, what does Anthropic currently instrument to measure developer productivity — and how much of that infrastructure exists today versus being something this PM would need to define and build from scratch? | Felix has experience with telemetry and BigQuery-driven prioritization at Intuit; this surfaces whether he'd be building on existing foundations or starting fresh. |
| culture_working_style | How does the team handle disagreements between what engineering leads want to build and what the PM believes is the right strategic bet — can you walk me through a recent example of how that tension got resolved? | Reveals the actual power dynamic between PM and engineering, and whether PMs have genuine product authority. |
| culture_working_style | Anthropic's mission around AI safety is central to everything — how does that show up in day-to-day decisions on the developer productivity team? For instance, when there's a trade-off between shipping fast and ensuring governance around agentic code workflows, how does the team navigate that? | Tests whether safety is a lived value in this team's decisions or primarily a company-level narrative. |
| culture_working_style | How much autonomy does this PM role have to set roadmap direction versus needing to align upward through multiple layers before committing to a strategic bet? | Felix has operated as a Staff PM with significant autonomy; understanding the decision-making latitude helps him assess fit. |
| growth_development | For someone coming in with strong platform PM and AI tooling experience, what's the growth trajectory that makes the most sense — is there a path toward broader infrastructure product ownership, or does this role tend to deepen into a specialized developer experience domain? | Helps Felix understand whether this is a deepening or broadening opportunity, and signals long-term ambition without being presumptuous. |
| growth_development | How does Anthropic invest in PM development — are there structured mechanisms for PMs to stay technically sharp as the AI and infrastructure landscape evolves, or is that largely self-directed? | Felix is clearly a continuous learner (NeurIPS, RL workbench, teaching at De Anza); this surfaces whether the environment will sustain that. |
| strategy_vision | The JD describes a 2–3 year horizon where a meaningful share of code is written, tested, and reviewed by Claude. What does Anthropic's internal vision for that world actually look like — is there a concrete north star for what the developer experience looks like when AI agents are first-class contributors in the workflow? | Tests whether the vision is genuinely developed or still aspirational, and gives Felix a chance to engage substantively with his own thesis on AI-native development. |
| strategy_vision | As AI agents take on more of the inner loop — writing and testing code — the JD notes the outer loop (review, validation, deployment) risks becoming the new bottleneck. How is Anthropic thinking about that governance and trust layer, and is that a product problem this PM would own or does it sit elsewhere? | Directly engages the most intellectually interesting part of the role and surfaces scope clarity on a genuinely hard problem. |
| strategy_vision | Anthropic is in a unique position of both building frontier AI and being a heavy internal consumer of AI-assisted development. How much does this team's work feed back into Anthropic's external product thinking — is there a flywheel between internal developer productivity learnings and what gets built for external Claude users? | Surfaces whether this role has external product influence, which would be a significant differentiator for Felix's long-term impact. |
| shared_context | I spent several years at Intuit scaling internal developer platforms — including CI/CD, SDK frameworks, and a self-service developer portal that cut onboarding from weeks to hours. One thing I found was that internal platform adoption is almost entirely a product quality problem, not a mandate problem. Is that dynamic something you've seen play out here, and how does the team think about internal developer NPS as a first-class metric? | Draws on Felix's directly relevant Intuit experience to build credibility and invite a peer-level conversation rather than a one-way interview. |
| shared_context | I've been building with Claude's MCP SDK in my own projects and have a strong intuition for where the agentic workflow abstractions feel natural versus where they create friction for developers. Has the team done much internal research on how Anthropic's own engineers experience Claude as a coding collaborator — and is that a structured feedback loop this PM would own? | Demonstrates hands-on Claude experience and positions Felix as someone who brings genuine product insight, not just PM process. |
Conversation starters
- I noticed the role sits at this really interesting intersection of classical platform engineering — build systems, CI/CD, monorepo tooling — and this genuinely new frontier of AI-native development. I'd love to hear how you personally think about that balance, because I suspect the team is navigating both simultaneously rather than sequentially.
- I've been building with Claude's MCP SDK in my own projects, and one thing that's struck me is how much the developer experience of working *with* an AI agent differs from working with a traditional API — the trust model, the feedback loops, the governance questions are all different. I'm curious how that's showing up internally at Anthropic.
- I spent a few years at Intuit scaling internal developer platforms, and the hardest part was never the technical architecture — it was the adoption and trust problem. Engineers are the most skeptical internal customers. I'd love to hear how Anthropic thinks about that challenge when the platform you're building is also powered by AI.
⚠ Handle carefully
- Without access to the interviewer's actual LinkedIn profile, avoid making any assumptions about their tenure, prior companies, or specific background during the conversation — ask open questions rather than referencing details you cannot confirm.
- The compensation range ($385K–$595K) is unusually wide; avoid any questions that could be read as negotiating or anchoring on comp during the interview — save that for the recruiter.
- Anthropic has had public attention around AI safety culture and internal debates; avoid probing questions about internal disagreements or safety culture tensions that could put the interviewer in an uncomfortable position — frame safety questions around product decisions rather than org dynamics.