JetBrains27.05.2026

Technical Product Manager (IntelliJ Scala Plugin)

Amsterdam

Обязанности

01Own the product vision for the Scala plugin, ensuring it provides fast, correct, and trustworthy IDE support that evolves with the language
02Analyze product usage statistics and run a consistent pipeline of user interviews to ground decisions in real workflows
03Use IntelliJ IDEA with the Scala plugin daily – dogfooding features, catching regressions, and validating the developer experience first-hand
04Maintain and develop reference projects that serve as showcases for new features, material for conference demos, and a living test bed for DX quality
05Own and continuously adapt the plugin roadmap for short-term release goals, mid-term initiatives, and longer-term projects related to the Scala ecosystem
06Align plugin planning with Scala compiler releases and IntelliJ IDEA release trains
07Make judgments about trade-offs and say "no" when cost, risk, or maintenance burden outweighs user value
08Define problem statements, success criteria, and scope for features, and then collaborate with engineers to validate and refine them
09Represent core Scala stakeholders – developers and library authors – and prioritize recurring pain points, for example, false positives, slow analysis, unreliable refactorings, onboarding pain points, and AI agent integrations
10Coordinate with Developer Advocates, the IntelliJ IDEA and Marketing teams, and other JetBrains teams

01Has professional software development experience in Scala (this is a must)
02Has at least five years of experience in technical product management or a comparable role in a complex technical domain
03Works closely with the product instead of relying solely on reports and meetings
04Has experience with AI coding tools and agents, and curiosity about how they are reshaping developer workflows
05Can define clear roadmaps with problem statements, success criteria, and explicit trade-offs
06Has strong communication skills in English – written and spoken – for both technical peers and executive audiences
07Is ready to represent the product externally at conferences, in blog posts, and in community interactions
08Takes the developer experience personally – not as an abstract metric, but as something they feel in their own daily workflow