Coding agents are only as good as the context they're given. Most explore a repository like a new hire on day one – grepping, opening files, guessing. JetBrains Context replaces that with actual knowledge of your whole codebase and resources, served to any agent that asks. If you want to own the layer that decides what an agent knows before it writes a single line, this is for you.

About JetBrains

We create intelligent software development tools for developers and teams. More than 15 million users, over 300,000 companies, and 88 of the Fortune Global Top 100 rely on our products to solve real, complex problems. Our mission is simple: make development teams more productive and AI adoptable at scale.

What you’ll do

As agents get better at searching for themselves, what is the durable value of a managed retrieval layer? We need someone with an opinionated answer to own JetBrains Context as a product – defining what it is for, who it is for, how we measure success, and where it goes next.

This is a hands-on role where you'll manage the product from a terminal and agent session rather than slides. You'll bridge the technical core and cross-functional teams: collaborating closely with engineering and ML teams on indexing pipelines and retrieval quality, working with Air, IDE, and Junie teams on integrations, and partnering with marketing, developer advocacy, sales, and customer success on positioning and adoption. You'll take full ownership of defining problem statements, setting explicit trade-offs, and balancing cost, latency, and freshness across the platform.

Day to day, you will:

• Build and maintain a deep working understanding of chunking, embeddings, index freshness, retrieval, reranking, and agent-facing surfaces.
• Define and defend an opinionated vision for the product's evolution, including explicit target audiences, use cases, and key success metrics.
• Translate product strategy into actionable problem statements, priorities, plans, and milestones with an explicit definition of “done”.
• Communicate product direction clearly to engineering, leadership, cross-functional stakeholders, customers, and prospects.
• Analyze competing context and code-search products through direct use to establish clear differentiators and identify gaps.
• Define core operational and product metrics – index freshness, retrieval quality, agent task outcomes, adoption, retention, and unit economics – to guide decision-making.
• Represent the product externally by sharing roadmaps, publishing updates, speaking to developer audiences, and gathering community feedback.
• Partner with ML teams on model evaluation and platform teams on service scale, reliability, and cost.

What you’ll bring

• A well-argued point of view on where AI-first development is going and what agents genuinely need from a context layer.
• Comfort with technical depth across embeddings, retrieval quality, sub-agents, tool-calling, indexing costs, and API design.
• The habit of using the product you build daily alongside competitors' tools.
• Communication that adapts to different audiences, from staff engineers and enterprise architects to conference attendees.
• A data-informed approach that combines telemetry, evaluation results, customer conversations, and market signals.
• Comfort with ambiguity and a preference for defining a new category over copying an existing one.

What you’ll need

• Proven experience owning a complex developer, platform, or infrastructure product end to end, including strategy and roadmap.
• Hands-on familiarity with modern AI coding tools and agent workflows.
• The technical capability to work directly with engineering on retrieval behavior, APIs, data models, and integration surfaces.
• The ability to define metrics for quality-sensitive products and build evaluation habits that maintain product standards.
• Experience communicating a product externally through written content, talks, or community engagement.
• Practical experience with search, retrieval, RAG, developer search, or static analysis at scale is a plus.

What success looks like

Within your first months, you'll form and share a clear thesis for what JetBrains Context is and is not – one the engineering team recognizes as theirs and leadership can invest in. You'll establish a metrics story that distinguishes real retrieval quality from vanity usage, a roadmap with clear trade-offs, and a documented evaluation of serious competitors.

Longer term, success means JetBrains Context becomes a deliberate choice for developers and organizations, agents get measurably better answers because it exists, enterprises adopt it for its governance and scale, and the market clearly understands its unique value because you've communicated it effectively.

Why join JetBrains? 

• Strong base salary. We offer competitive pay that reflects your skills and experience.
• Flexible work location. Enjoy the freedom to work from home or from the office.
• Remote work. Spend up to 30 days per year working remotely from abroad.
• Extra time off. More days to relax, recharge, and do the things you love.
• Medical insurance allowance. Enjoy peace of mind for you and your family
• Learning and development opportunities. Access to conferences, courses, and language classes.
• Language classes. Pick up the local language or sharpen your English skills.
• Fuel your day. Enjoy a hot meal or receive a lunch allowance on workdays.
• Mental health support. To help you feel your best, we provide easy access to professional mental health services.
• Sports benefit. Enjoy an on-site gym or sports club stipend.
• Internal events. Join company-wide celebrations and team gatherings.

*Some benefits may vary depending on location.

#LI-HYBRID - if you want LinkedIn to post your role as hybrid in all the locations where the role is open ---> leave this tag in JD
#LI-AA1