Product Manager

Who We're Looking For

Product Manager

Clearlink is a remote-friendly company, prioritizing virtual and in-person collaboration. This is a remote-first role for candidates who are located outside of Utah and outside of commuting distance. For candidates residing within 50 miles of our Salt Lake City, Utah office, a hybrid schedule of 2-3 days in-office is required. We’re hiring a Product Manager to own our site experience as a product: the systems, components, and surfaces that shape how visitors move through our sites, and the lead capture experiences that turn them into qualified customers.

This role owns the experience that performs, and it is accountable for the KPIs that experience drives. You'll thrive here if you treat a site as a product with customers and a scoreboard, not a thing to keep tidy. You're a self-starter who sees gaps and fills them, builds order out of ambiguity, and gets energized by finding the experience that performs and then scaling it everywhere it can win.

You'll work collaboratively and cross-functionally with editorial, design, and engineering across the full product lifecycle: discovery, road mapping, design, implementation, and measurement. You'll identify the objectives and user behaviors that shape our experiences, build strategic plans, and provide ongoing direction for the systems that move the business forward. By balancing data with cross-functional communication, you'll lead these products from ideation to delivery, owning both iterative improvements to what exists today and the launch of new capabilities that deliver measurable value.

• The site experience product. You own the reusable systems and components that power our sites, balancing a standardized, scalable approach against the distinct needs of each site it serves.
• The lead capture experience. You own the surfaces where visitors become qualified customers: their structure, behavior, placement, and performance.
• The performance engine. You experiment across our sites to learn what lifts results, find what works, and scale the winners.

• Be accountable for the KPIs tied to the experiences and systems you own, and build, update, and prioritize work in service of moving them.
• Define what each initiative is meant to accomplish and the metric that will prove it moved, before the work begins, then set baselines, targets, and a measurement cadence so progress is visible and tied to business goals.
• Translate customer research and behavioral data into requirements that improve experience and conversion.
• Build and evolve the systems.
• Own the reusable systems and components that power our sites, balancing a standardized, scalable approach against the distinct needs of each site it serves.
• Turn requirements into clear project overviews, epics, feature specs, and user stories that design and engineering can build against.
• Maintain the governance and documentation that keep the system consistent, on-brand, and aligned to our design standards as it evolves.
• Run systematic experimentation across sites to learn what performs, then scale the winners.
• Partner with other product managers to sequence work against a shared, finite capacity, balancing your priorities against the rest of the network rather than optimizing for any one site.
• Think in one-company terms: the highest use of a shared team is the work that lifts the most sites at once, and your job is to find it and prioritize it.
• Serve your internal users: editorial and brand teams.
• Treat the teams who publish through these systems as your primary users, and make their adoption and day‑to‑day experience a measure of your success.
• Describe the benefits and functionality of new capabilities in a way that drives adoption and engagement across business units.
• Proactively monitor for friction and improvement opportunities, and create and maintain detailed product documentation.
• Ship with quality. Lead user acceptance testing for new capabilities before they reach production, with extra rigor given that a shared system can ripple across every site that depends on it.
• Coordinate technical implementation across shared engineering resources, keeping…