Principal Solutions Architect (East Coast or Central)
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need headings like About the role, Responsibilities, Qualifications, Benefits, Pay, etc. Only include sections that have real specific content. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "Posting Information" etc. Also remove "Docker does not offer visa sponsorship for this role."? That's not boilerplate but maybe considered minor metadata; we can fold into a short
or drop it. Probably keep as a short paragraph under Qualifications or something. We need to include sections: About the role (intro description), Responsibilities, Qualifications (maybe combine Requirements and Qualifications), Benefits, Pay (Compensation & Equity). Schedule? Not mentioned. So we omit Schedule. We must not create sections with placeholder text. Ensure we only include sections with content. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About Docker intro: "About Docker Docker has been one of the most loved brands in developer tooling, trusted by more than 20 million monthly users and over 20 billion container image pulls. From solo founders to the world's largest companies, developers rely on Docker to build, share, and run their applications across our suite of products including Docker Desktop, Docker Hub, and Docker Scout. We are a globally distributed, remote-first team building the tools that define how software gets built and delivered. As AI agents redefine software development, Docker is at the center of that shift, providing the sandboxed environments, verified images, and secure infrastructure that make autonomous workflows trustworthy by default." Then the role description: "We are seeking a highly consultative Principal Solutions Architect to support our most important customers. This role is a critical technical position, spanning both product development and pre and post sales customer motions. You will act as a trusted technical lead and thought leader, partnering closely with Account Executives, Solutions Engineers, Post Sales, and Product teams to drive measurable business and technical value through High priority customer technical leadership Docker field technical leadership This role reports to the Director of Solutions Architecture and operates at the intersection of technical depth, business acumen, and thought leadership." We can combine into About the role section. Responsibilities: There's a block titled "Responsibilities" with bullet-like sentences. Let's extract each sentence as list items. Responsibilities content: - High priority customer technical leadership Work with Docker’s most important customers and cross functional Docker teams to accelerate the customer’s container and AI journeys, focusing on developer workflows - Engage with customer teams and cross functional Docker teams to gather customer’s technical/business goals and challenges related to their container and AI journey. - Create and manage engagement plans that span existing products and new Docker offerings to achieve critical business goals. - Oversee “design partner” rapid prototyping engagements with Docker engineering and customer teams to validate customer-product fit for new use cases - Work with Docker teams to create/manage/deliver custom demos and content aligned to customer use cases. - Deliver high-impact enablement and best practices content to customer audiences from developer to C level. - Ability to travel up to 50% domestically and internationally as a senior representative of Docker to prospective clients, customers, and technical alliance partners. - Docker field technical leadership (regional/area of responsibility) Be a thought leader for a particular area of responsibility both internal and external to Docker, working with fellow Dockhands to create/manage/deliver content - Gather field feedback from customer teams and Docker pre and post sales teams - Coordinate with Field CTO and other Solutions Architects to prioritize/contextualize/correlate field requests into a cohesive set of prioritized requests to the product/engineering teams. - Work directly with Docker product/engineering teams on workflows and feature alignment to customer use cases prioritized by revenue impact. - Be customer zero for new functionality produced by Docker product/engineering teams - Give input on internal technical enablement and customer enablement needs, and review enablement content - Assist the sales enablement team with internal technical enablement for new products and services. We need to ensure no duplication. Some sentences may be duplicated? Not obvious. Qualifications: block titled "Qualifications". Extract each sentence. Qualifications content: - Proven experience as a Sales Engineer, Solutions Engineer, or Solution Architect in complex enterprise environments. - Excellent communication, influence, and stakeholder management skills. - Experience in managing customer relationships at the technical and business level. - Experience presenting solutions and demonstrations to small and large audiences, virtually and in person. - Experience interfacing with internal product/software teams, including technical support, product, and engineering, to enhance documentation, enablement, and product features to improve customer experience and enablement. - Experience developing application code, and a clear understanding of the challenges developers experience on a daily basis. - Ability to solve technical problems and translate customer experience to actionable feedback for engineering. - Experience developing collateral to assist customers with best-practice adoption. - Solid understanding of cloud platforms (AWS, Azure, GCP), containers, DevOps, and modern application architectures. - Experience with Docker, container ecosystems, or adjacent technologies strongly preferred. - Development, Agentic AI dev, Software Development Lifecycle and/or Software Supply Chain Security experience strongly preferred. - Must be fluent in English - Willingness to travel up to 50% domestically and internationally as a senior representative of Docker to prospective clients, customers, and technical alliance partners. Also there is "What To Expect" sections (First 30 days, First 60 days, First 90 days). Those could be considered part of role description or maybe separate section like "What to Expect". But the instruction only lists certain headings; we could include a section like "What to Expect" but not in the list. Better to incorporate into About the role or maybe create a section "What to Expect" but not required. Since they said prefer a few substantive sections over many thin ones, we could incorporate the "What To Expect" into About the role or maybe a separate section "Onboarding & Ramp-up". However the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings but says use those for section headings (e.g. About the role, Responsibilities...). Likely they expect only those headings. So we should map content to those headings. Thus we can have:
About the role
with paragraphs covering the intro about Docker, role description, and maybe the "What To Expect" timeline.Responsibilities
with- items.
Qualifications
with- items.
Benefits
with- items from Perks & Benefits.
Pay
with paragraph about compensation. We should not include Schedule. We need to remove duplicated lines: The travel requirement appears both in Responsibilities and Qualifications; we should keep only once? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If duplicated, we should keep both? It says remove duplicated lines. So we should deduplicate. Travel up to 50% appears in Responsibilities and Qualifications. We'll keep only one instance, maybe under Qualifications (or Responsibilities). Let's keep under Qualifications (makes sense). Remove from Responsibilities. Also "Ability to travel up to 50% domestically and internationally as a senior representative of Docker to prospective clients, customers, and technical alliance partners." appears twice. We'll keep one. Also "Docker field technical leadership (regional/area of responsibility)" appears as a heading inside Responsibilities; we can treat as a list item. Now Benefits: list from "Perks & Benefits". Items: - Remote-first by design – Work from your home, with offices in Seattle and Paris for connection and collaboration. - Flexibility that fits your life – We trust you to manage your schedule while delivering great work. - Time to recharge – Generous PTO, designated quarterly Whaleness Days, and a designated end-of-year Whaleness break. - Home office support – Set up your workspace for comfort and success. - Technology stipend – Equivalent to US$100 net per month to help support your work. - Learning & development – Annual stipend for conferences, courses, certifications, and continued learning. - Parental leave – 16 weeks of paid parental leave after six months of employment. - Equity for all full-time employees – Share in Docker's long-term success as we continue to grow. - Comprehensive benefits – Medical, retirement, and paid holidays vary by country. - Docker swag – Because representing the whale never gets old. We should output as- .
Pay: "Compensation & Equity Canada: CA$314,300 – CA$449,00 OTE + equity United States:$217,000 – $310,000 OTE + equity". Note there is a typo: CA$449,00 missing a digit? We'll keep as is.
We'll output as
. Now About the role: combine Docker intro, role description, and What To Expect timeline (first 30/60/90 days). We'll put as paragraphs. We need to ensure we don't include boilerplate like "Posting Information", "Open vacancy:", "AI in hiring:", "Interview recordings:", "Docker does not offer visa sponsorship for this role.", "EEO", etc. Also remove the lines like "_______________________________________________________________". Also remove the repeated "Docker field technical leadership" heading inside responsibilities? We'll treat as list item. Now produce HTML. Let's craft. About the role:
About Docker Docker has been one of the most loved brands in developer tooling, trusted by more than 20 million monthly users and over 20 billion container image pulls. From solo founders to the world's largest companies, developers rely on Docker to build, share, and run their applications across our suite of products including Docker Desktop, Docker Hub, and Docker Scout. We are a globally distributed, remote-first team building the tools that define how software gets built and delivered. As AI agents redefine software development, Docker is at the center of that shift, providing the sandboxed environments, verified images, and secure infrastructure that make autonomous workflows trustworthy by default.
We are seeking a highly consultative Principal Solutions Architect to support our most important customers. This role is a critical technical position, spanning both product development and pre and post sales customer motions. You will act as a trusted technical lead and thought leader, partnering closely with Account Executives, Solutions Engineers, Post Sales, and Product teams to drive measurable business and technical value through high priority customer technical leadership. This role reports to the Director of Solutions Architecture and operates at the intersection of technical depth, business acumen, and thought leadership.
What to Expect – First 30 days: You will be welcomed with a first-in-class onboarding experience that includes equipment setup, a sweet swag package, and a collaborative training program; you will learn how to navigate through award-winning sales tools such as Salesforce, Outreach, Sigma, and Opine; actively engage with senior stakeholders, and manage relationships with clients; you will work closely with your peers and shadow customer meetings to develop strategies to advocate for our customers. At the end of your first month, you will have a proficient grasp of the tools and activities necessary to be successful in your role.
First 60 days: You will be laser-focused on supporting the sales and customer success teams during your second month; you will have connected with all of your team members; you will gain
- .
Pay: "Compensation & Equity Canada: CA$314,300 – CA$449,00 OTE + equity United States:$217,000 – $310,000 OTE + equity". Note there is a typo: CA$449,00 missing a digit? We'll keep as is.
We'll output as
- items from Perks & Benefits.
- items.