Solutions Architect

American Amicable Group · Addison, TX · 1 mo ago

EngineeringFull-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. No job title heading. No Job ID. Remove boilerplate: EEO, legal, etc. Also remove "For Student Positions Only" maybe not relevant? It's a section but maybe not needed; but we can include if content present. However we should only include sections with real content. Let's parse the posting: - Intro: "Job Description Solutions Architect - U.S. REMOTE Build the future with us Are you eager to contribute to the purpose of a company that aims to help its clients feel confident and secure about their future? As a Solutions Architect, you will play a key role in defining and communicating a share technical vision for the American Amicable modernization initiative migrating core modules from the mainframe-based Policy Administration System to a modern AWS serverless-first architecture. This position is a great opportunity to showcase your skills and fully realize your potential within a caring and trustworthy company. Here, people and their development are at the heart of our priorities, fostering an environment that encourages collaboration and innovation." That's about the role. Could be "About the role" section. - "What you'll accomplish with us As a Solutions Architect, you'll be at the core of our mission. Here are the main responsibilities:" then bullet list (actually sentences separated by no bullet but we can treat as list). We'll create

for each responsibility. List items: - Lead the architectural design for migrating mainframe modules to AWS serverless services, defining bounded contexts, service boundaries, and integration patterns - Decompose monolithic mainframe functionality into event-driven serverless microservices using Lambda, Step Functions, EventBridge, API Gateway, SQS, SNS, and related AWS services - Work with product teams to create high-level designs for feature requests related to the modernization effort - Collaborate with team leads and product owners to create technical roadmaps in alignment with strategic plans and enterprise standards - Collaborate with the Data Architect to define data migration strategies and select appropriate data stores for modernized services - Establish patterns for coexistence and integration between legacy mainframe systems and new cloud services during the transition period - Prepare and present solution briefs to the ARB Solution Committee for proposed architectural changes - Play a central role in technical, business, and organizational contributions affecting the modernization teams - Solve technical problems of the highest scope, complexity, and ambiguity related to legacy-to-cloud transformation - Look for innovation opportunities between teams with a willingness to experiment and boldly confront problems of large complexity and scope - Ensure that OKR-level goals are aligned across teams involved in the modernization - Guide conversations to remove blockers and encourage collaboration across teams - Demonstrate technical excellence and consistency - Champion all NFR's including Infrastructure as Code, CI/CD automation, and observability best practices - "What could accelerate your success in this role We're looking for someone who:" then bullet list: - Is known for their analytical thinking and problem-solving skills - Stands out for their prior experience converting legacy/mainframe systems to modern cloud-native serverless architectures - Demonstrates strong sense of personal responsibility and accountability - Is recognized for their AWS Solutions Architect Associate certification - Has 5-7 years of principal or senior engineer experience with demonstrated knowledge of software development and technical excellence These could be Requirements or Qualifications. We'll decide: maybe "Requirements" for experience and certification; "Qualifications" for skills? But we can combine. The instruction: Use sections only when posting has real specific content. We'll include "Requirements" and maybe "Skills". Let's map: - Requirements: 5-7 years of principal or senior engineer experience, AWS Solutions Architect Associate certification, prior experience converting legacy/mainframe systems to modern cloud-native serverless architectures. - Skills: analytical thinking, problem-solving, personal responsibility/accountability. But we can also have "Qualifications" maybe same as requirements. To avoid thin sections, we could combine into one "Requirements" covering both experience and skills. However we need to follow instruction: prefer a few substantive sections over many thin ones. So maybe we have sections: About the role, Responsibilities, Requirements, Benefits. Pay and Schedule not mentioned, so omit. Skills maybe not needed separate. Benefits: list: Flexible group insurance plans, Competitive retirement savings plan, Employee share purchase plan, Vacation program, wellness days, and personal development days, Telemedicine services, Employee and Family Assistance Program (EFAP), Ergonomic furniture program, Performance bonus, Discounts on iA products, And much more! Also mention hybrid environment? Actually "Why you'll love working with us" includes: work environment where learning and development merge with collective pursuit of excellence; AI is in everyone's hands...; healthy, safe, fair, inclusive environment; opportunity to work in a hybrid environment, supported by flexibility and access to inspiring and innovative workspaces. Also "For Student Positions Only" but not relevant. Could treat those as Benefits or maybe "Why you'll love working with us" as a section like "About the company" but we only have allowed headings. Could put those under Benefits? But they are not benefits exactly; they are work environment. Could create a section "About the role" already includes some of that. Maybe we can add a section "Work Environment" but not allowed headings. So we must stick to allowed headings. Could incorporate those points into Benefits or About the role. Since Benefits heading is allowed, we can include both tangible benefits and work environment aspects under Benefits. But we should not invent content; we can include them as list items under Benefits. Pay: not specified, so omit. Schedule: not specified (though hybrid environment mentioned but not schedule). So omit. Thus final HTML:
About the role

... (the intro paragraph)

Responsibilities
Requirements
Benefits
Make sure no extra whitespace? It's fine. We need to preserve all substantive information; not invent or summarize away detail. So we must include all details from the posting that are not boilerplate. Let's extract About the role paragraph exactly: "Build the future with us Are you eager to contribute to the purpose of a company that aims to help its clients feel confident and secure about their future? As a Solutions Architect, you will play a key role in defining and communicating a share technical vision for the American Amicable modernization initiative migrating core modules from the mainframe-based Policy Administration System to a modern AWS serverless-first architecture. This position is a great opportunity to showcase your skills and fully realize your potential within a caring and trustworthy company. Here, people and their development are at the heart of our priorities, fostering an environment that encourages collaboration and innovation." But there is a typo "a share technical vision" maybe it's "a share"? We'll keep as is. We also have "Job Description Solutions Architect - U.S. REMOTE" at start but we should not repeat job title as heading. We can include that as part of About the role? Probably we can include the location "U.S. REMOTE" as part of About the role paragraph. But we should not repeat job title as heading; we can include it in paragraph. Thus About the role paragraph: "Solutions Architect - U.S. REMOTE Build the future with us Are you eager to contribute to the purpose of a company that aims to help its clients feel confident and secure about their future? As a Solutions Architect, you will play a key role in defining and communicating a share technical vision for the American Amicable modernization initiative migrating core modules from the mainframe-based Policy Administration System to a modern AWS serverless-first architecture. This position is a great opportunity to showcase your skills and fully realize your potential within a caring and trustworthy company. Here, people and their development are at the heart of our priorities, fostering an environment that encourages collaboration and innovation." We need to ensure we didn't miss any other substantive content: "What you'll accomplish with us As a Solutions Architect, you'll be at the core of our mission. Here are the main responsibilities:" This is intro to responsibilities; we can include as part of Responsibilities section preamble maybe a
before list. But we can just start list; but to preserve all info, we could include a
with that sentence then list. However instruction: Use
for prose. So we can include a
before

Solutions Architect

About the role

Responsibilities

Requirements

Benefits

About the role

Similar jobs