JetBrains - Product Designer (.NET Ecosystem)

• Own the design process from early research through shipped pixels –not just the middle part. • Work across multiple products while maintaining ecosystem coherence. • Partner with product managers, engineers, and researchers to shape product direction (you’ll have a seat at the table, not just a chair in the corner). • Conduct and participate in user research: interviews, usability testing, and design validation. • Build in Figma – fast, organized, with prototypes that actually communicate intent. • Navigate complex technical domains and translate them into clear, usable experiences. • Contribute to design system, and pattern documentation. • Present and defend your design decisions to stakeholders and leadership. • We’ll be happy to have you on our team if you have: • Strong product design craft: You can take on a problem from research through to delivering a polished UX, and you sweat the details others miss. • Strong product design craft • Figma fluency: You’re fast, your files are organized, and you can build prototypes complex enough to test real interactions. • Figma fluency • Comfort with technical complexity: You’re willing to design for domains you don’t fully understand yet, and you learn quickly. • Comfort with technical complexity • Systems thinking: You can hold multiple products in your head and design for ecosystem coherence, not just individual screens. • Systems thinking • Independence: You drive projects forward without waiting for direction. • Independence • Research capability: You can run user interviews, synthesize findings, and turn them into design decisions. • Research capability • Basic coding literacy: You don’t need to ship production code, but you’ve written enough to know what a breakpoint is, why a build might fail, and what developers actually experience when they work. • Basic coding literacy • Clear communication: You can explain your reasoning to engineers, PMs, and leadership – and you can push back when needed. • Clear communication • We’d be especially excited if you also have: • A developer background or engineering mindset: you understand how software gets built. • Experience designing developer tools, technical products, or complex professional software. • Opinions about how IDEs should work, backed by actual usage. • You’ll join a small design team (currently 3 people, including the lead) embedded in the .NET ecosystem. We’re building out our practices – prioritization frameworks, intake systems, and research processes – so you’ll shape how we work, not just what we ship. • The broader .NET organization includes product managers, engineers, QA, researchers, marketing managers, and technical writers across multiple products. Design partners with all of them. Here’s the thing: The engineers building these tools are also .NET developers – they’re your users. You’ll sit alongside the people whose workflows you’re designing for. That’s one of the rarest feedback loops in product design, and it changes how you work.