Product Manager

Role: Product Manager

Location: Mexico – Remote

Employment Type: Fulltime

What You Will Do

• Prototype with AI-assisted tools (Cursor, Claude Code, Figma Make) so stakeholders can react to something real before engineering commits.
• Design end-to-end authoring and publishing flows, including important states and edge cases in a newsroom: errors, empty states, concurrent edits, and deadline moments.
• Shape well-defined bets for the CMS squad, with briefs that include clear appetite, boundaries, success criteria, and identified risks before the cycle starts.
• Run lightweight discovery with editorial, production, and operations users through shadowing, usability checks, session reviews, and quick experiments.
• Define measurement for each bet upfront (time to publish, error rates, task completion, adoption) and review the results after launch.
• Handle day-to-day alignment for your bets, including privacy, compliance, and business stakeholders, so the squad stays unblocked.

What Success Looks Like

• The squad starts every cycle with a shaped brief and a tested flow, not a loose idea.
• Flows ship in reliable increments, use the design system consistently, and require little rework from engineering.
• Editors and producers notice that the tools are getting faster and less error-prone, and say so.
• Each bet has a readout: what moved, what did not, and what changes next cycle.
• Engineering leads describe you as a trusted partner on trade-offs, not a handoff.

What You Bring

• 5+ years of experience shipping internal tools or workflow products as a Product Manager, Product Designer, or both.
• Strong interaction design skills: clear hierarchy, sensible defaults, graceful handling of mistakes, and polish that matches shipping quality, not mockup quality.
• Comfort working closely with backend constraints (APIs, data models, permissions) and designing within them rather than around them.
• A default approach of prototyping with AI tools and validating with real users before requesting engineering time.
• Fluency with analytics and lightweight experimentation, and the discipline to define success before building.
• Ability to onboard quickly, operate with little oversight, and communicate clearly with both technical and editorial audiences.