Head of Product

At JetBrains, code is our passion. Ever since we started, back in 2000, we have strived to make the strongest, most effective developer tools on earth. By automating routine checks and corrections, our tools speed up production, freeing developers to grow, discover, and create. The largest department at JetBrains, the IntelliJ department is responsible for:

• The majority of our IDEs: IntelliJ IDEA, PhpStorm, WebStorm, GoLand, CLion, RubyMine, and RustRover, representing the company’s main revenue streams.
• The IntelliJ Platform, on top of which other JetBrains departments and external vendors create their IDEs.
• JetBrains Marketplace.
• AI Assistant.

The IntelliJ Head of Product role involves:

• Defining the product strategy, based on an understanding of users, market trends, our competitors, and the company’s long-term strategic goals.
• Building, mentoring, and leading a team of product managers.
• Ensuring a great user experience for our products.
• Finding new revenue streams.
• Overseeing the discovery and delivery of strategic product initiatives.
• Aligning product development efforts across different teams and departments.

Success as a Head of Product is defined by:

• Business outcomes: revenue and market share.
• Product outcomes impacting business: user satisfaction and retention.

Our ideal candidate will have:

• Overall experience
• At least 7 years of experience in product management, with at least 4 years in a leadership position (Head of Product or CPO).
• Familiarity with building and leading large product management organizations.
• Experience in being responsible not just for a product but for the overall business strategy associated with it.
• Prior experience as a software developer.

Examples of challenges the Head of Product will deal with:

• Finding product and business opportunities to increase the market share of CLion, GoLand, WebStorm, and RustRover.
• Finding product and business opportunities to grow revenue in IntelliJ IDEA and PhpStorm.
• Improving onboarding of new users to our IDEs.
• Unifying our IDEs into a single ecosystem which provides value to its users.
• Building the product organization within the department: structure the team, grow existing PMs, hire new ones, and train them to autonomously solve the challenges listed above.
• Switching the team mindset from outputs to outcomes.