Clasp Group Associate Product Manager at Clasp working alongside Product Managers to understand users and translate feedback into product specs. Manage partner data and measure product impact.
Responsibilities
Discovery and user feedback
Interview students and employer users, run surveys, and synthesize what you hear into insights PMs can act on.
Gather feedback from support tickets, Partner Success, sales calls, and usage data, and spot the patterns across them.
Run short research projects, such as competitive reviews or vendor evaluations, that feed roadmap decisions.
Specs and delivery
Draft user stories, requirements, and acceptance criteria with PMs and engineers.
After a release, track how features land, write follow-up tickets and fast-follows, and file clear, reproducible bug tickets.
Systems and data integrity
Advise Partner Success and Implementation on complex or unusual partner setups, helping them work out what the partner is really asking for and how our system should handle it.
Help keep our system in sync with partner data from HRIS and payroll integrations. Learn which data drives which rules, notice when they drift apart, and turn recurring issues into product fixes.
Partner with Operations on data backfills and cleanup. Spot recurring data quality issues, define the scope of the fix, check the results, and tell the affected teams what changed.
Think through how product and rule changes affect participants, payments, and reporting, and explain the impact clearly to internal teams and partners.
Qualification
1 to 3 years of experience in productData skillsMeasurement instinctSystems thinkingUser curiosityClear writingTechnical comfortOwnershipWhat We Give In ReturnHealth benefits (healthFlexible PTO policy
Required
1 to 3 years of experience in product, analytics, product operations, implementation, consulting, or a similar role.
Data skills: you've built dashboards people use, you use SQL to answer questions and to check data quality and validate results, and you're comfortable with a product analytics tool such as PostHog, Amplitude, or Mixpanel.
Measurement instinct: you can define what success looks like for a feature and tell a real result from noise.
Systems thinking: you trace how data and rules interact, spot edge cases and conflicts, and ask "and then what happens?" before anything goes live.
User curiosity: you've talked to users directly and can separate what they ask for from what they need.
Clear writing: your specs and tickets are easy for engineers to act on, and you can explain technical logic to non-technical partners.
Technical comfort: you understand how software gets built and work well with engineers.
Ownership: you follow through on all your work even the details, including the behind-the-scenes work, and flag problems early.