Naylor logo

Technical Product Manager

Salary
$115K–$135K
Hiring from
United States
Work type
Remote
Posted

623,633 remote jobs, straight from company career pages

100% free · New jobs every minute

Show job description

Naylor is replacing its association management system (AMS) — the platform client associations use to run membership, dues, subscriptions, events, committees and the finance behind them. The rebuild, AMS 2.0, is being delivered through a blended model: an external build partner, Naylor's internal engineering team and an AI-assisted pipeline for repeatable work. The current platform must keep serving clients until each one has moved.

This role is the single product owner for AMS across both platforms. You decide what gets built, in what order and why; you define what "done" means; and you hold every delivery lane — vendor, internal and AI-assisted — to that definition. You are the customer's voice inside delivery and the delivery team's voice in front of the business.

The initial focus is AMS through 2027. Ownership of the Careers platform roadmap may follow once the AMS 2.0 core modules are live.

Why the role exists now

  • Product decisions have no single owner. Scope, sequencing, acceptance and release decisions for AMS are spread across roughly ten people, each of whom has another primary job. The result is slower decisions and inconsistent standards.
  • The rebuild raises the stakes. With an external build partner engaged, unclear requirements become change orders. A clear, specification-led product owner protects both quality and budget.
  • Two platforms must be managed as one product. Every legacy fix, enhancement or client request is now also a decision about AMS 2.0: build it in the old platform, carry it forward, or retire it. That judgment needs one owner.

What you will own

1. Product direction and roadmap

  • Own the product roadmap across the legacy platform and AMS 2.0, sequenced by client impact, revenue and migration risk.
  • Define the minimum viable product module by module. Validate feature sets with client-facing teams, cut what associations do not use, and keep the scope honest.
  • Maintain the backlog as a prioritized, reasoned plan rather than an accumulated list, with the rationale visible to leadership and client services.

2. Requirements and acceptance

  • Translate business objectives and client needs into product requirements, user stories and acceptance criteria that engineers and the build partner can deliver without further interpretation.
  • Own the definition of done for each module: functional behavior, data and integration expectations, and the evidence required at each release gate.
  • Present material requests as options with a recommendation — what to build, what not to build, and why.

3. Build-partner and delivery-lane governance

  • Hold the external build partner to scope at the backlog level: review deliverables against specification, accept or reject with reasons, and identify scope creep before it becomes a change order.
  • Decide which work goes to which lane — partner, internal team or AI-assisted pipeline — with the Principal Architect, AMS.
  • Provide the product evidence that supports commercial conversations with the partner, including milestone acceptance and change-request assessment.
  • Own the AMS delivery plan across all three lanes: milestones, dependencies, sprint cadence and early escalation of risk, with legacy support and AMS 2.0 work balanced so neither starves the other.

4. Legacy platform and migration decisions

  • Make the invest, sustain or retire call on legacy AMS requests and defects, so effort on the current platform supports the transition rather than prolonging it.
  • Define the functional-parity baseline for AMS 2.0: which legacy capabilities carry forward, which are redesigned and which are retired.
  • Shape client migration sequencing with client services: which associations move, in what order and with what readiness criteria.

5. Release and adoption

  • Own product sign-off across the release path — internal review, validation, client beta and general release — and the go/no-go recommendation at each gate.
  • Coordinate client betas with client-facing teams and turn beta feedback into prioritized backlog decisions.
  • Ensure every release goes out with release notes that explain what changed and why it matters to the reader.

6. Commercial and customer alignment

  • Partner with the product-side business liaison so build decisions and go-to-market decisions — pricing tiers, packaging, rollout — are made together.
  • Act as the primary product contact for client services on AMS: anticipate needs, set expectations and decline misaligned requests with a reasoned alternative.
  • Report AMS product status to technology leadership with an accurate view of progress, risk and trade-offs.

7. Product knowledge and ways of working

  • Write and maintain the specifications, decision records and product documentation that keep AMS knowledge in shared documents rather than in individuals.
  • Use AI-assisted tooling as the default way of working, and help define how it fits the AMS delivery process.

How the role fits the AMS team

  • Technical Product Manager, AMS (this role)
    Owns: What gets built, in what order and why; requirements and acceptance; the delivery plan and cadence; product sign-off.
    Relationship to this role: Product authority across both platforms.
  • Principal Architect, AMS
    Owns: How it is built: architecture, data model, technical standards, engineering leadership.
    Relationship to this role: Peer. Functional and technical trade-offs are resolved between the two roles, with escalation only when a business decision is needed.
  • QA Engineer, AMS
    Owns: Quality assurance: test planning and execution, regression coverage, test automation and defect verification.
    Relationship to this role: This role sets the acceptance criteria; QA tests releases against them and supplies the quality evidence for each release gate.
  • External build partner
    Owns: Delivery of contracted AMS 2.0 scope.
    Relationship to this role: This role is the partner's product counterpart and accepts its deliverables.
  • Client services and product-side liaison
    Owns: Client relationships, commercial packaging and rollout.
    Relationship to this role: Partners on requirements, betas, migration sequencing and go-to-market.
  • VP, Technology and Digital Innovation
    Owns: Program direction, budget and vendor contract.
    Relationship to this role: Line manager; escalation point for scope, commercial and priority decisions.

What you bring

Required

  • Four or more years in product management or technical product management on a B2B software or SaaS platform.
  • A track record of owning requirements and acceptance for delivered software, not only tracking work defined by others.
  • Experience delivering through an external or blended build, managing a partner at the backlog level as well as the contract level.
  • Experience running a legacy platform and its replacement in parallel, including parity and migration decisions.
  • Enough technical depth to challenge engineers credibly: API-literate, comfortable with data models, able to read a technical specification critically.
  • A quality mindset: acceptance criteria, regression awareness and release gates are how you work, not overhead.
  • Clear, fast writing. Your specifications, decision records and release notes are finished products that people read and act on.
  • The ability to say no diplomatically and hold a priority line with stakeholders while keeping the relationship collaborative.

Preferred

  • Association management, membership, subscription, events or nonprofit software experience.
  • Exposure to payments, invoicing, dues or other finance-adjacent product areas.
  • Experience with Jira or equivalent tooling, and with modern .NET and Microsoft Azure delivery environments.
  • Hands-on use of AI tools in product or delivery work.

What success looks like

First 90 days

  • A working understanding of the legacy AMS, its clients and the open request and defect backlog.
  • An agreed AMS 2.0 MVP definition and module sequence, reviewed with technology leadership and client services.
  • Established working agreements with the Principal Architect, QA and the build partner: who decides what, and how acceptance works.
  • A single prioritized AMS backlog spanning both platforms, with the invest, sustain or retire decision applied to legacy items.

First 12 months

  • AMS 2.0 modules accepted against written acceptance criteria, with partner deliverables reviewed against specification and change requests assessed before approval.
  • At least one client beta completed and a client migration sequence agreed with client services.
  • Legacy effort visibly concentrated on work that supports the transition, with retired requests closed and explained.
  • Release notes, specifications and decision records maintained as the reference for AMS, without dependence on any one person's knowledge.

Naylor Association Solutions is an equal opportunity employer and is committed to hiring a diverse workforce.

Similar jobs

Apply for this job100% free