Product Manager

Morning Consult•New York, NY

2d•Hybrid

About The Position

Morning Consult is a global decision intelligence company changing how modern leaders make smarter, faster, better decisions. The company pairs its proprietary high-frequency data with applied artificial intelligence to better inform decisions on what people think and how they will act. This role is available in any of our office locations (Washington, DC; New York, NY; Chicago, IL) or can be based remotely, though candidates in Washington, DC or New York, NY are preferred. Join us in the office for catered lunch on Tuesdays, Wednesdays and Thursdays, or grab a beverage from the fridge for an impromptu after-work happy hour! The Role We're looking for a Product Manager to join our highly collaborative, driven, and creative product & engineering team. It’s never been a more exciting time to work at a data company building products on mountains of proprietary data. For the last few years, we’ve been continuously innovating on how we leverage AI to meet the next level of customer need, with creativity and speed. This is an execution-first role. You'll partner day-to-day with engineering to turn priorities into a strong, well-run backlog — writing tickets, unblocking work, tracking down the follow-up nobody else caught, and making sure nothing stalls between teams. We do a lot of our work in ambiguous problem spaces that are being mapped out as we go. Your job is to bring clarity and momentum to the work, not to have all the answers on day one. You'll work closely with a Senior PM who owns the broader strategic picture across two engineering teams. What we need most is someone who can lock into the details, keep things moving, and build trust with engineers and stakeholders along the way. Over time, as you build context and track record, this role has room to grow into more strategic ownership and direct client-facing work. We're intentionally open on background here. We're less focused on whether you've run a product team before and more focused on whether you're a self-starter who's smart, curious, and proactive. A few years of relevant experience is great; what matters most is how you operate.

Requirements

Roughly 3-5 years of relevant experience — this can be product management, or another background (engineering, operations, client success, program management) that's built the same muscles
Proactive, low-ego, and collaborative — you care more about the team's outcomes than individual credit, and you'd rather ask "want me to jump in on this?" than wait to be assigned
A strong, clear communicator who shares status and priorities without being asked, and who's comfortable saying "here's where this actually stands"
Comfortable moving fast and showing work early, even when it's not fully polished — you'd rather check in on direction than burn a week perfecting something that might be off-track
Curious enough to dig into a technical domain you haven't worked in before and keep asking questions until you genuinely understand it
A relationship-builder — engineers trust you, and people don't worry about what's happening on your team

Nice To Haves

Experience with APIs or technical/data products is a plus, but not required

Responsibilities

Own a clean, prioritized backlog with clear user stories, requirements, acceptance criteria, and scope decisions.
Following up until requirements actually land
Partner with engineering on solution design and scope, pushing for iterative releases that get value out the door without waiting for perfect
Set the team up for productive planning and refinement by coming prepared, not catching up in the room
Track the metrics that tell you whether something's actually working, and use them to inform what's next
Proactively surface risks, blockers, and things that aren't connecting — before they turn into fire drills
Work with engineering leads and your Senior PM partner to help shape and prioritize problem statements
Build enough domain fluency — through relentless, good-natured question-asking — to understand not just what you're building, but why it matters and what it unlocks downstream
Communicate clearly to a range of audiences: writing help docs and release notes, and keeping stakeholders honestly informed on status
As you grow in the role, take on more direct stakeholder and client conversations — asking the right discovery questions rather than just relaying what engineering tells you