Highlights 

• Location: Armenia, Remote
• Stock options
• Languages: Fluent in English and Russian.

About Fundraise Up

We’re Fundraise Up - a global fundraising platform built to make donating to nonprofits fast, seamless, and accessible to all. Every month, our technology powers tens of millions of dollars in donations across the globe. We focus on innovation that directly impacts results: faster load times, higher conversion rates, global payment support, and accessibility-first design.

Our platform is trusted by many of the world’s leading nonprofits, including UNICEF, the Alzheimer’s Association, and a wide range of global NGOs. With a 4.9/5 rating across top software review platforms, we’re recognized not just for our impact - but for the quality of the product we deliver.

About the Role

This role is the primary owner of how the product team operates. You ensure quality and velocity don't trade off against each other — by building, scaling, and protecting the processes that make good product decisions repeatable.

You'll report directly to the CPO and serve as the main entry point for new Product Ops initiatives — prioritizing, routing, and leading the ones that matter most. You focus on what scales across the whole product team, not what solves a one-off problem for one squad.

The Product Ops team is two people: you and one manager — with plans to grow. This is a genuinely hands-on role — you'll be doing real work, not just directing it. Expect to own processes end-to-end, from design through adoption.

What You'll Own

• Be the primary entry point for new Product Ops initiatives — prioritize them, decide what gets resourced, and route what doesn't fit.
• Lead major cross-team process changes: design the frame, align stakeholders, and drive adoption.
• Own cross-team processes across the Product department (Product, Design, and Analytics) where central coordination is required — quarterly planning, goal decomposition, metrics alignment.
• Build and maintain shared frameworks and artifacts (prioritization logic, metrics models, decision templates) that improve clarity and consistency across the product team.
• Identify and escalate systemic process problems that require cross-team or leadership-level decisions.
• Drive AI automation of product workflows — identify high-leverage opportunities, build or oversee solutions, measure against baselines, and decide what scales across the team.
• Manage Product Ops focus and load: ensure the team works on things that move the needle, not reactive noise.

What Success Looks Like

• Product Ops initiatives have a transparent, understood focus — no one wonders what the function is for.
• Shared processes are adopted and used consistently across product teams (measured by adoption rate and CSAT).
• Operational noise decreases — fewer ad-hoc requests, less manual coordination, fewer alignment gaps.
• Product decisions become more predictable and higher quality — even as the company keeps scaling fast.

What We're Looking For

• Process design experience. You've built or significantly improved operational processes in a product or tech environment. You think in systems, not tasks.
• Cross-functional influence. You know how to align people who don't report to you. You bring clarity to ambiguous situations and can drive decisions across teams.
• Metrics-driven. You track adoption and satisfaction as seriously as any product team tracks conversion. You know how to set a baseline and measure change.
• Bias toward scalability. You distinguish between fixing a one-off problem and building something the whole team can use. When both paths are possible, you ask: will this still work when the team doubles?
• Full ownership of your domain. You take accountability for outcomes, not just tasks. Blockers are your problem to solve — not someone else's.
• AI automation fluency. You've used AI tools to automate workflows or processes — and you can identify where automation creates real leverage vs. where it's noise.
• Fluent English (C1+). We're a mixed company — the product team works in Russian, but you'll have English-language meetings daily and work with English documentation constantly.

Bonus Points

• Product fluency — you understand how product teams work: discovery, prioritization, planning cycles, roadmap trade-offs
• Background in product operations or program management
• Familiarity with OKR frameworks, quarterly planning processes, or company-wide goal alignment
• Comfortable working in a fast-scaling environment without a defined playbook for everything

Benefits

Our compensation package includes comprehensive benefits and perks, meaningful equity, and a competitive salary:

• 31 days of paid time off
• 100% paid telemedicine plan
• Home office setup assistance
• English learning courses
• Professional education budget
• Gym or swimming pool membership
• Co-working support
• Fully remote work

At JetBrains, we build developer tools that help engineers stay focused on solving hard problems instead of fighting routine work.

Within JetBrains AI, we are collaborating with Zed on the Agent Client Protocol (ACP), an open protocol that lets AI coding agents work inside editors and IDEs. ACP is already supported in JetBrains AI Assistant, and the project is jointly governed by JetBrains and Zed. We see ACP as a long-term investment in interoperability, developer choice, and durable AI-powered workflows across the JetBrains ecosystem. (The JetBrains Blog).

ACP evolves in the open. Real-time coordination happens in Zulip, actionable work is tracked in GitHub Issues, longer-form discussion happens in GitHub Discussions, and substantial protocol changes move through the RFD process. We need someone who can help JetBrains shape that work from the product side: define the right developer scenarios, align internal and external stakeholders, and turn ecosystem needs into clear priorities for JetBrains and for the protocol. (Agent Client Protocol).

This is not a generalist product management role. It is also not a pure protocol engineering role. It sits between developer-experience product work and protocol evolution.

This role is often a strong fit for someone who has spent several years as a software engineer – ideally on APIs, SDKs, web/backend systems, libraries, frameworks, or platform integrations – and then moved into product management or a hybrid product or engineering role.

This will be an exciting opportunity if you:

• Want to shape an open interoperability layer for AI-native software development.
• Enjoy turning messy cross-team technical discussions into clear product direction.
• Like working with engineers, agent developers, and external partners to make complex systems usable and durable.

In this role, you will:

• Identify and prioritize the developer scenarios JetBrains should support through ACP in JetBrains IDEs.
• Study how those scenarios are already handled in CLIs and agents, and define coherent IDE-native flows that JetBrains should support.
• Work on examples such as plan mode, sub-agent workflows, or agent-to-agent communication, and turn them into clear scenario definitions and product requirements.
• Talk to JetBrains product and engineering teams, external agent developers, and partners to collect requirements, constraints, and compatibility concerns.
• Turn those inputs into crisp problem statements, GitHub Issues, success criteria, and roadmap priorities.
• Partner closely with protocol engineers and ACP maintainers to translate validated scenarios into protocol proposals, implementation requirements, and delivery plans.
• Represent JetBrains in regular protocol conversations with Zed and the broader ACP community, helping drive alignment on what belongs in the protocol, what should remain implementation-specific, and what should wait.
• Balance immediate JetBrains product needs against long-term protocol design concerns such as extensibility, backward compatibility, clarity, and ecosystem fit.
• Define and monitor the right telemetry and product metrics for ACP-related surfaces, including agent installation success, authentication success, protocol feature adoption, task completion, reliability, and developer satisfaction.
• Help JetBrains make long-term, product-quality decisions about supporting ACP across multiple IDE experiences.
• Communicate decisions, trade-offs, and priorities clearly to highly technical stakeholders inside and outside JetBrains.

We’ll be happy to have you on our team if you:

• Have 1-4 years of product management experience, or equivalent end-to-end ownership in a hybrid engineering/product role.
• Have a substantial software engineering background and hands-on production coding experience in real systems.
• Understand how modern web and integration primitives work in practice, including OAuth, WebSockets, HTTP, JSON-RPC, and service-to-service communication.
• Are comfortable reasoning about APIs, protocols, payload schemas, event-driven systems, authentication flows, local/remote execution, and backward compatibility.
• Can discuss technical details credibly with engineers and agent developers, even when the conversation goes deep into protocol behavior, edge cases, or extensibility.
• Can take raw technical feedback and turn it into clear user scenarios, requirements, issue tickets, and written decisions.
• Have strong product judgment and can distinguish between a JetBrains-specific UX choice and a protocol-level capability that should be standardized.
• Have a data-driven mindset and know how to combine telemetry, qualitative feedback, and ecosystem signals in product decisions.
• Have strong spoken and written English.

We’d be especially thrilled if you:

• Previously worked as a senior software engineer, staff engineer, library/framework maintainer, SDK owner, or platform/integration engineer before moving closer to product work.
• Have experience with developer tools, IDEs, AI coding agents, CLI workflows, or interoperability layers such as LSP, MCP, or ACP.
• Have contributed to open-source projects or standards-like processes.
• Are comfortable working in public GitHub workflows with Issues, Discussions, pull requests, and proposal documents.
• Have built or supported products where compatibility, extensibility, and future-proofing mattered.
• Use JetBrains IDEs regularly.

#LI-KL1 

We’re looking for a Product Owner to join our team in Yerevan, Armenia!

✅ Key responsibilities:

🔹 Gather Functional and non-Functional requirements, maintain and verify requirements as well.

🔹 Manage Product Backlog: formulating the list of backlog items and prioritizing them as per the critical business objectives.

🔹 Backlog Refinement: ability to prioritize, enhance, and finalize the items with the team before the sprint planning.

🔹 Define Acceptance Criteria for their Product: the Product Owner must know what they want their product features to achieve.

🔹 Define Sprint Objectives.

🔹 Review and approve the work done by the development team: the product owner inspects the product increment made by the development team in each iteration, from design preparation to production release verification.

🔹 Provide effective communication to the stakeholders of the project: the Product Owner is the central communicator between the development team and the stakeholders.

🔹 Create and Maintain Epics, Stories, Use and Edge Cases.

🔹 Participate in OKR planning.

✅ Requirements:

🔹 Experience: At least 3 years as a Product Owner or similar role (Business Analyst, System Analyst, Quality Assurance Analyst).

🔹 Skills Requirements:

To execute tasks, technical understanding is required in the following areas:

- Requirements lifecycle

- Product backlog management

- Product development architecture

- Scrum and Agile development methodologies

- User experience principles

- Coding and designing (nice to have)

🔹 Communication Skills (Proficient in English).

🔹 Analytical Skills: ability to analyze various issues and find workable solutions as quickly as possible.

🔹 Organizational skills.

🔹 Leadership: You will lead a team (without being a manager), therefore you must be able to demonstrate effective leadership techniques.

🔹 Professional Certification: PSPO level 1 or similar, but not a requirement.