דרושים » מוצר » Product Operations Manager

Required Product Manager
About the role:
We've taken a platform-first, builder mindset from day one, developing the modular building blocks we call pillars. Our users are exceptional engineers who continuously build creative and unexpected solutions with our platform. Being a PM here means embracing that creative tension while staying relentlessly focused on where the platform needs to go next.
As a PM, you'll own a pillar end-to-end alongside your team of engineers and designers. You'll build and evolve it as a standalone value stream and as a connected part of the broader platform. PMs are full picture owners: they shape the story of their pillar from market positioning to technical enablement, defining success not just by what gets shipped, but by the measurable impact it delivers.
What you'll do:
Define what to build and why. Go deep with customers, analyze usage data, and research the competitive landscape. Bring that view to your team, build a sharp perspective on what's worth building next, and communicate the reasoning to engineering, leadership, and the market.
Shape experiences engineers choose to use. our developer experience spans the entire ecosystem across the UI, API, CLI, and daily chat and coding interfaces. Work closely with design and engineering to make each surface deliberate, from the first wireframe through launch.
Drive cross-functional impact. PMs don't hand off and wait. You work across engineering, design, marketing, sales, and CS throughout the full product cycle, accountable for picking the right problem, the solution built, and whether the launch lands.
Build for agents and developers. We are the context and action layer for both. Shape your domain so agents can act on it reliably and developers can navigate it intuitively. Understand the tradeoffs in how data, APIs, and interfaces serve both. Separate the signal from the hype, and use that view to sharpen your roadmap.
Measure what matters. Define success metrics before you ship. Track adoption, analyze what's landing, and iterate until the outcome is real.

About the role You own the product end to end: the problem, the prototype, the spec, the release, the experiment, and the call to keep it, change it, or kill it. Which parts of the product you're focused on follows the opportunities we decide to invest in, and you'll hold several of them at once. The craft is the same in all of them. Some of what we build is AI itself: an AI co-founder for business owners, and an AI-led signup flow. Some of it is ordinary product work: checkout, pricing, compliance filings, a dashboard. In both cases, AI is how the job gets done here, not a type of project you get assigned. You build the prototype yourself. Our PMs build working prototypes in AI coding tools such as Lovable and Claude Code - alone or with a designer, depending on the project. The prototype goes to engineering as the spec, with real components, real states and real copy. Not a wireframe and a document. You move fast. You have an engineering team building against your decisions, and you are responsible for what they spend their time on. We release several times a day, nothing waits for a quarterly plan, and what you sketch on Monday can be live by Wednesday. You run your own experiments. Design the TEST, declare the primary metric before you open it, set exposure, get it instrumented with the data team, read it, and call it. Tests run in Statsig, with results in Heap and Tableau, though often we skip the dashboard and have an AI agent read the TEST straight out of the warehouse. Closing your own TEST on control is part of the job. You get your own answers. The same habit applies to every question, not only to tests. Instead of filing a request and waiting, you go and find out. You are expected to notice when a number is wrong, and to say so before a decision gets made on it. You own the consequences. When a price renders wrong or a payment method stops appearing on one browser, you are the person who works out how many customers it reached, decides what we do for them, and makes sure it cannot happen the same way twice. You hold the stakeholders. Requests reach you from other product teams, BizDev, Marketing, Finance, Legal, CX and data, and they will not agree on what matters most. You hear them out, decide what your team takes on and in what order, and tell the people who did not get what they asked for why not. They also need to know what is changing, what it means for their work, and when it lands, before it lands.

Were rebuilding the application from the ground up, and youll co-own it. Its two products at once: the workspace analysts and government operators actually work in, and the composition layer underneath it - an app builder for missions. Youll build the data and UX primitives that other PMs assemble into a customer-tailored mission workflow. The problem to solve is a modular investigations system: sharp enough to compose into different missions, and open enough that agentic workflows run inside them rather than beside them.

What Youll Do
Own the layer everyone else builds on. The application itself. The rest of the product org, sales engineering, and every mission we sell run on the primitives you define.
Work on things that matter. Interdiction, mission planning, investigations - our product sits inside decisions with real global consequences.
Lead your own team of engineers. A dedicated team building with you. Youre not their manager, but you set what gets built and why, and youre in the architecture conversation rather than briefed after it.
Challenge, get challenged. We move between different kinds of hard, but we do it together. New research areas, novel world problems, new types of intelligence sources.
Present your own work. Small product org, no layers. Youre in front of the exec team, sales team, and marketing team.
Build your own agents and skills. Youll spend time abstracting your job and putting yourself in a position where your role is about judgment, not busiwork.
Join a team thats pretty fun, kinda smart, and a little stupid. We love working together, care about good work and good vibes in equal measure, are genuinely obsessed with solving hard problems, and want you to succeed here.

our company's product does the work a SecOps engineer does: it investigates coverage gaps against live enterprise security data, authors and tests detection logic, and tunes noisy alerting. That means product decisions here are SecOps engineering decisions, and they need someone who has actually done the job. You'll join our company's product team and own the detection engineering surface of the product - what good coverage analysis looks like, what correct detection content looks like, what a security team should be able to trust the product to do on its own. we are defining a category around Security Operations Resilience, and the fastest way to get that right is to be genuinely credible with the SecOps engineers we're building for.
What you'll be doing
Drive the detection product domain: Bring deep expertise in SecOps engineering across SIEM, data pipelines, and SOAR, and help the product team define where the product should excel. Develop a strong understanding of the day-to-day work of SecOps engineers and the challenges they face.
Turn expertise into product insight: Conduct deep, hands-on research across real security environments, SecOps engineering practices, data, and tooling. Combine customer feedback with your own experience and the knowledge of the broader team to identify meaningful problems, opportunities, and product directions.
Shape and execute the roadmap: Translate product insights into a focused roadmap aligned with company strategy and customer needs. Partner with the product and engineering teams to prioritize initiatives, make tradeoffs, define outcomes, and drive execution from discovery through delivery.
Turn problems into product direction: Translate ambiguous problems into clear product requirements and actionable plans. Work closely with engineering, design, and security experts to ensure complex technical problems are translated into products that are useful, intuitive, and technically sound.
Shape and evaluate AI agent capabilities: Define what our companys AI agent should be capable of doing as a SecOps engineer, what good looks like, and where it must be trusted or constrained. Develop evaluation frameworks, scenarios, and ground truth to measure and continuously improve agent performance.
Own product quality and outcomes: Maintain a deep understanding of how the product is used in real-world security operations. Validate assumptions, identify gaps, and use customer feedback, product data, and operational experience to continuously improve the product and its direction.

Working in Product means making bold decisions with the data you have. You're the type that always asks, “Is there a better way?” From product managers to designers to researchers, the people who thrive here are strategic by nature, curious by default, and comfortable sailing without a full map. So if you challenge assumptions and know how to bring multiple stakeholders together, the Fiverr Product team might be your place.

What am I going to do?:
Make an impact: Drive outcomes across the Fiverr marketplace for clients and freelancers alike — but expect the specific area you own to shift. Where you focus is set by our strategic Bets, and those change as the Bets change. Lead a multidisciplinary team: Collaborate with engineers, designers, and data scientists to drive product delivery and innovation. Turn data into decisions: Define how we collect, validate, and use the signals that power the product — translating data into reliable inputs for better decision-making. Drive the end-to-end user experience: Continuously improve the surfaces and flows that users rely on, from onboarding to ongoing engagement. Develop and execute roadmaps: Create strategic product roadmaps and lead their execution, balancing short-term delivery with long-term platform thinking. Collaborate across teams: Work with stakeholders across the organization to align on a shared direction and amplify impact. How we actually work: Fiverr's product org runs on strategic Bets — leadership sets a small number of company-wide Bets each half, derived directly from our OKRs, and most of our capacity flows there. Teams get assigned to whatever Bet most needs them next, not necessarily their "home" domain. That means the traditional model — a fixed squad with permanent mission and task ownership — doesn't really apply here. Scope, team composition, and priorities move as the Bets move, sometimes mid-cycle. You're joining a team and a mission-driven org, not a fixed job description, and the right person for this role reads that as the exciting part, not the risky part.

Equal opportunities:
At Fiverr, we know that talent has no single face. We welcome talent from everywhere and everyone because it makes everything we build better. Need accommodations? Just ask. And if this role excites you but you don't tick every box, apply anyway. The best people rarely fit the mold exactly.

In your first year, we expect you to set a clear quality bar for our search products that the team builds against, have a real influence on where our index goes next, and bring us a point of view on where search infrastructure is heading.

This is a hands-on senior IC role with real ownership, reporting to the Director of Product. You will work day to day with our search engineering and research teams, with the evaluation team, and with customer success, who bring us quality feedback from real accounts every week. Our search engineers are deeply experienced in large-scale retrieval, and the product team is small, so you will argue your case directly with the people building it. That only works if you have built at this scale yourself.

Your responsibilities will include:

Set the quality bar and release criteria for search: what good means per use case, and what a change has to clear before it ships. Our evaluation team owns the measurement, and you work closely with them on what to measure and why.
Own the depth, latency, and cost tradeoffs across our search products, and make them explicit and defensible.
Shape the direction of our index: what it needs to cover, how fresh it needs to be, and what quality bar it has to meet.
Build a point of view on where search infrastructure is going as agents, rather than people, become the main consumer, and turn that into a roadmap.
Know how we compare to the alternatives customers evaluate, and drive the work that closes the gaps that matter.
Work with customer success and directly with customers to understand where our results fall short in real workflows, and turn that into quality priorities.
Partner with the data and vertical product owners on what our corpus needs to contain and how results should be shaped per industry.

You'll be part of the team that owns every interaction a customer has with their FinOps data - helping some of the largest corporations in the world adopt and mature their FinOps practice. That runs from the budget they set for next year, to Billy, our FinOps assistant, to the heavy data APIs their platform teams build on top of us.

Inside a single customer, that's hundreds of users a day - engineers, FinOps analysts, finance leads, and increasingly AI agents asking on their behalf. Billions of dollars of cloud and AI spend run through us, so one decision made on a screen you designed moves millions. Make it clear, and a company builds differently. Make it confusing, and they go the wrong way for a quarter.

And the AI half is wide open. Three fronts, all live right now:

FinOps for AI. Make AI spend measurable - GPUs, tokens, models, inference - and attributable to the team, product, and customer that generated it.

AI for FinOps. Agents that 10x a FinOps team. The furthest edge of FinOps innovation, and no playbook to copy.

We are for agents. Agents are becoming the ones asking and acting. We have to be the layer they query and act through - which means designing for a user who isn't human.

How we work, and who we're looking for:

We move fast, we work hard, and we have a good time doing it. You'll love it here if:

You prototype with AI, hand it to our coding agent, and get an answer in days instead of quarters.

Speed is the part of the job you enjoy, not the part you survive.

You'd rather ship something imperfect to ten enterprise customers this month than a perfect thing next quarter.

You don't believe in six-month roadmaps either. A plan written in January is fiction by March, and you'd rather re-plan every few weeks and be right.

You want to sit across from the sharpest FinOps and platform people on earth, hear exactly what's wrong with your product, and have your fix in their hands days later.

You already use AI to do real work, not to look busy. You've built with it, and you can tell output from value.

You want to define products that don't exist yet, in a category being invented right now.

You're comfortable being the most junior person in one room and the most senior in the next, on the same day.

And probably not, if:

You need a stable roadmap, a quiet quarter, and a clear lane.

Your favorite part of product is the process.

You want to be handed requirements, or hand them off.

You use the term strategic to describe your next pm position; we build and create value; we dont talk about strategy for a living.

Your AI experience is mostly having opinions about AI.

You will sit with customers in these industries, learn how they actually work, and turn their needs and pain points into clear specs. You will build with engineering, ship it, and make sure go-to-market knows how to sell it. You own the outcome, not just the handoff: from the first market call through to adoption and revenue.

The hard part is choosing. There are more verticals worth building than we can build, and the difference between a good year and a wasted one is knowing which ones to invest in and which to walk away from, even when a large customer is asking for another.

In your first year, we expect you to know our top use cases better than anyone here, ship a product built for one of them that customers will pay more for, and have a defensible view of what comes next.

This is a hands-on senior IC role with real ownership. You will work within a small PM team reporting to the Director of Product, alongside engineering, research, data, and go-to-market.

Your responsibilities will include:

Own the vertical roadmap. You decide where we invest, what we ship for each, and when a vertical is not worth it.
Shape the product surface on top of the data, so a customer gets something built for their job.
Find and evaluate the data behind each vertical, across public sources and paid providers, and decide what is worth investing in.
Sit with customers in these industries until you understand their workflow, then turn that into specs engineering can build.
Set what a good answer looks like in each use case, working with our evaluation team, who own how we measure it.
Work with customer success to learn what customers ask us for and what makes them leave.
Partner with the search owner on how results should be ranked and shaped for each use case.

Were looking for an AI Product Manager to join our product team and lead our Platform and shape the next generation of AI developer tools. This is a high-impact role for someone who thrives at the intersection of technical depth, user empathy, and product thinking. This role is ideal for someone who has worked on technical or developer-facing products, is deeply customer-oriented, and is comfortable rolling up their sleeves when needed.

Own the product lifecycle for one or more product areas - from ideation and requirements through delivery and go-to-market enablement.
Work closely with R&D teams on a daily basis - participating in technical discussions, helping shape architecture trade-offs, and ensuring the team has clear, well-defined requirements.
Spend significant time with customers: conducting discovery interviews, understanding pain points firsthand, and translating insights into product decisions.
Enable the sales and customer success teams with the knowledge, materials, and positioning they need to land deals and drive adoption.
Define and validate product opportunities through customer research, data analysis, and competitive intelligence.
Translate complex technical concepts into clear product requirements and crisp user stories.
Drive cross-functional alignment across engineering, design, sales, and customer success to ensure launches land well.
Establish and track success metrics, running experiments and iterating based on evidence.
Be the voice of the developer - obsessively understanding how developers work, what they struggle with, and where AI can genuinely help.