Senior Product Designer, Policies

📍 Job Overview

Job Title: Senior Product Designer, Policies

Company: GitLab

Location: Remote (Americas, Ireland, Netherlands)

Job Type: Full-Time

Category: Product Design / Security & Compliance Operations

Date Posted: 2026-02-24T19:02:59

Experience Level: 5-10 Years

Remote Status: Fully Remote

🚀 Role Summary

• Lead the end-to-end design of security policy configuration and compliance workflows within GitLab's DevSecOps platform.

• Translate complex governance and regulatory requirements into intuitive, scalable, and user-centered experiences for AppSec professionals, Compliance Managers, and Developers.

• Drive high-quality craft and systems thinking to ensure policy experiences integrate seamlessly with existing security tools and adhere to the Pajamas Design System.

• Collaborate extensively with Product Management, Engineering, and cross-functional security teams to define priorities, scope Minimum Viable Changes (MVCs), and maintain design integrity throughout the development lifecycle.

📝 Enhancement Note: Given the focus on "Policies" within "Security & Compliance," this role sits at the intersection of Product Design and specialized Operations, specifically within the security governance domain. The responsibilities indicate a need for deep understanding of how policies impact development workflows (SDLC) and operational security practices. The seniority implies leadership in design strategy and execution for this critical area.

📈 Primary Responsibilities

• Own Design for Security Policy & Compliance: Lead the complete design lifecycle for policy configuration, compliance reporting, and Software Development Life Cycle (SDLC) governance features, ensuring usable solutions that address immediate user needs while maintaining long-term quality and consistency.

• Translate Technical Complexity: Partner with security experts to deeply understand policy configuration, compliance frameworks, and enforcement logic, then design accessible experiences for diverse user types, from detailed rule setters to developers needing to understand blockers.

• Cross-Functional Partnership: Collaborate closely with Product Managers, Engineering Managers, and multiple security product groups to shape priorities, scope MVCs, and ensure design quality. Foster strong relationships with adjacent teams (e.g., vulnerability management, scanners, CI/CD) to align on cohesive experiences.

• Deliver High Craft Quality: Demonstrate exceptional interaction design, visual design skills, and meticulous attention to detail. Actively participate in design reviews, provide constructive feedback, and uphold rigorous standards in personal work.

• Contribute to Design System: Actively contribute to the Pajamas Design System by identifying reusable patterns, proposing new components, and ensuring your group's work adheres to system standards, balancing system leverage with the need for unique solutions.

• Ground Work in Research: Conduct usability studies, competitor evaluations, and formative research. Collaborate with UX Research on problem validation and integrate insights to meet user and business needs, engaging with users and the GitLab community for long-term solutions.

• Communicate Designs Clearly: Create comprehensive documentation including wireframes, prototypes, user flows, and high-fidelity designs. Effectively present work to stakeholders, articulate rationale, build alignment, and practice asynchronous communication for clarity.

• Practice Effective Iteration: Break down designs for release cadence, review user-facing merge requests, and guide others in adopting effective iteration practices. Mitigate UX risks with MVCs and prioritize usability issues.

📝 Enhancement Note: The responsibilities highlight a need for strategic thinking beyond just UI design. The emphasis on "translating technical complexity," "systems thinking," and "contributing to the design system" points to a role that shapes the product's operational capabilities and user experience at a fundamental level. The focus on MVCs and iteration suggests an agile product development environment where designers must balance immediate needs with long-term vision.

🎓 Skills & Qualifications

Education: While no specific degree is listed, a strong portfolio and demonstrated experience are prioritized. A background in HCI, Design, Computer Science, or a related field is often beneficial.

Experience: Minimum of 5-10 years of experience in product design, with a strong emphasis on enterprise-grade software, particularly in security, compliance, or DevSecOps domains.

Required Skills:

• Demonstrated experience designing enterprise-grade security, compliance, or DevSecOps products.

• Strong portfolio showcasing end-to-end product design work, from problem framing through shipped solutions.

• Proven experience designing holistic workflows and translating complex technical concepts into clear, user-centered experiences.

• Excellent collaboration skills and experience fostering partnerships across multiple product teams and stakeholders.

• Systems thinking and experience contributing to or working with design systems.

• Experience conducting user research (e.g., usability studies, competitor evaluations) and using insights to validate design decisions.

• Strong visual design skills with the ability to balance system consistency with custom solutions.

• Experience working in remote, distributed teams.

• Proficiency with Figma and prototyping tools for creating wireframes, user flows, and high-fidelity mockups.

Preferred Skills:

• Familiarity with GitLab's product and platform.

• Experience with policy configuration interfaces or governance tools.

• Understanding of regulatory compliance frameworks (e.g., SOC 2, ISO 27001, GDPR).

• Experience with CI/CD pipelines, vulnerability scanning, or application security concepts.

• Contribution to open-source design systems or communities.

📝 Enhancement Note: The "5-10 years" experience level, combined with the "Senior" title and responsibilities like "owning design," "translating technical complexity," and "contributing to the design system," suggests this role requires not just execution but also significant strategic input and mentorship capabilities within the design team. The emphasis on enterprise security and compliance indicates a need for a deep understanding of B2B SaaS product design challenges.

📊 Process & Systems Portfolio Requirements

Portfolio Essentials:

• Demonstrate end-to-end product design ownership, from initial problem identification and user research through to the final shipped solution.

• Showcase case studies that highlight complex technical concepts translated into clear, intuitive user experiences, focusing on policy configuration and governance.

• Include examples of systems thinking, illustrating how designs integrate within a larger product ecosystem or design system.

• Provide evidence of collaboration with Product Management and Engineering, demonstrating your role in shaping product direction and ensuring design intent through development.

Process Documentation:

• Detail your process for conducting user research, including methods used, participant recruitment, and how insights were synthesized and applied.

• Document your approach to designing complex workflows, emphasizing how you ensured usability, scalability, and adherence to established design patterns and systems.

• Illustrate your contribution to or utilization of design systems, showcasing how you maintained consistency and leveraged existing components effectively.

• Present examples of how you iterated on designs based on feedback, research, or changing requirements, including the rationale behind those iterations.

📝 Enhancement Note: For a Senior Product Designer role, especially in a complex domain like security policies, the portfolio is crucial. It needs to go beyond static mockups to demonstrate a deep understanding of the design process, problem-solving capabilities, and the ability to handle intricate, enterprise-level requirements. The emphasis on systems thinking and design system contribution is key for a company like GitLab.

💵 Compensation & Benefits

Salary Range: The listed range for US residents is $100,000 - $150,000 USD per year.

Note: This range is specific to the United States. GitLab operates globally, and compensation will be adjusted based on local market data, cost of living, and the candidate's experience level, equity, and alignment with internal benchmarks. For candidates in Ireland and the Netherlands, local salary benchmarks for senior product design roles in enterprise SaaS companies will apply and will likely differ from the US range.

Benefits:

• Comprehensive benefits to support health, finances, and well-being.

• Flexible Paid Time Off (PTO) to promote work-life balance.

• Access to Team Member Resource Groups (TMRGs) for community and support.

• Equity Compensation and Employee Stock Purchase Plan (ESPP) for shared ownership.

• Growth and Development Fund to support continuous learning and skill enhancement.

• Generous Parental Leave to support new parents.

• Home office support to ensure a productive remote work environment.

Working Hours: Approximately 40 hours per week, typical for a full-time role. GitLab emphasizes asynchronous communication, allowing for flexibility within global time zones, but core collaboration hours may be expected depending on team needs.

📝 Enhancement Note: The salary range is provided for the US only. For candidates in Ireland and the Netherlands, a localized salary research would be necessary. Benchmarks for Senior Product Designers in enterprise SaaS companies in Dublin and Amsterdam typically fall within €70,000 - €100,000+ and €75,000 - €110,000+ respectively, depending on experience and specific company compensation bands. GitLab's global compensation philosophy aims for competitive pay across all regions.

🎯 Team & Company Context

🏢 Company Culture

Industry: Software Development Tools, DevSecOps Platform, AI-powered Orchestration. GitLab operates in the highly competitive and rapidly evolving SaaS market, with a strong focus on security and developer productivity.

Company Size: GitLab is a large, established, all-remote company, with a significant number of employees globally. This size implies robust processes, a wide array of tools, and ample opportunities for specialization and cross-functional interaction.

Founded: GitLab has been an all-remote company since its inception, emphasizing its commitment to flexible work and distributed collaboration. This long-standing remote culture means their processes and tools are optimized for a globally distributed workforce.

Team Structure:

• The Senior Product Designer will likely be part of a broader Product Design team, potentially specializing within a Security & Compliance product group.

• Reporting structure will be to a Design Manager or Director, with close alignment and collaboration with Product Managers and Engineering Managers for the specific product area.

Methodology:

• GitLab champions a data-driven approach, utilizing AI as a core productivity multiplier and encouraging all team members to incorporate it into their workflows.

• Workflow planning and optimization are driven by principles of efficiency, iteration, and continuous improvement, aligned with their DevSecOps mission.

• Automation and efficiency are key themes, reflected in both their product offerings and internal operations. Their handbook-driven, transparent culture supports continuous knowledge exchange.

Company Website: https://about.gitlab.com/

📝 Enhancement Note: GitLab's "all-remote" culture is a defining characteristic. This means the candidate must be comfortable with asynchronous communication, self-management, and a highly transparent, handbook-first approach to work. The emphasis on AI integration is also a significant cultural and operational aspect.

📈 Career & Growth Analysis

Operations Career Level: This is a Senior Product Designer role. In the context of operations and product development, "Senior" implies a high degree of autonomy, ownership, and the ability to influence design strategy and execution for a significant product area. It suggests a capacity to mentor junior designers and contribute to the overall design discipline within the company.

Reporting Structure: The designer will report into a design leadership structure (likely a Design Manager or Director) and will work closely with Product Management and Engineering leadership for their specific domain. This structure facilitates strategic alignment and efficient execution.

Operations Impact: The Senior Product Designer's work directly impacts the operational security posture of over 100,000 organizations using GitLab. By designing intuitive policy and compliance workflows, they enable customers to meet regulatory requirements, reduce risk, and improve their overall DevSecOps efficiency, directly contributing to customer success and GitLab's value proposition.

Growth Opportunities:

• Specialization: Deepen expertise in security, compliance, and governance design within the DevSecOps space, becoming a subject matter expert.

• Leadership: Progress to Staff or Principal Designer roles, taking on larger product areas, strategic initiatives, or leading design efforts for entire product groups. Opportunity to mentor and guide other designers.

• Cross-Functional Influence: Expand influence across product and engineering teams, contributing more broadly to product strategy and operational excellence.

• Design System Evolution: Play a key role in evolving and scaling the Pajamas Design System.

• Industry Contribution: Contribute to industry best practices through thought leadership, speaking engagements, or open-source contributions.

📝 Enhancement Note: The growth opportunities for a Senior Product Designer at GitLab are substantial, given its scale and focus on innovation. The emphasis on "AI as a core productivity multiplier" suggests potential future growth in designing AI-assisted features within the policy and compliance space.

🌐 Work Environment

Office Type: GitLab is a fully remote company. There are no physical offices for employees to commute to. The work environment is entirely virtual.

Office Location(s): Remote work is supported across diverse geographies, including the Americas, Ireland, and the Netherlands. Specific country hiring guidelines may apply, ensuring compliance with local labor laws.

Workspace Context:

• The virtual workspace is highly collaborative, utilizing tools like Slack, Zoom, and GitLab's own platform for communication and project management. Emphasis is placed on asynchronous communication to accommodate global time zones.

• Access to a wide range of digital tools and technologies is provided to support design, development, and collaboration. This includes Figma, prototyping tools, and internal GitLab tools.

• Opportunities for interaction with the operations and product teams are frequent through scheduled meetings, design reviews, and collaborative sessions on the GitLab platform itself.

Work Schedule: While a standard 40-hour work week is typical, GitLab's remote, asynchronous culture offers significant flexibility. Employees are encouraged to manage their schedules to optimize productivity and work-life balance, within the constraints of team collaboration needs and global time zone coverage.

📝 Enhancement Note: The "all-remote" nature of GitLab is a critical aspect of its work environment. Candidates should be highly self-motivated, disciplined, and adept at virtual collaboration and asynchronous communication.

📄 Application & Portfolio Review Process

Interview Process:

• <strong>Application Submission:</strong> Submit resume and portfolio through the GitLab careers portal.

• <strong>Recruiter Screen:</strong> Initial conversation to assess basic qualifications, cultural fit, and interest.

• <strong>Hiring Manager Interview:</strong> Deeper dive into experience, skills, and alignment with the role's responsibilities. Portfolio review will likely be a key component.

• <strong>Design Portfolio Presentation:</strong> A dedicated session where the candidate presents 1-2 case studies from their portfolio, demonstrating their design process, problem-solving abilities, and impact. This is often followed by Q&A.

• <strong>Cross-Functional Interviews:</strong> Interviews with Product Management and Engineering counterparts to assess collaboration skills, systems thinking, and ability to work within a team.

• <strong>Values Interview:</strong> Assessment of alignment with GitLab's company values.

Portfolio Review Tips:

• <strong>Select Relevant Case Studies:</strong> Prioritize projects that showcase experience with complex enterprise software, security, compliance, or governance domains. Highlight your end-to-end design process.

• <strong>Structure for Clarity:</strong> For each case study, clearly articulate the problem, your role and responsibilities, the design process (research, ideation, iteration), the solutions, and the measurable impact or outcomes.

• <strong>Show Systems Thinking:</strong> Demonstrate how your designs integrate with existing products or systems, and how you adhered to or contributed to a design system.

• <strong>Highlight Collaboration:</strong> Explain how you partnered with Product Managers, Engineers, and Researchers, and how you navigated differing opinions or technical constraints.

• <strong>Quantify Impact:</strong> Where possible, present data or metrics that demonstrate the success of your designs (e.g., improved user satisfaction, increased feature adoption, reduced error rates).

Challenge Preparation:

• While not explicitly stated, be prepared for potential design exercises or hypothetical problem-solving scenarios during interviews.

• Familiarize yourself with GitLab's product, particularly its security and compliance features, to understand the context and potential design challenges.

• Understand GitLab's values and how they translate into design practice.

📝 Enhancement Note: The portfolio presentation is a critical step. Candidates should prepare to articulate their design thinking, problem-solving methodologies, and the impact of their work in a clear, concise, and compelling manner. Practicing asynchronous communication of design concepts is also advisable.

🛠 Tools & Technology Stack

Primary Tools:

• <strong>Design & Prototyping:</strong> Figma (primary tool), potentially other prototyping tools for specific needs.

• <strong>Collaboration:</strong> Slack for real-time communication, Zoom for video conferencing.

• <strong>Project Management & Documentation:</strong> GitLab's own platform for issue tracking, merge requests, and documentation. Confluence or similar for broader knowledge base.

Analytics & Reporting:

• Internal GitLab metrics and analytics platforms to understand user behavior and feature adoption.

CRM & Automation:

• While not a direct tool for designers, understanding the role of CRM (e.g., Salesforce) and automation platforms in the B2B SaaS context is beneficial.

• Familiarity with how design decisions impact downstream operational processes and automation within the DevSecOps lifecycle.

📝 Enhancement Note: Proficiency in Figma is explicitly mentioned as a requirement. Candidates should be comfortable working within a mature design system (Pajamas) and collaborating in a fully digital, asynchronous environment.

👥 Team Culture & Values

Operations Values: GitLab's core values are Collaboration, Results, Efficiency, Diversity, Inclusion & Belonging, Iteration, and Transparency.

• <strong>Collaboration:</strong> Working effectively across distributed teams, valuing diverse perspectives.

• <strong>Results:</strong> Focusing on delivering tangible outcomes and impact, especially in driving customer success and product adoption.

• <strong>Efficiency:</strong> Embracing AI and automation to optimize workflows and productivity, both internally and for customers.

• <strong>Diversity, Inclusion & Belonging:</strong> Creating an environment where everyone feels valued and can contribute their best work.

• <strong>Iteration:</strong> Embracing a continuous improvement mindset, breaking down work into manageable parts, and learning from feedback.

Collaboration Style:

• Highly collaborative, with a strong emphasis on asynchronous communication and documentation via their handbook.

• Cross-functional teams work closely together, with designers embedded within product groups alongside PMs and Engineers.

• Feedback is encouraged from all levels and functions, fostering a culture of continuous learning and improvement.

• Knowledge sharing is paramount, with an expectation that team members contribute to and leverage the company handbook.

📝 Enhancement Note: Candidates must demonstrate an alignment with GitLab's unique values and remote-first, handbook-driven culture. The emphasis on transparency and iteration is crucial for success in this environment.

⚡ Challenges & Growth Opportunities

Challenges:

• <strong>Complexity of Security Policies:</strong> Designing intuitive interfaces for highly technical and complex security policy configurations requires deep domain understanding and user empathy.

• <strong>Balancing System Consistency and Customization:</strong> Ensuring policy features feel native to GitLab while potentially requiring unique affordances for specialized functions can be challenging.

• <strong>Global Time Zones:</strong> Effective asynchronous communication and collaboration across widely dispersed teams require strong organizational and communication skills.

Learning & Development Opportunities:

• <strong>Deep Domain Expertise:</strong> Gaining in-depth knowledge of DevSecOps, security governance, and compliance frameworks.

• <strong>Design Leadership:</strong> Developing mentorship and strategic design leadership skills within a large, remote organization.

• <strong>AI Integration in Design:</strong> Exploring and applying AI tools to enhance design workflows and product features.

• <strong>Contribution to Design Systems:</strong> Influencing and contributing to a widely used design system (Pajamas).

• <strong>Industry Engagement:</strong> Learning from and contributing to the broader product design and DevSecOps communities.

📝 Enhancement Note: The challenges are inherent to the role's domain and the company's operational model. Embracing these challenges as opportunities for growth and learning is key for success.

💡 Interview Preparation

Strategy Questions:

• Expect questions about how you approach designing for complex, enterprise-level workflows, particularly in regulated or security-sensitive domains.

• Be prepared to discuss how you translate technical requirements and user needs into actionable design solutions, referencing specific examples from your portfolio.

• Articulate your understanding of systems thinking and how you ensure consistency and scalability in your designs, especially in relation to design systems.

Company & Culture Questions:

• Research GitLab's mission, values, and product extensively. Understand their DevSecOps platform and how security policies fit into it.

• Be ready to discuss your experience working in a remote, asynchronous environment and how you ensure effective collaboration and communication.

• Prepare to talk about how you embody GitLab's values (Collaboration, Results, Efficiency, etc.) in your work.

Portfolio Presentation Strategy:

• <strong>Storytelling:</strong> Frame your case studies as narratives—problem, your role, your process, solution, and outcome.

• <strong>Focus on Impact:</strong> Quantify results whenever possible. If direct metrics aren't available, articulate the intended impact and how you would measure success.

• <strong>Show, Don't Just Tell:</strong> Use visuals (wireframes, mockups, prototypes) effectively to illustrate your design decisions and the user experience you created.

• <strong>Explain Your 'Why':</strong> Be prepared to thoroughly explain the rationale behind your design decisions, demonstrating critical thinking and user-centered principles.

• <strong>Address Collaboration:</strong> Explicitly mention how you worked with cross-functional teams (PM, Eng, Research) throughout the project.

📝 Enhancement Note: The interview process will likely focus heavily on your design process, problem-solving capabilities, collaboration skills, and cultural fit with GitLab's unique remote and transparency-focused environment.

📌 Application Steps

To apply for this Senior Product Designer position:

• Submit your application through the GitLab careers portal, ensuring your resume and portfolio are up-to-date and accurately reflect your experience.

• <strong>Tailor Your Portfolio:</strong> Select 1-2 case studies that best demonstrate your experience with complex enterprise software, security/compliance design, and end-to-end product ownership. Emphasize your process, collaboration, and impact.

• <strong>Optimize Your Resume:</strong> Highlight keywords from the job description, such as "Product Design," "Security Policies," "Compliance Workflows," "DevSecOps," "Design Systems," "Figma," and "Remote." Quantify achievements where possible.

• <strong>Prepare for the Portfolio Presentation:</strong> Practice articulating your design thinking, process, and the outcomes of your work. Be ready to discuss your rationale for design decisions and how you collaborated with teams.

• <strong>Research GitLab:</strong> Thoroughly understand GitLab's product, mission, values, and their remote-first culture. Be prepared to discuss how you align with these aspects.

⚠️ 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.

---