דרושים » תוכנה » Product Manager

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.

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.

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.

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.

We are looking for a Principal Product Manager to join our team. This is a hybrid capacity in our Israel/Tel Aviv Office role, reporting to the Senior Director, Product Management in the Security Operations Platform Product Management department. Join our data fabric and secops platform team, work in the dashboards, reporting and measurement product areas. Lead the product effort for platform reporting and dashboarding, as well as advanced semantic capabilities such as calculated dimensions, measurements, aggregations and custom KPI capabilities, enabling best-in-market product capabilities and UX that will be used by our security operations applications offerings and personas.

What youll do (Role Expectations)

Lead product discovery by deeply understanding customer problems, business goals, and operational constraints across reporting and dashboarding products that serve multiple security operations use cases

Define the product vision and roadmap for AI-powered, simple platform reporting and dashboarding capabilities from discovery through planning, UX, documentation, customer validation, and launch

Work day-to-day with engineering to prioritize backlogs, clarify scope, and ensure high-quality execution

Collaborate with applications product managers, and customers to facilitate feedback and success across multiple personas and use cases, partnering with go-to-market, sales, and customer success teams to support pilots, launches, and customer adoption

Measure product success using adoption, usage, customer value, and business outcome metrics

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.

Required Product Manager, Mobile
About the role:
Our mobile app is a critical component in the day-to-day financial operations of the worlds leading financial institutions.
As the Mobile PM, youll own the full product domain: driving the roadmap, collaborating closely with engineering and design, and ensuring every feature ships with precision and measurable impact. But this is more than a customer-facing product - its also a foundational platform that other product teams across rely on to deliver their features to mobile users. Youll own both dimensions: driving the customer experience outbound while advancing the infrastructure that makes it possible. As the world moves toward agentic, AI-native financial operations, this team is building exactly that. You define what gets built and why.
What youll own:
The mobile product end-to-end - roadmap, strategy, and delivery across iOS and Android, with full accountability for outcomes.
The customer experience - deeply understanding how institutional users interact with their financial operations on mobile, and continuously raising the bar.
The mobile platform - working with product teams across to understand their needs and ensuring mobile can support their features effectively.
The AI and intelligence layer on mobile - defining how smart, proactive capabilities get surfaced to users in a way that adds real value.
What the work actually looks like:
Spending significant time with customers and data - forming a sharp, evidence-based view of what to build next and why.
Making hard prioritization calls - balancing customer-facing improvements, platform needs from internal teams, and long-term product investments.
Working across teams - product, engineering, design, security, and customer success - to align on scope and get things shipped.
Owning the full arc of a feature - from problem definition and spec to launch, adoption, and iteration.

We're looking for a Product Manager to own the data and knowledge component of the platform end to end. This is both a strategy and an execution role: you'll decide what execution responsibilities the product would expand to and be in the details with engineering and design shipping it. The hard part isn't building a workflow - it's knowing which work a customer will genuinely hand to an agent, and what has to be true before they will.
What You'll Do:
Architect the Data Fabric: Own the data layer, defining schemas and cross relationships across IAM, network, and security domains to power agent capabilities.
Lead the Knowledge Layer: Own how policies and operating procedures are captured, structured, and updated so agents apply them reliably.
Build the Customer Experience: Partner with design and engineering to build user interfaces for data exploration, search, reporting, and connection health.
Scale Data Fabric and Knowledge as a Platform: Own the internal interface between data layers and other product components to feed agent visibility and decision making.
Drive Field to Roadmap Feedback Loops: Partner closely with customer facing and POC teams to turn real world field signals into scalable product features.

Required Product Manager , Developer Experience
About the Role:
The majority of our customers consume our APIs to build products on top of the platform, and that share has grown substantially over the past years and continues to grow steadily. Developers are the most strategically important customer segment we have, and this role owns how they experience us: defining what it means to build on our platform, making our APIs and infrastructure something developers choose and trust, and closing the gap between what weve built and the potential it represents. This role is central to how we grow as a platform business.
What Youll Own:
The developer platform product area end to end, from the tools developers use to discover and test our APIs to the reliability of the infrastructure their integrations depend on
The developer experience: what it feels like to build on our platform, where the friction is, and how we close the gap
The developer persona inside Platform, carrying it into roadmap decisions, cross-functional planning, and conversations with customers
The quality bar for API contracts and developer-facing surfaces across
What the Work Actually Looks Like:
Talking to developers to understand their real business problems, then translating those into product decisions rather than feature requests
Deciding what to build, what to defer, and why, across a product area where the right trade-off isnt always obvious
Defining the problem clearly enough that the solution has a chance of actually working: writing specs, challenging assumptions, and pressure-testing ideas with engineering and design before anything gets built
Tracking whether what shipped solved the problem, and being honest when it didnt.