Questions and Answers Session
summary
The Q&A discusses JetBrains hiring and product strategy with concrete points: a Forrester ROI study claims developers become several-hundred-percent more productive after adopting JetBrains tools; Rider is a paid product (~$13/month personal) with no community Rider planned; writing plugins is a supported way to engage and get noticed. Hiring combines algorithmic technical checks and cultural-fit interviews, supported by internships, scholarships and university partnerships; strategic priorities include Kotlin and cross‑platform work (as an alternative to Flutter), plus focus on lightweight editor work and plugin ecosystems guiding product decisions and splits.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:47IDE productivity differences
- 3:14Joining JetBrains
- 6:31Interview process
- 10:26Engineer to manager
- 13:23Build automation tools
- 14:08C# and .NET support
- 16:17Toxic employees
- 18:48Rider community edition
- 22:08User growth and education
- 25:52Cross-platform vs Flutter
- 27:59Company growth plans
- 30:31Why not one language
- 31:58Separate language editors
- 35:39JetBrains paths and prospects
- 37:53Employee metrics
- 38:38IDE performance issues
- 42:14Summary
related talks
44mDeveloping Native Product Vision in Teams and Individuals
13mFrom Fan to Developer Advocate - Interview
49mStories about IntelliJ IDEA and productivity with online/offline influencers
44mFrom TUM to Team Lead: A Journey in Software Development and JetBrains
34mNative Agile Psychology of Teams and Individuals
01h 09mPlatform Wars
35mLearn and Teach Java with JetBrains!
13mGetting hired in Rust - Recruiter's perspective