DirectJobHub
Jobs · Consulting · Texas

Solutions Architect, AWS Industries - Energy & Utilities

Amazon Web Services (AWS) · Austin, TX · 3 wk ago
ConsultingFull-time
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. Must not include boilerplate like EEO, etc. Must preserve all substantive info. We need to parse description. Key parts: - Intro paragraph: description about role, team, etc. Could be "About the role" section. - "Key job responsibilities" -> Responsibilities. - "A day in the life" maybe part of responsibilities? Could be part of responsibilities but we can keep as part of responsibilities or separate? Probably keep under Responsibilities. - "About The Team" maybe part of About the role? Could be separate but we have only allowed headings. Could put under About the role. - "Diverse Experiences", "Why AWS?", "Inclusive Team Culture", "Mentorship & Career Growth", "Work/Life Balance" are boilerplate? They are generic AWS culture statements; maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Those sections are not exactly EEO but are generic company culture; they might be considered boilerplate? The instruction says to remove EEO/equal-opportunity/scam-warning boilerplate. Not explicitly remove culture sections. However they are not specific to the job; they are generic AWS marketing. Might be considered boilerplate? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It doesn't say to remove generic culture sections. But we should prefer few substantive sections over many thin ones. So we could combine them into About the role or maybe omit them to keep concise. However we must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit those culture sections, we are removing substantive information? They are substantive but generic. The instruction says to prefer few substantive sections over many thin ones. So we could include them under About the role as prose. - Basic Qualifications and Preferred Qualifications: these are Requirements/Qualifications/Skills. We need to map. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. - About the role: introductory paragraph about role, team, mission, location requirement (must be located within 25 miles of San Antonio, TX). Also maybe "About The Team". Could include location. - Responsibilities: list from "Key job responsibilities" and "A day in the life". Use
  • . - Requirements: maybe Basic Qualifications? Or "Requirements" could be basic qualifications. Qualifications could be Preferred Qualifications. Skills could be specific skills like experience with presentations, etc. But we have overlapping. Better: Use Requirements for basic qualifications, Qualifications for preferred qualifications, Skills for specific skill items like experience communicating across technical and non-technical audiences, presentations, architecting large enterprise IT environments, etc. However those are also in basic qualifications. Might be redundant. We could combine: Requirements = Basic Qualifications; Qualifications = Preferred Qualifications; Skills = maybe not needed if covered. But we need to output only sections with real content. If we put Skills empty, we shouldn't output. So we could omit Skills if not distinct. Benefits: The posting mentions benefits: "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." Also mentions sign-on payments and RSUs. So we have Benefits content. Pay: The posting includes base salary range: "USA, TX, Virtual Location - Texas - 153,600.00 - 207,800.00 USD annually". Also mentions sign-on payments and RSUs. So we have Pay. Schedule: Not mentioned. No schedule info. So we should not create Schedule section. Thus sections: About the role, Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Benefits, Pay. We need to ensure we don't repeat job title. Use

    for each section heading. We need to use
    • for any list of duties/requirements/benefits. For prose, use

      . We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from basic qualifications, preferred qualifications, responsibilities, day in the life, about the team, benefits, pay, location, etc. We must not include boilerplate like EEO, etc. We'll remove the equal opportunity employer paragraph and accommodation link, etc. Also remove "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." Also remove "Learn more about our benefits at https://amazon.jobs/en/benefits." (maybe that's a link; could be considered application instruction? It's a link to benefits; but it's not application instruction; but it's a reference. Might be okay to keep? The instruction says remove application instructions. That link is not an application instruction but a reference. Might keep but it's not substantive? It's a link to learn more about benefits; could be considered boilerplate. Safer to omit. Also remove "Amazon is an equal opportunity employer..." paragraph. Also remove "If you have a disability and need a workplace accommodation..." paragraph. Also remove "Our inclusive culture empowers Amazonians..." maybe keep as part of About the role? It's generic but could be considered boilerplate. I'd lean to omit to keep focused. We must preserve location requirement: "Must be located within 25 miles of San Antonio, TX". Include in About the role. Now craft content. About the role: combine introductory paragraphs and About The Team. Let's extract: Intro: "Imagine being a part of a team where your ideas can help reshape the future of the Energy industry and improve the lives of many. Here at Amazon Web Services (AWS), you'll work with a talented & inclusive team while using the latest technologies to help our customers accelerate the global energy transition. We are looking for an experienced and motivated technologist who possess a deep understanding of the Oil & Gas industry. You will have a business mindset, technical depth, and have strong interpersonal skills to build the future with us as a Solutions Architect - supporting one or some of the largest Energy companies in the world. You will work with customer line of business owners to solve their biggest business problems and help them attain new levels of performance. You will leverage AWS’ leading AI and cloud services to craft highly scalable, flexible and resilient cloud architectures that address business problems and accelerate the customer cloud journey. These solutions always have the customer and their experience at the center of everything we do. You will adeptly interact, communicate and partner with other teams at AWS such as product, marketing, and professional services, and represent your team to executive management. You possess a demonstrated ability to think strategically about business, products, and technical challenges. Your dynamism, creativity and passion for excellence will make a positive impact with your customer. If you can educate AWS customers about the art of the possible, while inspiring the impossible, come build the future with us." About The Team: "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 AI and 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." We can combine. Add location: "Must be located within 25 miles of San Antonio, TX." Now Responsibilities: list from "Key job responsibilities" and "A day in the life". Key job responsibilities bullet points (as paragraphs): - ownership of the technical relationship with customers, making recommendations on security, cost, performance, reliability, operational efficiency and best-practice architectures. - internally, act as an advocate on behalf of the customer to help drive continual improvements to the AWS platform, sharing their needs and wants to inform the roadmap of AWS features and services. - help shape the future of the Solutions Architecture organisation by helping to hire, coach and mentor others. - creativity will link technology to tangible solutions, with the opportunity to define or invent cloud-native reference architectures with the worldwide AWS Solutions Architect community. - participate in the creation and sharing of best practices, technical content and new reference architectures (e.g. white papers, code samples, blog posts) and evangelise and educate about AWS technology (e.g. through workshops, user groups, meetups, public speaking, online videos or conferences). A day in the life details: we can turn into list items as well. - leading a 2-hour architecture review with the customer's platform engineering team on data lake modernization, driving deep technical discussions on design trade-offs. - spending a day on-site at the customer's office conducting discovery sessions with new business units, having lunch with the VP of Digital to discuss their AI roadmap and influence strategic direction. - building and refining a generative AI demo using RAG architecture for automated drilling report summarization, sync with account team to align on messaging, and brief specialist teams on complex workloads. - presenting Well-Architected reviews to the customer's cloud center of excellence. - writing competitive displacement patterns for peer Solutions Architects. - participating in hiring debriefs. - leading community sessions to share reference architectures that scale beyond direct delivery. We can combine all into a single

      • list. Now Requirements (basic qualifications): list each bullet. 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 communicating across technical and non-technical audiences, including executive level stakeholders or clients - Experience with presentations and speaking with executives, IT, management, and developers - Experience architecting and operating in large Enterprise IT environments, including expertise with corporate identity management systems, enterprise authentication frameworks, standard operating procedures (SOPs), IT Service Management (ITSM), change management processes, and enterprise security controls. Note there is a duplicate "experience" at end of each line; we keep as is. Now Qualifications (preferred qualifications): list. Preferred Qualifications: - 5+ years of infrastructure architecture, database architecture and networking experience - Knowledge of software development tools and methodologies - Experience architecting or deploying Cloud/Virtualization solutions in enterprise customers - Experience in design, implementation, or consulting in applications and infrastructures (duplicate of basic? but keep) - Experience working with Data & AI related technologies, including, but not limited to, AI/ML, GenAI, Analytics, Database, and/or Storage - Experience designing IoT architectures for industrial settings, including expertise with sensor networks, telemetry systems, equipment monitoring platforms, and integration patterns for legacy operational systems Now Benefits: list. Benefits: - Sign-on payments and restricted stock units (RSUs) - 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 - Parental leave We could also mention base salary range under Pay. Pay: - Base salary range: $153,600.00 - $207,800.00 USD annually (for USA, TX, Virtual Location - Texas) - Sign-on payments and RSUs (maybe already in benefits; but we can mention under Pay as part of

Similar jobs