Product Manager

About GaggleAMP GaggleAMP helps companies turn employees into active advocates on social media. Our customers run employee advocacy programs that drive brand visibility, sales engagement, and recruiting impact, all with minimal effort from the people involved. We've been at this for years, have real customers, and have a clear point of view about what we do and who we do it for. Mission Own product at GaggleAMP so that every feature we ship makes our customers' jobs genuinely easier and proves measurable value to their organizations, applying phase-one discipline and customer evidence to every decision. Outcomes We share this scorecard openly so you know exactly what success looks like. By day 30: Reviewed at least 20 recorded customer calls and built working knowledge of customer pains and language patterns Held one-on-ones with each developer, the engineering lead, the customer success lead, the CEO, and at least two CS team members Read and internalized our product principles, persona docs, brand guide, and GTM playbook well enough to apply them in conversation Audited the current product backlog, can articulate what's in flight and why, and formed initial opinions on prioritization Scoped at least two product optimizations end-to-end (from usage data through a defined solution to engineering handoff) Produced a written first-impressions document for the CEO and engineering lead By day 90: Shipped at least one meaningful piece of new work that you scoped, designed, and handed off, with engineering buy-in Own and run weekly product/design reviews independently Produced a roadmap proposal for the upcoming quarter, defined as the full mix of new capability, optimizations to existing flows, and infrastructure work that affects usability. Grounded in customer evidence and our product principles Built your own customer conversation cadence (at least two live customer calls per month) Reduced senior leadership involvement in feature-level product decisions to near zero Made at least one clearly defensible "no" to a feature request, based on principle application rather than capacity Competencies Customer obsession and persona discipline. Every product decision grounded in real customer evidence, applied to a specific persona, not imagined users. Phase-one scoping discipline. Ship the smallest meaningful version first and let customer feedback drive what comes next. Comfortable cutting scope. Can defend "no" with reasoning. Strategic and tactical balance. Real product work is a mix of new capability, optimizations, and usability-affecting infrastructure, not just new feature delivery. Resist the bias toward shipping new things at the expense of improving what exists. AI-leveraged execution with human ownership. Use AI tools fluently across discovery, writing, design, and analysis. Own every outcome and deliverable as your own work, regardless of which tools helped produce it. AI is leverage, not a substitute for…