Product Designer (.NET Ecosystem)

JetBrains
Full-time

📍 Job Overview

Job Title: Product Designer (.NET Ecosystem)

Company: JetBrains

Location: Belgrade, Serbia; Berlin, Germany; Limassol, Cyprus; Madrid, Spain; Munich, Germany; Prague, Czech Republic; Remote, Germany; Warsaw, Poland; Yerevan, Armenia

Job Type: Full-Time

Category: Product Design / UX Design

Date Posted: 2026-06-15T14:53:26

Experience Level: Mid-Level to Senior (estimated 5-10 years)

Remote Status: Hybrid/Remote Options Available

🚀 Role Summary

  • Drive end-to-end product design for JetBrains' .NET ecosystem, encompassing leading IDEs and performance tools.

  • Collaborate closely with product managers and engineers to shape product strategy and deliver sophisticated user experiences for expert developers.

  • Maintain coherence and consistency across a complex suite of developer tools, including Rider, ReSharper, and profilers.

  • Leverage user research and a strong design craft to solve challenging problems within technical domains.

📝 Enhancement Note: The role is explicitly for a "Product Designer" focused on the ".NET Ecosystem," indicating a specialization within the broader JetBrains product suite. The emphasis on "end-to-end experiences" and "owning the design process" signifies a significant level of autonomy and responsibility. The target audience being "expert developers" with "strong habits and strong opinions" highlights the critical need for meticulous design and a deep understanding of user workflows.

📈 Primary Responsibilities

  • Lead the complete design lifecycle, from initial research and conceptualization through to final pixel-perfect delivery.

  • Develop user-centered design solutions for complex technical products, including cross-platform IDEs, extensions, and performance analysis tools.

  • Conduct and synthesize user research, including interviews and usability testing, to inform design decisions and validate concepts.

  • Create high-fidelity designs and interactive prototypes in Figma to effectively communicate design intent and facilitate testing.

  • Collaborate with cross-functional teams (Product Management, Engineering, QA, Research) to define product direction and ensure design alignment.

  • Contribute to the development and maintenance of design systems and pattern libraries to ensure ecosystem-wide consistency.

  • Present and articulate design rationale, decisions, and trade-offs to stakeholders at various levels, including leadership.

  • Translate intricate technical concepts and developer workflows into clear, intuitive, and usable interfaces.

  • Ensure a high degree of ecosystem coherence and integration across multiple products within the .NET suite.

📝 Enhancement Note: The explicit mention of "moving across products rather than specializing in one" and "holding complexity in your head and making decisions that work across contexts" points to a role requiring strong systems thinking and the ability to manage multiple, interconnected design challenges. The responsibility to "coordinate with the broader IntelliJ Platform design team" suggests a need for understanding and contributing to a larger design framework.

🎓 Skills & Qualifications

Education: While no specific degree is listed, a Bachelor's or Master's degree in Design, Human-Computer Interaction, Computer Science, or a related field is often preferred for such roles. Strong practical experience and a robust portfolio can often substitute formal education.

Experience: Estimated 5-10 years of professional product design experience, with a proven track record of delivering complex digital products. Experience specifically designing for technical or developer audiences is highly advantageous.

Required Skills:

  • Advanced Product Design Craft: Demonstrated ability to own and execute the entire design process, from research to final delivery, with meticulous attention to detail.

  • Figma Proficiency: Expert-level skills in Figma, including efficient file organization, component creation, and building functional prototypes for complex interactions.

  • Systems Thinking: Ability to conceptualize and design for interconnected products and maintain a cohesive user experience across an ecosystem.

  • User Research Acumen: Experience conducting user interviews, usability testing, and synthesizing findings into actionable design insights.

  • Technical Domain Aptitude: Willingness and ability to quickly learn and design for complex technical domains.

  • Independence and Proactivity: Demonstrated ability to drive projects forward with minimal direction and take initiative.

  • Clear Communication: Excellent verbal and written communication skills, with the ability to articulate design decisions and defend rationale to diverse audiences.

  • Basic Coding Literacy: Understanding of fundamental programming concepts, developer workflows, and the challenges faced by software engineers.

Preferred Skills:

  • Developer Background/Engineering Mindset: Prior experience as a software developer or a strong understanding of software development lifecycles and methodologies.

  • Developer Tooling Design Experience: Proven experience designing user interfaces for IDEs, code editors, performance profiling tools, or other complex technical software.

  • Deep Understanding of IDEs: Familiarity with and strong opinions on how Integrated Development Environments (IDEs) should function, backed by practical usage.

  • Design Systems Contribution: Experience in building, contributing to, or maintaining design systems and pattern libraries.

📝 Enhancement Note: The "Basic coding literacy" requirement is crucial for this role, signaling that the company values designers who understand the developer's perspective and the technical constraints they work within. This is a key differentiator for roles in the developer tools space.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

  • Showcase end-to-end product design case studies, demonstrating your ability to handle complex problems from initial research to final shipped product.

  • Highlight projects where you've demonstrated strong systems thinking, particularly in maintaining consistency across multiple products or features.

  • Include examples of user research conducted, detailing your methodology, findings, and how they influenced your design decisions.

  • Present interactive prototypes created in Figma that effectively communicate complex user flows and interactions.

  • Demonstrate your ability to translate highly technical concepts into clear and usable interfaces. Process Documentation:

  • Detail your process for conducting user research, including methods for participant recruitment, interview techniques, and synthesis of findings.

  • Explain your approach to iterative design and prototyping, including how you use feedback to refine designs.

  • Illustrate your methods for collaborating with engineering and product management teams throughout the design process.

  • Showcase your contributions to or understanding of design systems and how you apply them to ensure product consistency.

📝 Enhancement Note: Candidates should prepare to discuss their process in detail, focusing on how they tackle complexity and ensure coherence across different products. The emphasis on "owning the design process from early research through shipped pixels" means case studies should cover the entire journey, not just the visual design phase.

💵 Compensation & Benefits

Salary Range: While not explicitly stated, based on the locations (including major European tech hubs like Berlin and Madrid), experience level (Mid-Level to Senior), and company reputation (JetBrains is a well-established tech company), a competitive salary range for a Product Designer in these regions would typically fall between €60,000 - €100,000+ annually. This can vary significantly based on specific location, candidate experience, and negotiation.

Benefits:

  • Competitive Base Salary: Reflecting skills and experience.

  • Flexible Work Location: Option to work from home or office.

  • Remote Work Abroad: Flexibility to work remotely from other countries for up to 30 days per year.

  • Extra Time Off: Additional paid time off for rest and rejuvenation.

  • Medical Insurance Allowance: Financial support for medical coverage for employees and their families.

  • Learning and Development Opportunities: Access to conferences, courses, and language classes to foster professional growth.

  • Relocation Support: Assistance provided to facilitate smooth transitions for employees moving to a new location.

  • Language Classes: Opportunities to learn local languages or improve English proficiency.

  • Lunch Allowance: Daily allowance or provision for meals on workdays.

  • Mental Health Support: Access to professional mental health services.

  • Sports Benefit: Stipend for gym memberships or sports clubs.

  • Internal Events: Participation in company-wide celebrations and team-building activities.

Working Hours: Standard full-time hours, likely around 40 hours per week. The company emphasizes flexibility, suggesting that while core hours may exist, there's an allowance for managing work around personal needs, especially with remote and hybrid options.

📝 Enhancement Note: The salary estimate is based on typical market rates for experienced Product Designers in major European tech cities and considering JetBrains' position as a leading software company. The benefits package is comprehensive, with a notable emphasis on flexibility and employee well-being, including remote work abroad and mental health support.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software Development Tools, Technology, Engineering. JetBrains operates in a highly competitive space, providing essential tools for software developers worldwide, focusing on enhancing productivity and code quality.

Company Size: JetBrains is a significant player in the software development tools market. While the exact current employee count isn't provided, it's known to be a large, international organization with hundreds, if not thousands, of employees globally. This implies a structured yet dynamic work environment with established processes but also room for individual impact.

Founded: 2000. Founded by Sergey Dmitriev, Valentin Kipiatkov, and Eugene Belyaev, JetBrains has a long history of innovation in developer tools, starting with ReSharper and expanding to a vast array of IDEs and productivity tools.

Team Structure:

  • The Product Designer will join a small, embedded design team within the .NET ecosystem (currently 3 people, including the lead).

  • This team is actively building out its operational practices, including prioritization, intake systems, and research processes, offering a chance to shape how design functions.

  • Design partners closely with Product Managers, Engineers, QA, Researchers, Marketing Managers, and Technical Writers across multiple .NET products.

  • A unique aspect is sitting alongside the engineers who are also .NET developers, creating a rare and valuable direct feedback loop between designers and their user base. Methodology:

  • Data-Driven Design: While not explicitly stated for design, JetBrains as a whole is known for its analytical approach, and this role will likely involve using user data and research to drive decisions.

  • Iterative Development: The emphasis on "shipping work that developers use every single day" and "owning the design process from early research through shipped pixels" implies an iterative design and development methodology.

  • Collaboration and Partnership: The role emphasizes close partnership with PMs and engineers, suggesting a collaborative approach to problem-solving and product development.

  • Focus on Developer Experience (DX): The core mission is to improve the productivity and experience of developers, indicating a deep focus on understanding and optimizing their workflows.

Company Website: https://www.jetbrains.com/

📝 Enhancement Note: The culture at JetBrains appears to be one that deeply respects its user base (developers) and values the expertise of its employees. The opportunity to "build the practice" within the .NET design team is a significant draw for candidates who want to influence processes and contribute to the growth of design within the organization. The close proximity to engineers who are also users is a unique and powerful aspect of the work environment.

📈 Career & Growth Analysis

Operations Career Level: This role is positioned as a Product Designer with significant ownership and responsibility within a critical product ecosystem. It aligns with a mid-to-senior level designer who can operate independently, manage complex projects, and contribute strategically. The opportunity to "own end-to-end experiences" and "move across products" suggests a role with broad scope and potential for significant impact.

Reporting Structure: The designer will report to a Design Lead within the .NET ecosystem and will work closely with Product Managers and Engineering Leads for the various .NET products. The small size of the immediate design team implies direct access to leadership and collaborative decision-making.

Operations Impact: The designer's impact is directly tied to the usability, efficiency, and adoption of JetBrains' flagship .NET development tools. By improving the user experience for millions of developers, the role contributes significantly to JetBrains' market position and revenue. The ability to influence product strategy means designers are integral to the business's success.

Growth Opportunities:

  • Skill Specialization: Deepen expertise in designing for developer tools and complex technical domains, potentially becoming a subject matter expert within the .NET ecosystem or the broader JetBrains Platform.

  • Leadership and Mentorship: As the design team grows, there will be opportunities to mentor junior designers, lead design initiatives, or take on team lead responsibilities.

  • Cross-Product Influence: Gain exposure to and contribute designs across a wider range of JetBrains products, potentially influencing the overall IntelliJ Platform design language.

  • Process Improvement: Actively participate in and lead the development of design processes, research methodologies, and the design system, contributing to the maturation of the design function.

  • Strategic Input: Continue to have a seat at the table for product strategy discussions, influencing roadmap priorities and product direction.

📝 Enhancement Note: The role offers a clear path for growth beyond individual contribution, with opportunities to influence team processes, product strategy, and potentially lead future design initiatives. The "build the practice" aspect is a strong indicator of growth potential in shaping organizational design maturity.

🌐 Work Environment

Office Type: JetBrains offers a hybrid work model, allowing employees to work from home or from designated office locations. The company emphasizes flexibility, suggesting that the specific setup will depend on team needs and individual preferences, within defined parameters.

Office Location(s): The role is available in multiple international locations, including Belgrade (Serbia), Berlin (Germany), Limassol (Cyprus), Madrid (Spain), Munich (Germany), Prague (Czech Republic), Warsaw (Poland), and Yerevan (Armenia). Remote work within Germany is also an option. This wide geographical distribution supports a global talent pool and accommodates diverse employee needs.

Workspace Context:

  • Collaborative Environment: Despite remote and hybrid options, the culture emphasizes close partnership with Product Managers and Engineers. This suggests a highly collaborative digital workspace, utilizing tools for seamless communication and co-creation.

  • Developer-Centric Tools: Designers will work within an environment where the primary users are developers. This means access to and familiarity with the tools developers use daily will be inherent in the workspace.

  • Direct User Feedback Loop: A significant aspect is sitting alongside the engineers who are also .NET developers. This proximity fosters a unique, direct feedback loop, allowing for rapid iteration and a deep understanding of user pain points.

Work Schedule: While a standard 40-hour work week is implied for full-time employment, JetBrains promotes flexibility. This allows designers to manage their schedules to accommodate deep work sessions, collaborative meetings, and personal needs, particularly beneficial for complex problem-solving and iterative design processes.

📝 Enhancement Note: The blend of remote flexibility and embedded team structure, coupled with direct access to developer users, creates a unique and potentially highly productive work environment. The international presence means candidates can choose a location that suits them best, while still being part of a cohesive global team.

📄 Application & Portfolio Review Process

Interview Process:

  1. Application Submission: Submit CV, portfolio, and a brief cover letter detailing interest in the role.

  2. Portfolio Review: Initial screening will likely focus on the quality and relevance of the portfolio, assessing design craft, problem-solving approach, and experience with complex domains.

  3. Initial Interview: A conversation with a hiring manager or design lead to discuss experience, motivations, and initial fit. This may include a high-level overview of portfolio projects.

  4. Design Challenge/Case Study: Candidates may be given a take-home design exercise or asked to present a detailed case study from their portfolio. This will assess their thinking process, research capabilities, and design execution.

  5. Team/Stakeholder Interviews: Interviews with engineers, product managers, and potentially other designers to evaluate collaboration skills, technical understanding, and cultural fit.

  6. Final Interview: A concluding interview, possibly with senior leadership, to finalize the decision and discuss terms.

Portfolio Review Tips:

  • Showcase End-to-End Process: For each case study, clearly articulate the problem, your role, the research conducted, the design process, your rationale, and the outcome (including metrics if available).

  • Highlight Systems Thinking: Explicitly demonstrate how you approached consistency and integration across multiple features or products. Use diagrams or explanations to show how your designs fit into a larger ecosystem.

  • Emphasize Developer Focus: If possible, include projects where you designed for technical users or complex domains. Explain how you understood and addressed the specific needs and workflows of that audience.

  • Figma Proficiency: Ensure prototypes are well-built and clearly demonstrate complex interactions. Your file organization and design system approach within Figma can also be a talking point.

  • Quantify Impact: Whenever possible, include quantifiable results or impact metrics related to your designs (e.g., increased user engagement, reduced task completion time, improved conversion rates).

Challenge Preparation:

  • Understand the .NET Ecosystem: Research JetBrains' .NET products (Rider, ReSharper, dotTrace, dotMemory) and their primary competitors (e.g., Visual Studio). Understand the target user (developers) and their common pain points.

  • Prepare a Deep Dive Case Study: Select a portfolio project that best showcases your ability to handle complexity, systems thinking, and deliver end-to-end design. Be ready to discuss every decision and trade-off.

  • Articulate Your "Why": Be prepared to clearly explain why you are interested in designing for developers and specifically for JetBrains' .NET products. Connect your passion for design with the company's mission.

  • Think About Trade-offs: Be ready to discuss design decisions where you had to balance user needs, technical constraints, and business goals.

📝 Enhancement Note: The application process emphasizes evaluating how candidates "think" and "approach work," prioritizing the portfolio and cover letter over just checking off boxes. This suggests a focus on understanding the candidate's problem-solving methodology and design philosophy.

🛠 Tools & Technology Stack

Primary Tools:

  • Figma: Explicitly mentioned as the required design tool for building organized files and prototypes. Proficiency is essential.

  • Design Systems Tools: While not named, candidates will likely work with or contribute to design system documentation and libraries, potentially using tools like Zeroheight or internal documentation platforms.

Analytics & Reporting:

  • User Research Tools: Likely includes tools for conducting user interviews (e.g., Zoom, Google Meet), usability testing (e.g., UserTesting.com, Maze), and potentially analytics platforms (e.g., Amplitude, Mixpanel) to understand user behavior post-launch.

  • Data Analysis: While not explicitly a design tool, understanding how to interpret usage data and analytics to inform design decisions is key.

CRM & Automation:

  • Project Management & Collaboration: Tools like Jira, Confluence, Slack, and Asana are likely used for team collaboration, task tracking, and communication.

  • Version Control (Conceptual): While designers don't typically use Git directly, understanding concepts like versioning and branching can be beneficial given the technical audience.

📝 Enhancement Note: The primary tool requirement is Figma. However, a candidate's familiarity with the broader ecosystem of design and research tools, and their ability to integrate design insights with data analytics, will be highly valued.

👥 Team Culture & Values

Operations Values:

  • User-Centricity: A deep commitment to understanding and serving the needs of expert developers, recognizing them as a demanding but rewarding audience.

  • Craftsmanship and Detail: A dedication to high-quality design execution, where meticulous attention to detail is valued and noticed by the expert user base.

  • Innovation and Problem-Solving: A drive to tackle genuinely hard problems within complex technical domains, pushing the boundaries of what's possible in developer tools.

  • Collaboration and Partnership: A belief in working closely with product managers, engineers, and researchers to achieve shared goals, treating design as a strategic input.

  • Autonomy and Ownership: Empowering individuals to take ownership of their work, drive projects forward, and have accountability for outcomes.

  • Continuous Improvement: A culture of building and refining practices, processes, and the design system to enhance team efficiency and product quality.

Collaboration Style:

  • Integrated Design: Designers are embedded within product teams and sit alongside engineers, fostering close, day-to-day collaboration.

  • Cross-Functional Partnership: Active collaboration with Product Management, Engineering, QA, Research, Marketing, and Technical Writers to ensure a holistic product approach.

  • Open Communication: Emphasis on clear communication, constructive feedback, and the ability to defend design decisions while being open to pushback.

  • Shared Learning: The team is actively building its practices, suggesting a culture where knowledge sharing and collective learning are encouraged.

📝 Enhancement Note: The culture seems to revolve around deep respect for the developer user, a commitment to quality and technical excellence, and a collaborative environment where design is a critical, integrated function rather than an isolated department.

⚡ Challenges & Growth Opportunities

Challenges:

  • Designing for Experts: Creating intuitive and effective experiences for highly skilled, opinionated developers who have established workflows and high expectations.

  • Navigating Technical Complexity: Translating intricate, often abstract, technical concepts (e.g., performance profiling, code analysis) into user-friendly interfaces.

  • Maintaining Ecosystem Coherence: Ensuring a consistent and integrated user experience across a suite of complex, interconnected products (IDEs, extensions, profilers).

  • Balancing Multiple Products: Holding the design needs and context of several distinct but related products in mind simultaneously.

  • Building Design Practices: Contributing to the establishment and refinement of design processes, research methodologies, and design systems within a growing team.

Learning & Development Opportunities:

  • Deep Dive into Developer Workflows: Gain unparalleled insight into the daily lives and challenges of millions of software developers.

  • Mastering Complex Domain Design: Develop expertise in designing for sophisticated technical products, a valuable niche skill.

  • Influence on Product Strategy: Contribute directly to the strategic direction of leading developer tools.

  • Shaping Design Operations: Play a key role in defining how design operates within the .NET organization at JetBrains.

  • Access to Industry Events and Training: Leverage the company's support for conferences, courses, and language classes to enhance skills.

  • Mentorship from Design Lead: Learn from experienced design leadership within a growing team.

📝 Enhancement Note: The challenges presented are inherent to designing for expert users and complex software. The growth opportunities are substantial, offering deep domain expertise, strategic influence, and the chance to shape organizational design maturity.

💡 Interview Preparation

Strategy Questions:

  • "Describe a time you had to design for a highly technical or expert user audience. What were the unique challenges, and how did you address them?" (Focus on your understanding of developer psychology, research methods for experts, and how you handled their strong opinions.)

  • "Walk us through a complex project from your portfolio where you were responsible for the end-to-end design process. What was the problem, your process, your role, and the outcome?" (Be ready to detail every step, from research to shipped pixels, and defend your decisions.)

  • "How do you approach designing for an ecosystem of products versus a single product? Provide an example." (Highlight your systems thinking skills, ability to maintain consistency, and understanding of user flow across multiple touchpoints.)

  • "Imagine you're designing a new AI-assisted feature for Rider. What research would you conduct, and how would you ensure it integrates seamlessly without disrupting existing developer workflows?" (Demonstrate your approach to new technologies, user context, and integration challenges.) Company & Culture Questions:

  • "Why JetBrains, and specifically why this role designing for the .NET ecosystem?" (Connect your passion for design, developer tools, and JetBrains' mission.)

  • "How do you see design contributing strategically to a product like Rider or ReSharper?" (Show your understanding of design's role beyond just UI aesthetics, focusing on user experience and product success.)

  • "Describe your ideal collaboration with engineers and product managers. How do you handle disagreements on design decisions?" (Emphasize your partnership approach and constructive communication skills.) Portfolio Presentation Strategy:

  • Structure for Impact: Organize your presentation logically: Problem -> Your Role -> Process (Research, Ideation, Design, Testing) -> Solution -> Outcome/Impact.

  • Tell a Story: Frame each case study as a narrative of problem-solving. Explain the stakes, your journey, and the resolution.

  • Focus on "Why": For every decision, be ready to explain the rationale behind it. Why this approach? Why this solution? What were the trade-offs?

  • Show, Don't Just Tell: Use visuals effectively. Show wireframes, mockups, prototypes, and user flows. If discussing research, present key findings or quotes.

  • Quantify When Possible: If you have metrics on user engagement, task completion, satisfaction, or business impact, present them clearly.

  • Be Prepared for Deep Dives: Anticipate questions about specific design choices, technical constraints you considered, or alternative solutions you explored.

📝 Enhancement Note: The interview process is designed to assess not just design skills but also strategic thinking, problem-solving capabilities, and the ability to integrate into a technically sophisticated environment. A strong portfolio that clearly articulates process and impact is paramount.

📌 Application Steps

To apply for this Product Designer position:

  • Submit your portfolio, CV, and a brief cover letter explaining your interest in the role through the provided application link.

  • Portfolio Customization: Tailor your portfolio to highlight projects demonstrating end-to-end design process, systems thinking, and experience with complex or technical domains. Ensure your Figma proficiency is evident through interactive prototypes.

  • Resume Optimization: Clearly articulate your experience in product design, user research, and any relevant technical background or developer tool experience. Use keywords like "Product Design," "UX Design," "Figma," "User Research," "Systems Thinking," and ".NET ecosystem" where applicable.

  • Interview Preparation: Practice articulating your design process, rationale, and outcomes for your portfolio projects. Prepare to discuss how you approach designing for expert users and complex technical challenges.

  • Company Research: Familiarize yourself with JetBrains, its mission, its .NET products (Rider, ReSharper), and its commitment to developer productivity. Understand the company's values and culture.

⚠️ Important Notice: This enhanced job description includes AI-generated insights and operations industry-standard assumptions. All details should be verified directly with the hiring organization before making application decisions.

Application Requirements

Requires strong product design craft, Figma fluency, and the ability to navigate high technical complexity. Basic coding literacy and experience with systems thinking for ecosystem coherence are essential.