Principal Consultant-AWS

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About the role: The first paragraph: "The AWS Principal Consultant engages with clients and internal teams to provide design and engineering activities for AWS projects and solutions. This role is expected to be a thought leader in the areas of technical solutions provided for our customer. The Principal Consultant is also responsible for working with Management to align delivery teams on best practices and upskilling architecture and engineering resources." That's about the role. - Responsibilities: The bullet list after "What You Will Do". Many items: "Professional services delivery for CDW customers globally on major Public Cloud platforms", "Aggregate oversight of technical solutions across multiple projects to ensure synergy in our approach and broad visibility to the solutions delivery team", "Works closely with other CDW consulting groups for cohesive technical solution approaches focusing on bridging the gap between sales and delivery", "Focuses on technical standardization and opinionated approaches for client solutions", "Assists management with technical growth plans for engineers and architects", "Assists with SOW reviews and approval as needed.", "Assists with technical screening for new candidate interviews", "Lead technical deployment engineering with customers on workload design on major public cloud vendors.", "Provide workshops and training events for customers and industry leaders on emerging technologies in Public Cloud", "Training and Mentoring Engineers and Architects to take on Cloud and DevOps projects", "Providing Engineering Services for AWS, coordinating engagement strategies, and qualifying technical resource augments", "Proficiency in automation tools and technologies relevant to IT operations, such as configuration management tools (e.g., Ansible, Puppet, Chef), continuous integration/continuous deployment (CI/CD) tools (e.g., Jenkins, GitLab CI/CD), infrastructure-as-code (IaC) tools (e.g., Terraform, CloudFormation), and containerization platforms (e.g., Docker, Kubernetes).", "Deep understanding of AI and machine learning algorithms, including supervised learning, unsupervised learning, reinforcement learning, deep learning, and natural language processing (NLP)", "Continuous learning and staying updated with the latest advancements, research papers, and breakthroughs in AI and related fields.", "Oversee team projects to ensure delivery excellence and act as an escalation point.", "Ability to analyze complex systems, workflows, and dependencies to design effective automation solutions that address business needs and requirements.", "Strong knowledge of DevOps principles and practices, including continuous integration, continuous delivery, infrastructure as code, and automated testing.", "Experience in implementing DevOps workflows and pipelines to automate software development, testing, deployment, and operations processes.", "Performing Billable work at other DV clients (Consulting Engagements)", "Support Presales architects on large deals to validate consulting estimates as well as provide needed expertise for Cloud/DevOps projects", "Meet Training and certification requirements for selected Vendors (AWS, Hashicorp, Docker, CKA, etc.)", "Help develop and mature our Cloud Solutions practice areas in response to client needs and market demand.", "Travel estimate is 10% Internal projects when applicable" Some of these are more like responsibilities; some are skills. We'll separate. - Requirements / Qualifications: "What We Expect Of You" includes: Bachelor's Degree and 7+ years of IT Infrastructure experience, including at least 3 years in large enterprise consulting. Or, 10+ years of IT Infrastructure experience, including at least 3 years in large enterprise consulting. The candidate should demonstrate leadership and provide expert advice on technical matters and architecture design. They should be a subject matter expert, staying updated with the latest technology trends, and have the ability to develop IT services offerings. Proven ability to maintain client relationships as a trusted advisor and mentor engineers for project design and coordination. Excellent communication skills are required, with experience in making technology recommendations. History of building constructive relationships at all organizational levels and the ability to research complex technology solutions and present them to clients. Should remain calm and productive in situations of change, ambiguity, and risk. Ability to multitask and prioritize in a fast-paced environment is essential. The candidate should anticipate future trends and create strategies that add value. Willingness to travel to other CDW locations or client sites. A valid U.S. driver’s license is required. Demonstrated knowledge of public cloud platforms, aware of multi-platform solutions and capabilities Expertise in automation and infrastructure as code.Deep understanding of Kubernetes architecture, including master and worker nodes, API server, etcd, kubelet, kube-proxy, and container runtimes. Knowledge of Kubernetes networking concepts, including service discovery, load balancing, network policies, and container networking interfaces (CNI). - Skills: Many items: proficiency in automation tools, deep understanding of AI/ML, continuous learning, ability to analyze complex systems, strong knowledge of DevOps, experience implementing DevOps workflows, etc. Could be separate Skills section. - Benefits: "Benefits overview: https://cdw.benefit-info.com/" plus maybe mention of annual bonus target of 10% subject to terms and conditions of plan. Also "Salary ranges may be subject to geographic differentials". Also "CDW is committed to being an AI-fluent organization ..." but that's more culture. Benefits: we have benefits overview link, annual bonus target. Also maybe mention of "Travel estimate is 10%" but that's schedule? Travel is schedule? Could be schedule. - Pay: "Pay range: $156,000 - $240,800 depending on experience and skill set". Also "Annual bonus target of 10% subject to terms and conditions of plan". Also "Salary ranges may be subject to geographic differentials". So we can include Pay section. - Schedule: Travel estimate 10% maybe schedule? Could include "Travel estimate is 10% Internal projects when applicable". Also maybe mention of "Willingness to travel to other CDW locations or client sites." That's schedule. We need to avoid filler like "commensurate with experience". Not present. We must not include boilerplate like EEO, equal opportunity, legal, etc. Also remove "About Us" maybe? It's not a required heading but could be considered "About the role"? Actually "About Us" is company description; we could include as a section maybe "About CDW"? But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but says use those for those sections. Probably we should stick to those headings only if content exists. "About Us" could be considered "About the role"? Not exactly. Might be better to omit "About Us" as it's not requested. However we need to preserve all substantive information; but "About Us" is substantive but not required heading; we could embed it in a

without heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for those sections. It might be okay to include other headings but better to follow guidance. We could put "About CDW" as a

without heading. But the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are the allowed headings. So we should only use those headings. So we need to map content to those headings. Thus: - About the role: first paragraph. - Responsibilities: list of duties from "What You Will Do" that are responsibilities (maybe many). We'll include all bullet-like items that are duties. - Requirements: education/experience etc. - Qualifications: maybe similar to requirements; but we could combine? The instruction says use headings for Requirements, Qualifications separately if content exists. We have both: "What We Expect Of You" includes education/experience, leadership, etc. That could be Requirements. Qualifications could be specific technical qualifications like Kubernetes, public cloud, automation, AI/ML, etc. We'll separate. - Skills: maybe list of specific technical skills (automation tools, AI/ML, DevOps, etc.) but some overlap with qualifications. We'll decide. - Benefits: benefits overview link, annual bonus target. - Pay: pay range, bonus, geographic differentials. - Schedule: travel estimate, willingness to travel. We must not repeat job title. Must not include metadata like Job ID. We must remove boilerplate: EEO, equal opportunity, legal, scam warning, etc. Also remove "About Us" maybe? But we need to preserve substantive info; "About Us" is substantive but not under allowed headings. Could we incorporate it into About the role? Not really. Maybe we can include a

without heading for "About Us". The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but suggests using those for those sections. It might be okay to have other headings but better to stick to those. However we need to preserve all substantive info; we could put "About Us" as a

without heading. That's allowed because we are not using a heading for it. The instruction didn't forbid paragraphs without heading. So we can include a

about CDW. Similarly, the AI-fluent organization statements could be part of About the role or maybe a separate section like "Culture". But we could incorporate into About the role or maybe a

without heading. We must not include duplicated lines. Let's extract content precisely. I'll rewrite in my own words but preserve meaning; must not invent or summarize away detail. We can keep sentences as is, but we need to format into HTML. We'll produce:

About the role

The AWS Principal Consultant engages with clients and internal teams to provide design and engineering activities for AWS projects and solutions. This role is expected to be a thought leader in the areas of technical solutions provided for our customer. The Principal Consultant is also responsible for working with Management to align delivery teams on best practices and upskilling architecture and engineering resources.

Responsibilities

• Professional services delivery for CDW customers globally on major Public Cloud platforms
• Aggregate oversight of technical solutions across multiple projects to ensure synergy in our approach and broad visibility to the solutions delivery team
• Works closely with other CDW consulting groups for cohesive technical solution approaches focusing on bridging the gap between sales and delivery
• Focuses on technical standardization and opinionated approaches for client solutions
• Assists management with technical growth plans for engineers and architects
• Assists with SOW reviews and approval as needed
• Assists with technical screening for new candidate interviews
• Lead technical deployment engineering with customers on workload design on major public cloud vendors
• Provide workshops and training events for customers and industry leaders on emerging technologies in Public Cloud
• Training and mentoring engineers and architects to take on Cloud and DevOps projects
• Providing engineering services for AWS, coordinating engagement strategies, and qualifying technical resource augments
• Proficiency in automation tools and technologies relevant to IT operations, such as configuration management tools (e.g., Ansible, Puppet, Chef), continuous integration/continuous deployment (CI/CD) tools (e.g., Jenkins, GitLab CI/CD), infrastructure-as-code (IaC) tools (e.g., Terraform, CloudFormation), and containerization platforms (e.g., Docker, Kubernetes)
• Deep understanding of AI and machine learning algorithms, including supervised learning, unsupervised learning, reinforcement learning,