Solutions Architect, Greenfield, Automotive & Manufacturing
About the role
and thenwith that content. Next: "Key job responsibilities New customer acquisition of Automotive & Manufacturing customers Communicate effectively with both business and technical stakeholders as a trusted technical advisor. Participate in deep architectural and design discussions to create world-class solutions built on AWS while ensuring solutions are designed for successful deployment in the cloud. Author and contribute to AWS customer-facing publications such as whitepapers and proof of concepts. In partnership with the sales team, formulate and execute a sales strategy to exceed revenue objectives through the adoption of AWS. Build deep relationships with business and senior technical individuals within customers to enable them to be cloud advocates. Capture and share best-practice knowledge amongst the AWS solutions architect community. Travel is mostly regional, and is expected to be 15-20% A day in the life" We need to extract responsibilities as list items. Also note "Travel is mostly regional, and is expected to be 15-20%" maybe schedule? Actually travel percent could be schedule? But schedule section is for work schedule (e.g., full-time, part-time). Travel percent is not schedule; maybe we can include under responsibilities as a bullet. The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. Travel percent is not schedule; we can ignore or include under responsibilities. We also have "A day in the life" heading but no content after? Actually after that there is "Diverse Experiences" repeated. So we ignore. Next: "Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying." That's repeated twice (under "About The Team" and earlier). It's boilerplate about encouraging applicants; but it's substantive? It's about diversity encouragement. Might be considered boilerplate but it's not navigation/legal/EEO. It's a statement about inclusive hiring. Could be kept? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is about encouraging diverse applicants; not exactly EEO but similar. Might be considered EEO boilerplate. Safer to remove duplicated lines and maybe keep one instance? But it's repeated; we should remove duplicated lines. We can keep a single instance if it's substantive. However it's generic encouragement; might be considered boilerplate. I'd remove it entirely to avoid EEO-like content. The instruction says remove EEO/equal-opportunity boilerplate. This is about diverse experiences encouragement, which is similar. So remove. Next: "About The Team Diverse Experiences AWS values diverse experiences. Even if you do not meet all of the preferred qualifications and skills listed in the job description, we encourage candidates to apply. If your career is just starting, hasn’t followed a traditional path, or includes alternative experiences, don’t let it stop you from applying." Same as above; remove. Next: "Why AWS? Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses." That's about company; could be part of "About the role" or separate section "About AWS"? Not in allowed headings. Could be included in "About the role" as extra paragraph. But we already have about role; we could append. Next: "Inclusive Team Culture AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do." That's about culture; could be part of About the role or maybe a separate section "Benefits"? Not exactly. Could be part of About the role. Next: "Mentorship & Career Growth We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional." Next: "Work/Life Balance We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve." These are benefits/culture; could be part of Benefits section? Benefits usually refer to health insurance etc. But we have actual benefits later: "Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave." Thus we should create a Benefits section with that list. Pay: we have salary ranges per location. The posting includes multiple location salary ranges. That is pay info. So we need a Pay section with those ranges. Should we list each location? Yes preserve all substantive info. So we can list each location line as
or
- . Probably
- each.
Schedule: Not explicitly stated besides travel percent. No schedule like full-time/part-time. So we should not create Schedule section.
Qualifications: There's "Basic Qualifications" and "Preferred Qualifications". We need Requirements and Qualifications sections. The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Basic Qualifications (requirements) and Preferred Qualifications (preferred). Could map Basic Qualifications to Requirements, Preferred Qualifications to Qualifications. Also there may be Skills section: maybe we can extract skills from responsibilities? Not explicit. Could combine skills under Qualifications? But we need to follow headings only if content exists. We have content for Requirements and Qualifications. Skills maybe not explicit; we could omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We must not repeat job title. Use
for each section heading. Now we need to strip boilerplate: Remove duplicated lines, navigation, EEO, etc. Also remove "A day in the life" heading if no content. Remove "Why AWS?" etc? Might be considered fluff but it's substantive about company; we can incorporate into About the role. We need to preserve all substantive information: So we need to include the content from "Why AWS?" etc? It's about AWS; but we already have description about AWS Global Sales etc. Might be redundant but we should keep if not duplicated. However it's similar to earlier description; but we can keep as part of About the role. Let's craft About the role paragraph combining the initial paragraphs and the Why AWS? etc and culture etc? Might be too much but okay. Better: Keep About the role as the initial description (first paragraph plus the second paragraph about Solutions Architect team). Then we can add a separate section "About AWS" but not allowed heading. So we incorporate into About the role. Thus About the role content: combine: "AWS Global Sales drives adoption of the AWS cloud worldwide, enabling customers of all sizes to innovate and expand in the cloud. We dive deep to understand each customer's unique challenges, then craft innovative solutions that accelerate their success. This customer-first approach is how we built the world's most adopted cloud. Join us and help us grow. The Amazon Web Services (AWS) Solutions Architect team partners with customers to design and build some of the most scalable, flexible and resilient cloud architectures and solutions. AWS Solutions Architects collaborate with AWS Sales and other AWS teams to help address customer business challenges and accelerate the adoption of AWS services. As a trusted customer advocate, Solutions Architects help organizations understand best practices around advanced cloud-based solutions, and provide advice on strategies for migrating existing workloads to the cloud. You’ll help drive successful business outcomes across a broad set of enterprise customers through your passion for educating, training, designing and building cloud solutions. You will have the opportunity to help shape and execute a strategy to build deep adoption and broad use of AWS within your enterprise customers, and you will do this by mobilizing resources within AWS and working with our extensive partner network. Amazon Web Services (AWS) is the world’s most comprehensive and broadly adopted cloud platform. We pioneered cloud computing and never stopped innovating — that’s why customers from the most successful startups to Global 500 companies trust our robust suite of products and services to power their businesses. AWS values curiosity and connection. Our employee-led and company-sponsored affinity groups promote inclusion and empower our people to take pride in what makes us unique. Our inclusion events foster stronger, more collaborative teams. Our continual innovation is fueled by the bold ideas, fresh perspectives, and passionate voices our teams bring to everything we do. We’re continuously raising our performance bar as we strive to become Earth’s Best Employer. That’s why you’ll find endless knowledge-sharing, mentorship and other career-advancing resources here to help you develop into a better-rounded professional. We value work-life harmony. Achieving success at work should never come at the expense of sacrifices at home, which is why we strive for flexibility as part of our working culture. When we feel supported in the workplace and at home, there’s nothing we can’t achieve." That seems to capture all substantive non-boilerplate content. Now Responsibilities: list items. We need to extract each responsibility: - New customer acquisition of Automotive & Manufacturing customers - Communicate effectively with both business and technical stakeholders as a trusted technical advisor. - Participate in deep architectural and design discussions to create world-class solutions built on AWS while ensuring solutions are designed for successful deployment in the cloud. - Author and contribute to AWS customer-facing publications such as whitepapers and proof of concepts. - In partnership with the sales team, formulate and execute a sales strategy to exceed revenue objectives through the adoption of AWS. - Build deep relationships with business and senior technical individuals within customers to enable them to be cloud advocates. - Capture and share best-practice knowledge amongst the AWS solutions architect community. - Travel is mostly regional, and is expected to be 15-20% We could keep travel as a bullet. Now Requirements (Basic Qualifications): - 2+ years of design, implementation, or consulting in applications and infrastructures experience - 4+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data