Solutions Architect, Public Sector - East
. Then we have sections. We need headings: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to appropriate headings.
We have "An Overview Of This Role" -> could be "About the role". Use About the role
then paragraph(s) describing role.
Then "What You'll Do" -> Responsibilities. Use Responsibilities
then - items.
Then "What You'll Bring" -> Requirements/Qualifications/Skills. Could combine into Requirements. Use
Requirements
then list.
Then "About The Team" -> maybe "Team" but not in list; we could use About the Team
but not in allowed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those. So we can use About the Team as heading.
Then "How GitLab Supports Full-Time Employees Benefits" -> Benefits. Use Benefits
then list.
We must not include Pay or Schedule sections because not present.
We must not include filler like "commensurate with experience". Not present.
We need to remove boilerplate: The initial paragraph about GitLab is maybe okay. Also the sentence "Fortune 500® is a registered trademark..." is legal boilerplate; should remove. Also "Claim based on GitLab data..." etc. Remove.
Also remove "An Overview Of This Role" heading? We'll convert to About the role
and keep content.
We need to ensure we don't duplicate lines.
Let's extract content.
Intro paragraph before "An Overview Of This Role":
"GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster. The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software."
We keep that as
.
Then after that, "An Overview Of This Role As a Public Sector Solutions Architect, you'll be a trusted advisor to U.S. government customers, helping them understand how GitLab's Enterprise Edition and DevSecOps platform can address real business and mission outcomes. You'll own the technical evaluation and validation stages of the sales cycle, guide customers through proofs of concept and value, and connect GitLab's modern software development, operations, and cloud capabilities to measurable value. In this role, you'll work closely with sales and cross-functional GitLab teams, provide technical guidance from first conversation through successful deployment, and act as a customer advocate back into Product, Sales, and Marketing."
We'll put that as paragraph(s) under About the role.
Then "What You'll Do" bullet list:
- Engage with public sector customers, both onsite and remotely, to provide technical expertise and guidance throughout the pre-sales process, including tailored demos, technical presentations, and hands-on workshops.
- Collaborate with the sales team to shape and execute account strategies that drive GitLab adoption within government environments.
- Own the technical evaluation process, including proof of concept (POC) and proof of value (POV) design and delivery, tender and audit support, and technical input into proposals.
- Lead the creation of Customer Success Plans that capture technical success criteria and handoff details from the pre-sales process, ensuring a smooth path to deployment and adoption.
- Build and deepen relationships with technical and business stakeholders so they become advocates for GitLab within their organizations.
- Serve as the customer advocate internally by channeling feedback and insights to Product, Sales, Marketing, and other GitLab teams to influence roadmap and messaging.
- Maintain and expand your expertise in GitLab and related technologies, including modern software development, operations, and cloud practices, and create reusable examples and assets for customers and partners.
- Run Value Stream Assessments to identify opportunities for customers to improve their software delivery with GitLab.
We'll put each as
- .
Then "What You'll Bring":
- Background in technical pre-sales, consulting, or information technology roles, ideally with U.S. public sector or federal customers, where you guided customers through evaluations and solution design
- Hands-on experience using GitLab and familiarity with modern software development and operations practices, such as CI/CD, DevSecOps, and automation
- Experience with cloud computing platforms and related technologies in regulated or security-conscious environments.
- Ability to connect technical solutions to measurable business or mission outcomes and to advise senior stakeholders on tradeoffs and options.
- Strong, confident communication and relationship-building skills, including leading customer meetings, demos, and value-focused conversations in close partnership with sales and cross-functional teams
- Openness to learning, seeking feedback, and building new skills, including familiarity with GitLab's Solutions Architect handbook and related resources.
We'll put as list under Requirements.
Then "About The Team":
"The Public Sector Solutions Architect role is part of GitLab's Solutions Architect team, a group of trusted technical advisors who help government customers understand, evaluate, and adopt the GitLab DevSecOps platform. The team is distributed and collaborates asynchronously across time zones using GitLab and our handbook-first practices to share knowledge, reusable examples, and best practices. You'll help the team address unique public sector challenges such as security, compliance, and mission-critical software delivery, and contribute customer insights that shape our product direction."
We'll put as paragraph(s) under About the Team.
Then "How GitLab Supports Full-Time Employees Benefits":
List:
- Benefits to support your health, finances, and well-being
- Flexible Paid Time Off
- Team Member Resource Groups
- Equity Compensation & Employee Stock Purchase Plan
- Growth and Development Fund
- Parental Leave
We'll put as list under Benefits.
We must remove the sentence "Please note that we welcome interest from candidates with varying levels of experience; many successful candidates do not meet every single requirement. Additionally, studies have shown that people from underrepresented groups are less likely to apply to a job unless they meet every single qualification. If you're excited about this role, please apply and allow our recruiters to assess your application." Also remove Country Hiring Guidelines, Privacy Policy, EEO statements.
Now produce HTML fragment.
We need to ensure no extra whitespace? Just output.
Let's craft:
GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster. The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software.
About the role
As a Public Sector Solutions Architect, you'll be a trusted advisor to U.S. government customers, helping them understand how GitLab's Enterprise Edition and DevSecOps platform can address real business and mission outcomes. You'll own the technical evaluation and validation stages of the sales cycle, guide customers through proofs of concept and value, and connect GitLab's modern software development, operations, and cloud capabilities to measurable value. In this role, you'll work closely with sales and cross-functional GitLab teams, provide technical guidance from first conversation through successful deployment, and act as a customer advocate back into Product, Sales, and Marketing.
Responsibilities
- Engage with public sector customers, both onsite and remotely, to provide technical expertise and guidance throughout the pre-sales process, including tailored demos, technical presentations, and hands-on workshops.
- Collaborate with the sales team to shape and execute account strategies that drive GitLab adoption within government environments.
- Own the technical evaluation process, including proof of concept (POC) and proof of value (POV) design and delivery, tender and audit support, and technical input into proposals.
- Lead the creation of Customer Success Plans that capture technical success criteria and handoff details from the pre-sales process, ensuring a smooth path to deployment and adoption.
- Build and deepen relationships with technical and business stakeholders so they become advocates for GitLab within their organizations.
- Serve as the customer advocate internally by channeling feedback and insights to Product, Sales, Marketing, and other GitLab teams to influence roadmap and messaging.
- Maintain and expand your expertise in GitLab and related technologies, including modern software development, operations, and cloud practices, and create reusable examples and assets for customers and partners.
- Run Value Stream Assessments to identify opportunities for customers to improve their software delivery with GitLab.
Requirements
- Background in technical pre-sales, consulting, or information technology roles, ideally with U.S. public sector or federal customers, where you guided customers through evaluations and solution design
- Hands-on experience using GitLab and familiarity with modern software development and operations practices, such as CI/CD, DevSecOps, and automation
- Experience with cloud computing platforms and related technologies in regulated or security-conscious environments.
- Ability to connect technical solutions to measurable business or mission outcomes and to advise senior stakeholders on tradeoffs and options.
- Strong, confident communication and relationship-building skills, including leading customer meetings, demos, and value-focused conversations in close partnership with sales and cross-functional teams
- Openness to learning, seeking feedback, and building new skills, including familiarity with GitLab's Solutions Architect handbook and related resources.
About the Team
The Public Sector Solutions Architect role is part of GitLab's Solutions Architect team, a group of trusted technical advisors who help government customers understand, evaluate, and adopt the GitLab DevSecOps platform. The team is distributed and collaborates asynchronously across time zones using GitLab and our handbook-first practices to share knowledge, reusable
Requirements
then list. Then "About The Team" -> maybe "Team" but not in list; we could useAbout the Team
but not in allowed list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those. So we can use About the Team as heading.
Then "How GitLab Supports Full-Time Employees Benefits" -> Benefits. Use Benefits
then list.
We must not include Pay or Schedule sections because not present.
We must not include filler like "commensurate with experience". Not present.
We need to remove boilerplate: The initial paragraph about GitLab is maybe okay. Also the sentence "Fortune 500® is a registered trademark..." is legal boilerplate; should remove. Also "Claim based on GitLab data..." etc. Remove.
Also remove "An Overview Of This Role" heading? We'll convert to About the role
and keep content.
We need to ensure we don't duplicate lines.
Let's extract content.
Intro paragraph before "An Overview Of This Role":
"GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster. The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software."
We keep that as
. Then after that, "An Overview Of This Role As a Public Sector Solutions Architect, you'll be a trusted advisor to U.S. government customers, helping them understand how GitLab's Enterprise Edition and DevSecOps platform can address real business and mission outcomes. You'll own the technical evaluation and validation stages of the sales cycle, guide customers through proofs of concept and value, and connect GitLab's modern software development, operations, and cloud capabilities to measurable value. In this role, you'll work closely with sales and cross-functional GitLab teams, provide technical guidance from first conversation through successful deployment, and act as a customer advocate back into Product, Sales, and Marketing." We'll put that as paragraph(s) under About the role. Then "What You'll Do" bullet list: - Engage with public sector customers, both onsite and remotely, to provide technical expertise and guidance throughout the pre-sales process, including tailored demos, technical presentations, and hands-on workshops. - Collaborate with the sales team to shape and execute account strategies that drive GitLab adoption within government environments. - Own the technical evaluation process, including proof of concept (POC) and proof of value (POV) design and delivery, tender and audit support, and technical input into proposals. - Lead the creation of Customer Success Plans that capture technical success criteria and handoff details from the pre-sales process, ensuring a smooth path to deployment and adoption. - Build and deepen relationships with technical and business stakeholders so they become advocates for GitLab within their organizations. - Serve as the customer advocate internally by channeling feedback and insights to Product, Sales, Marketing, and other GitLab teams to influence roadmap and messaging. - Maintain and expand your expertise in GitLab and related technologies, including modern software development, operations, and cloud practices, and create reusable examples and assets for customers and partners. - Run Value Stream Assessments to identify opportunities for customers to improve their software delivery with GitLab. We'll put each as
GitLab is the intelligent orchestration platform for DevSecOps. GitLab enables organizations to increase developer productivity, improve operational efficiency, reduce security and compliance risk, and accelerate digital transformation. More than 50 million registered users and more than 50% of the Fortune 100* trust GitLab to ship better, more secure software faster. The same principles built into our products are reflected in how our team works: we embrace AI as a core productivity multiplier, with all team members expected to incorporate AI into their daily workflows to drive efficiency, innovation, and impact. GitLab is where careers accelerate, innovation flourishes, and every voice is valued. Our high-performance culture is driven by our values and continuous knowledge exchange, enabling our team members to reach their full potential while collaborating with industry leaders to solve complex problems. Co-create the future with us as we build technology that transforms how the world develops software.
About the role
As a Public Sector Solutions Architect, you'll be a trusted advisor to U.S. government customers, helping them understand how GitLab's Enterprise Edition and DevSecOps platform can address real business and mission outcomes. You'll own the technical evaluation and validation stages of the sales cycle, guide customers through proofs of concept and value, and connect GitLab's modern software development, operations, and cloud capabilities to measurable value. In this role, you'll work closely with sales and cross-functional GitLab teams, provide technical guidance from first conversation through successful deployment, and act as a customer advocate back into Product, Sales, and Marketing.
Responsibilities
- Engage with public sector customers, both onsite and remotely, to provide technical expertise and guidance throughout the pre-sales process, including tailored demos, technical presentations, and hands-on workshops.
- Collaborate with the sales team to shape and execute account strategies that drive GitLab adoption within government environments.
- Own the technical evaluation process, including proof of concept (POC) and proof of value (POV) design and delivery, tender and audit support, and technical input into proposals.
- Lead the creation of Customer Success Plans that capture technical success criteria and handoff details from the pre-sales process, ensuring a smooth path to deployment and adoption.
- Build and deepen relationships with technical and business stakeholders so they become advocates for GitLab within their organizations.
- Serve as the customer advocate internally by channeling feedback and insights to Product, Sales, Marketing, and other GitLab teams to influence roadmap and messaging.
- Maintain and expand your expertise in GitLab and related technologies, including modern software development, operations, and cloud practices, and create reusable examples and assets for customers and partners.
- Run Value Stream Assessments to identify opportunities for customers to improve their software delivery with GitLab.
Requirements
- Background in technical pre-sales, consulting, or information technology roles, ideally with U.S. public sector or federal customers, where you guided customers through evaluations and solution design
- Hands-on experience using GitLab and familiarity with modern software development and operations practices, such as CI/CD, DevSecOps, and automation
- Experience with cloud computing platforms and related technologies in regulated or security-conscious environments.
- Ability to connect technical solutions to measurable business or mission outcomes and to advise senior stakeholders on tradeoffs and options.
- Strong, confident communication and relationship-building skills, including leading customer meetings, demos, and value-focused conversations in close partnership with sales and cross-functional teams
- Openness to learning, seeking feedback, and building new skills, including familiarity with GitLab's Solutions Architect handbook and related resources.
About the Team
The Public Sector Solutions Architect role is part of GitLab's Solutions Architect team, a group of trusted technical advisors who help government customers understand, evaluate, and adopt the GitLab DevSecOps platform. The team is distributed and collaborates asynchronously across time zones using GitLab and our handbook-first practices to share knowledge, reusable