Senior Solutions Architect I
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID etc. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also remove "About Us" maybe? It's not in list of allowed headings but we can still use for any heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings if needed? Probably we should stick to those headings where applicable. The posting includes "Responsibilities", "Qualifications", "About Us", "About The Team". "About Us" could map to "About the role"? Not exactly. But we could treat "About Us" as "About the role"? Might be okay. However "About The Team" could be considered part of benefits? Not exactly. The instruction says prefer few substantive sections over many thin ones. So maybe combine "About Us" and "About The Team" into a single section like "About the role" or "About the team"? But we need to preserve all substantive info. Could create sections: Responsibilities, Qualifications, Benefits (since benefits are listed), maybe "About the role" for introductory paragraphs. Pay and Schedule not present (no salary range given? Actually there is a line: "The below represents the expected salary range for this job requisition." but no actual numbers given, just statement. That's placeholder? It says "The below represents the expected salary range for this job requisition." but no numbers. That's filler? It says not to create Pay/Schedule/Benefits sections unless posting actually states them. Since no actual numbers, we should not create Pay section. Benefits are listed concretely: Competitive base salaries, Bonus incentives, 6% Company Match..., etc. So we should include Benefits section.
We also have "About Us" and "About The Team" which are descriptive about company culture, benefits, etc. Some of that overlaps with Benefits section. We could combine them into an "About the role" section that includes the introductory paragraphs about Amex Tech, GCS, etc. Then Responsibilities, Qualifications, Benefits.
We must not include boilerplate like EEO, equal opportunity, visa sponsorship note? Actually "Employment eligibility to work with American Express in the United States is required as the company will not pursue visa sponsorship for these positions." That's substantive? It's a requirement. Could be part of Qualifications? Might be included there. But it's a legal requirement; maybe we keep it in Qualifications.
We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. The text includes a lot of EEO statements at the end. Remove those.
Also remove "For a full list of Team Amex benefits, visit our Colleague Benefits Site ." That's a link; maybe keep as part of Benefits? It's a reference; we could keep but it's not substantive detail; maybe drop.
Also remove "US Job Seekers - Click to view the “ Know Your Rights ” poster..." etc. That's boilerplate; remove.
Also remove "The below represents the expected salary range for this job requisition. Ultimately, in determining your pay, we’ll consider your location, experience, and other job-related factors." That's placeholder; no actual range, so we should not create Pay section. Also we should not include that sentence as it's filler. So drop.
Now craft HTML:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies those are examples; we can use other headings if needed? Probably we should stick to those headings where applicable. The posting includes "Responsibilities", "Qualifications", "About Us", "About The Team". "About Us" could map to "About the role"? Not exactly. But we could treat "About Us" as "About the role"? Might be okay. However "About The Team" could be considered part of benefits? Not exactly. The instruction says prefer few substantive sections over many thin ones. So maybe combine "About Us" and "About The Team" into a single section like "About the role" or "About the team"? But we need to preserve all substantive info. Could create sections: Responsibilities, Qualifications, Benefits (since benefits are listed), maybe "About the role" for introductory paragraphs. Pay and Schedule not present (no salary range given? Actually there is a line: "The below represents the expected salary range for this job requisition." but no actual numbers given, just statement. That's placeholder? It says "The below represents the expected salary range for this job requisition." but no numbers. That's filler? It says not to create Pay/Schedule/Benefits sections unless posting actually states them. Since no actual numbers, we should not create Pay section. Benefits are listed concretely: Competitive base salaries, Bonus incentives, 6% Company Match..., etc. So we should include Benefits section.
We also have "About Us" and "About The Team" which are descriptive about company culture, benefits, etc. Some of that overlaps with Benefits section. We could combine them into an "About the role" section that includes the introductory paragraphs about Amex Tech, GCS, etc. Then Responsibilities, Qualifications, Benefits.
We must not include boilerplate like EEO, equal opportunity, visa sponsorship note? Actually "Employment eligibility to work with American Express in the United States is required as the company will not pursue visa sponsorship for these positions." That's substantive? It's a requirement. Could be part of Qualifications? Might be included there. But it's a legal requirement; maybe we keep it in Qualifications.
We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. The text includes a lot of EEO statements at the end. Remove those.
Also remove "For a full list of Team Amex benefits, visit our Colleague Benefits Site ." That's a link; maybe keep as part of Benefits? It's a reference; we could keep but it's not substantive detail; maybe drop.
Also remove "US Job Seekers - Click to view the “ Know Your Rights ” poster..." etc. That's boilerplate; remove.
Also remove "The below represents the expected salary range for this job requisition. Ultimately, in determining your pay, we’ll consider your location, experience, and other job-related factors." That's placeholder; no actual range, so we should not create Pay section. Also we should not include that sentence as it's filler. So drop.
Now craft HTML:
About the role
Joining Amex Tech means discovering and shaping your contribution to something big. Here, you can work alongside talented tech teams and build a unique career with the Powerful Backing of American Express. With a range of opportunities to work with the latest technologies, and a commitment to back the broader engineering community through open source, our mission is to power your success. Because Amex Tech is powered by our technology, our culture, and our colleagues. The Technology organization enables and accelerates the company’s growth strategies, delivering global capabilities and services in support of Amex’s customers and colleagues, while maintaining 24/7 servicing and availability to ensure an uninterrupted, high-quality customer experience. Technology provides the foundation for everything we do in the company while driving differentiation through building and leveraging innovative technology and data insights. Global Commercial Services (GCS) serves millions of business customers around the world, from mom-and-pop shops to approximately 70% of the S&P 500. We are the number one issuer of small business cards, the industry leader in corporate T&E and represent approximately 40% of the company’s total revenues. Our vision is to be essential to our customers’ businesses every day. We do that by offering a diverse suite of payment and cashflow tools our customers need to run and grow their businesses, from a wide range of traditional card products, to working capital and supply chain financing, to new digital solutions that make it easy for our customers to manage their financial and payment needs.
Responsibilities
- Sr Solutions Architect I leads alignment of technology platforms with company roadmaps, optimizes integration and performance, oversees solution architecture and application programming interface strategy, mentors engineering teams, and collaborates on technical strategy and improvements.
- Mentors junior Solutions Architects and cross-functional team of colleagues, fostering a culture of excellence and innovation
- Identifies and implements technical solutions and business process improvements by analyzing business needs and leveraging innovative technologies
- Collaborates with business partners and product engineering teams to enforce architecture practices, ensuring alignment with architectural and technical strategy through governance and project reviews
- Leads technology platform solutions alignment with platform blueprints and company roadmaps, serving as the Single Point of Contact (SPOC) and coordinating with relevant stakeholders
- Optimizes cross-platform integration implementing advanced integration strategies to enhance platform capabilities, performance, and efficiency
- Ensures the engineered environment meets comprehensive business, application design, and infrastructure requirements by overseeing platform integration performance
- Executes solution architecture design strategies, leads design and code reviews to ensure the delivery of desired business outcomes and adherence to enterprise standards
- Supervises the platform's application programming interface strategy and implementation roadmap by collaborating with business and data architects, incorporating their input into cohesive platform solutions
- Collaborates and co-creates effectively with teams in product and the business to align technology initiatives with business objectives
- Embeds AI-assisted architecture tools into team workflows, improving design analysis, documentation, and platform integration outcomes
- Mentors junior architects on responsible use of AI-enabled tools for solution design, API strategy, and requirement analysis
- Applies AI-assisted capabilities to improve architecture reviews, business process analysis, and technical solution recommendations across the platform
Qualifications
- Hands-on programming experience relevant to the assigned technology platform in a professional environment, and/or comparable experience
- Experience in application solution architecture design and end-to-end software development of complex distributed (multi-tiered) systems
- Experience in multiple technology disciplines with a deep knowledge of architectural concepts (business, data, technical, and solution) and a proven track record of implementation
- Experience in using a systems analysis and design methodology applicable to an Agile product environment
- Experience in relevant software development life cycle methodologies, practices, and compliance policies/procedures
- Experience in solution architecture, complex application systems design, and platform integration via modern approaches (i.e., RESTful application programming interfaces)
- Experience leading adoption of AI-assisted tools within solution architecture or platform integration teams
- Experience using AI-enabled capabilities to improve architecture analysis, design quality, and documentation practices
- Bachelor's Degree in Computer Science, Computer Engineering, Information Systems, and/or comparable experience; advanced degree preferred
- Have passed (or pass within 6 months) a Senior Engineer level DT Technical Assessment in at least one technology discipline relevant to the assigned Technology Platform(s)
- Knowledge of relevant supporting architecture domains required to align and deliver solutions (business, information, application, technical, etc.)
- Knowledge of Service Oriented Architecture design principles, execution patterns, and performance optimization techniques
- Knowledge of current industry best practices regarding solution delivery disciplines
- Knowledge of AI-enabled architecture tools and their application within solution delivery, integration, and documentation workflows
- Understanding of governance considerations for AI-assisted architecture work, including validation of outputs and control of design risk
- Employment eligibility to work with American Express in the United States is required as the company will not pursue visa sponsorship for these positions.
Benefits
- Competitive base salaries
- Bonus incentives
- 6% Company Match on retirement savings plan
- Free financial coaching and financial well-being support
- Comprehensive medical, dental, vision, life insurance, and disability benefits
- Flexible working model with hybrid, onsite or virtual arrangements depending on role and business need
- 20+ weeks paid parental leave for all parents, regardless of gender, offered for pregnancy, adoption or surrogacy
- Free access to global on-site wellness centers staffed with nurses and doctors (depending on location)
- Free and confidential counseling support through our Healthy Minds program
- Career development and training opportunities
before the list. We need to preserve all substantive info. So we should include the "About Us" cultural description somewhere. Perhaps we can add another section like "About the company" but not in allowed headings. However we could incorporate it into About the role section as additional paragraphs. That would be okay: About the role can include both the role description and company culture. So we should extend the About the role paragraph to