Sr Data Solutions Architect, Strategic Accounts

We need to output HTML fragment with sections: 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. Must preserve all substantive info, no boilerplate, no EEO, etc. Must not invent or summarize away detail. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes salary ranges for specific locations, and mentions benefits: "Amazon also offers comprehensive benefits including health insurance..., 401(k) matching, paid time off, and parental leave." Also mentions "Open to traveling up to 25% domestic with some international travel." That's schedule? Travel is schedule? Might be considered schedule? The instruction: include a section ONLY when posting has real, specific content for it. Travel could be schedule? But schedule usually refers to work schedule (full-time, part-time, shift). Travel is not schedule. Might not include schedule. Benefits: yes they list benefits. Pay: they list salary ranges for locations. So include Pay and Benefits sections. Also About the role: there is description at top. Responsibilities: there is a list of responsibilities under "Key job responsibilities" and sub-bullets. Requirements: there are "Basic Qualifications" and "Preferred Qualifications". Skills: maybe we can extract skills from responsibilities? But we need a Skills section only if posting has real specific content for it. There's no explicit "Skills" heading, but we could infer from qualifications? However instruction: prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications? But they ask to use headings for those sections if content exists. We have Basic Qualifications and Preferred Qualifications; we could put them under Requirements (or Qualifications). The spec says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which to include. We have content for About the role (initial paragraph). Responsibilities (list). Requirements (basic qualifications). Qualifications (preferred qualifications). Skills maybe not explicit; we could omit Skills section. Benefits (yes). Pay (yes). Schedule maybe not (travel not schedule). So we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Ensure we use

for each heading. Use

• for lists. Use

  for prose. Must not repeat job title. Must not include Job ID etc. Must strip boilerplate like EEO, equal opportunity, legal, etc. Also remove duplicated lines, navigation, cookie, etc. Also remove "Our inclusive culture empowers Amazonians..." etc. Also remove "If you have a disability..." etc. Also remove "Los Angeles County applicants..." etc. Also remove "Pursuant to the San Francisco Fair Chance Ordinance..." etc. Also remove "If the country/region you’re applying in isn’t listed..." etc. Also remove "Amazon is an equal opportunity employer..." etc. Also remove "Why AWS?" etc? Actually "Why AWS?" includes some content about AWS being comprehensive cloud platform, inclusive team culture, mentorship, work/life balance. That is substantive? It's more generic marketing but could be considered part of About the role? Might be considered boilerplate but it's about AWS culture. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Why AWS?" section is not exactly legal boilerplate; it's marketing but could be considered part of the job description. However it's somewhat generic; but we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's considered boilerplate. The instruction says prefer a few substantive sections over many thin ones. The "Why AWS?" could be part of About the role or maybe we could include as part of About the role. But we already have About the role from the initial description. We could merge the "Why AWS?" content into About the role paragraph. However we must not invent or summarize away detail; we can just keep it as part of About the role prose. So we can include that text in About the role. We need to ensure we don't include duplicated lines. Also need to exclude "Open to traveling up to 25% domestic with some international travel." That's substantive; maybe we could put under Responsibilities or a separate Schedule? But schedule not appropriate. Could include under Responsibilities as a bullet? It's not a responsibility but a condition. Could include under About the role as a sentence. We'll keep it in About the role. Now let's extract content. About the role: The initial paragraph: "Description Come build the future of data with us! Amazon Web Services (AWS) is seeking a senior, experienced, and motivated Data Specialist Solutions Architect (SSA) to help our Strategic Accounts customers architect the next generation of data platforms that power agentic AI and advanced analytics workloads. You should possess a unique balance of deep technical expertise in modern data technologies, business acumen, and exceptional interpersonal skills. In this role, you will partner with our most valuable customers to design enterprise-wide data strategies that connect siloed data across organizations in secure, scalable, and innovative ways using AWS, partner, and open-source data technologies. You will make a significant impact working directly with customer executives, forming trusted relationships as you help them define and execute their data modernization roadmaps. You will collaborate with AWS service teams to influence product direction and advocate for new features and capabilities based on Strategic Accounts needs. Our customers are industry leaders, and if you have what it takes to guide these critical accounts through complex data transformation initiatives, AWS wants to talk to you. The ability to bridge database, storage, analytics, and artificial intelligence technologies is essential for the Data SSA function. You should demonstrate strategic thinking about business challenges in the Agentic AI era and articulate technical solutions to address them. As a trusted customer advocate, you will develop comprehensive data technology strategies for our largest Strategic Accounts customers operating in complex, multi-faceted environments. You will interface with customer leadership to build relationships and enable them as data strategy champions. You will guide customers in designing advanced cloud-based data architectures, implementing innovative technologies across AWS services (including Amazon RDS, Aurora, Redshift, Athena, EMR, Glue, Kinesis, MSK), partner solutions (Snowflake, Databricks), and open-source frameworks (Spark, Flink, Trino), while adopting the best cloud practices for databases, storage, and analytics services. You will share your successes and learnings with the broader AWS SA community. Open to traveling up to 25% domestic with some international travel." Also "Why AWS?" section: "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. Inclusive Team Culture Here at AWS, it’s in our nature to learn and be curious. Our employee-led affinity groups foster a culture of inclusion that empower us to be proud of our differences. 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. 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 in the cloud." Also "AWS Sales, Marketing, and Global Services (SMGS) is responsible for driving revenue, adoption, and growth from the largest and fastest growing small- and mid-market accounts to enterprise-level customers including public sector. The AWS Global Support team interacts with leading companies and believes that world-class support is critical to customer success. AWS Support also partners with a global list of customers that are building mission-critical applications on top of AWS services. The AWS Industries team is committed to helping industry customers enable their digital transformation journeys. Our primary goal is to meet customers where they are in their cloud journey and work backwards from their industry specific needs to transform their business and their entire industry. Our team speaks the language of our industry customers, which means that we focus on business outcomes and industry use cases on behalf of our customers, whether that is how we build products and solutions, how we sell, how we deliver, or how we partner." This is more about AWS organization; could be considered part of About the role? It's somewhat generic but still substantive. We'll include it in About the role as well. Now Responsibilities: Under "Key job responsibilities" we have bullet points: - Customer Engagement & Solutions Design - Work closely with customers to design, implement, and manage AWS, OSS and partner data solutions that meet their technical requirements and business objectives, serving as a key player in driving customer success through their cloud journey. - Delivering on-site technical assessments with partners and customers, participating in customer visits, understanding customer requirements, and creating reference architectures utilizing AWS, partner and OSS analytics, database and storage, solutions. - Engaging with customer business and technology stakeholders to create a compelling vision of a modern data ecosystem to support a world where agents are the primary consumers of data. - Data Architecture Design & Implementation - Help customers define and implement data architectures including data lakes and lakehouses to meet the demands of an agentic future while proving the value of AWS infrastructure to support new distributed computing solutions that often span private cloud and public cloud services. - Technical Leadership & Advisory - As trusted advisors to customers, provide guidance on industry trends, emerging technologies, and innovative solutions while leading the implementation process, ensuring adherence to best practices, optimizing performance, and managing risks throughout the project. - This Includes Working closely with stakeholders to gather requirements, assess current infrastructure, and propose effective migration strategies to AWS. - Owning technical engagements and ensuring timely and successful value delivery. - Project Delivery & Oversight - Overseeing project delivery and ensuring compliance with security and governance standards. - Owning the planning, execution, technical engagement, and outcomes of specific implementation projects and assignments. - Collaboration & Communication - Collaborating with sales and technical teams to create proposals and assess customer needs. - Communicating with internal teams like Account Managers, Service Teams and Go-to-Market, bridging the gap between technical and non-technical stakeholders. Also "A day in the life" paragraph: "As a senior member of the account team, you will drive customer satisfaction and revenue growth across a strategic portfolio. You will interact, communicate, and partner with other AWS organizations including service teams, marketing, professional services, and business development to represent your customers' needs to AWS executive leadership. You will think strategically about business, product, and technical challenges while maintaining a passion for educating, training, and designing innovative cloud data solutions for enterprise customers." We could include that as part of Responsibilities or maybe separate but we can add to Responsibilities. Now Requirements: Basic Qualifications list: - 8+ years of specific technology domain areas (e.g. software development, cloud computing, systems engineering, infrastructure, security, networking, data & analytics) experience - 3+ years of design, implementation, or consulting in applications and infrastructures experience - 10+ years of IT development or implementation/consulting in the software or Internet industries experience - Experience with big data processing technology (e.g., Hadoop or ApacheSpark), data warehouse technical architecture, infrastructure components, ETL, and reporting/analytic tools and environments Also maybe "Preferred Qualifications" list: - 5+ years of infrastructure architecture, database architecture and networking experience - Experience working with end user or developer communities - Bachelor's degree in computer science, engineering, mathematics or equivalent - Knowledge of cloud architecture - Knowledge of AWS services, market segments, customer base and industry verticals - Experience leading and influencing your team or organization, or experience building complex software systems that have been successfully delivered to customers We'll put Basic Qualifications under Requirements heading, Preferred Qualifications under Qual