Cloud Solutions Architect
FDM Group · Waco, TX · 3 wk ago
HybridEngineeringContract
We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills maybe, Benefits, Pay, Schedule only if present. The posting includes: About The Role (text). Then Key Responsibilities (list). Then About You (Required Experience, Technical Expertise, Preferred Qualifications). Then What Success Looks Like (maybe could be part of responsibilities or separate). Then About FDM (company description). Then Additional Considerations (states). Also mention hybrid schedule: "This role will be hybrid with requirements to be in office 3 days per week." That's schedule info. No explicit pay or benefits. So we should include Schedule section with that detail. Benefits? Not mentioned. Pay? Not mentioned. So we omit those.
We need headings: for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills? Actually we can combine Requirements and Qualifications maybe. The instruction: Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills? Actually we can combine Requirements and Qualifications maybe. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements (maybe combine Required Experience and Technical Expertise), Qualifications (Preferred Qualifications), Skills (maybe technical expertise?), but we need to avoid filler. We need to preserve all substantive info.
We can structure:
About the role
About the role
... (the paragraph about role, W2, FDM, etc.)
Responsibilities
- ... each responsibility
Requirements
... Required Experience bullet points? Could be list.
maybe use- for list.
Qualifications
... Preferred Qualifications bullet list.
Skills
Maybe we can list technical expertise as skills. But we already have Required Experience includes technical expertise. Could combine. But we need to avoid thin sections. Perhaps we can merge Technical Expertise into Requirements as a list. Alternatively we could have sections: About the role, Responsibilities, Requirements (including experience and technical expertise), Qualifications (preferred), Schedule. We need to include Schedule: hybrid 3 days per week. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, equal opportunity, scam warning, etc. Also remove navigation, cookie, legal. Also remove "About FDM" maybe? It's company description; is that substantive? It's about the company, not required for job? Might be considered boilerplate but it's descriptive. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About FDM" is not explicitly listed as boilerplate, but could be considered company overview; maybe we keep it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep About FDM as it's substantive about the company. However, we might not have a heading for it; we could include under a section like "About FDM" but not in the list of headings. The allowed headings list includes only those; but we could still use for About FDM? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. ...)". Likely they expect only those headings. But we could treat About FDM as part of About the role? Might be redundant. However, we need to preserve all substantive info; we could include a paragraph after About the role that includes FDM description. That's fine.
Additional Considerations (states) is also substantive; we could include under a section like "Location / Eligibility" but not in allowed headings. Could we add a heading like "Location"? Not in list but maybe okay. But to be safe, we could incorporate that info into a paragraph under About the role or a new section "Eligibility". The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. I'd include a section for "Location" maybe as Location
. But they didn't list Location as example; but it's not prohibited. However, they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exhaustive. So we can add other headings as needed.
Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Schedule, Location (or Additional Considerations). We'll omit Benefits and Pay.
Now we need to extract content.
Let's parse the posting:
About The Role:
"This position requires the successful candidate to work on a W2 directly with FDM. We cannot accept C2C, 1099 or employment sponsorship (e.g. H1-B) for this position. FDM is a global business and technology consultancy delivering client and industry driven solutions through our 5 core specialist Practices; Software Engineering, Data & Analytics, IT Operations, Change & Transformation, and Risk, Regulation & Compliance. FDM is seeking a Solution Architect located in Waco to support a project in the Insurance sector. Involvement in this project is anticipated to last initially 12 months but may be extended.This role will be hybrid with requirements to be in office 3 days per week. We're are seeking a Lead Solution Architect to design and guide the delivery of enterprise business solutions across the Microsoft technology ecosystem. This role will partner with business and technical stakeholders to translate requirements into practical, scalable solutions and provide the technical leadership needed to ensure successful implementation. The ideal candidate brings deep experience with Microsoft business platforms and can move seamlessly from solution design to implementation oversight, ensuring solutions are secure, supportable, and aligned with business objectives."
Note there is a typo "We're are". We'll keep as is.
Key Responsibilities (list):
- Design end-to-end business solutions leveraging Microsoft technologies.
- Translate business requirements into scalable technical architectures.
- Lead solution reviews, architecture discussions, and proof-of-concept activities.
- Provide technical oversight throughout implementation and serve as the primary architectural authority.
- Transition solution designs to development, engineering, and support teams.
- Establish and maintain platform standards, governance, and best practices.
- Identify opportunities for automation, process improvement, and platform optimization.
- Partner with business leaders, infrastructure teams, developers, and vendors to ensure successful solution delivery.
- Mentor technical teams and serve as a senior escalation point for complex issues.
About You:
Required Experience:
- 7+ years of experience in solution architecture, enterprise applications, platform engineering, or a related technology field.
- Proven experience designing and delivering enterprise business solutions.
- Strong understanding of application architecture, integration, security, and cloud technologies.
- Experience leading solutions from concept through implementation and operational handoff.
- Ability to influence technical decisions and lead without direct authority.
Technical Expertise:
- Experience with several of the following:
- Microsoft Dynamics 365
- Microsoft Teams
- SharePoint / ShareNet
- Power Apps
- Power Automate
- Power BI
- Microsoft Power Platform
- Exchange Online / Microsoft 365
- Microsoft Azure
- Enterprise integrations, APIs, and workflow automation
Preferred Qualifications:
- Microsoft, Azure, Dynamics 365, or Power Platform certifications.
- Agile, Scrum, or SAFe experience.
- Insurance industry experience preferred.
- Experience establishing governance and standards for Microsoft business platforms.
What Success Looks Like:
- Designs practical, scalable Microsoft-based solutions that meet business needs.
- Provides clear direction to implementation teams and drives successful delivery.
- Ensures solutions are secure, supportable, and aligned with enterprise standards.
- Delivers measurable improvements in efficiency, automation, and user experience.
- Serves as a trusted advisor to both business and technical stakeholders.
- This is a senior individual contributor role that combines solution architecture, technical leadership, and implementation oversight across the Microsoft technology ecosystem.
About FDM:
"FDM powers the people behind tech and innovation. We spot trends, find top talent, and help businesses stay ahead. With 35+ years of experience, we coach, mentor, and launch fresh thinkers from diverse backgrounds into world-class careers. Partnering with top global companies, we deliver the right talent at the right time—while guiding our people toward exponential growth. 🌍 Global impact – 18 centers across North America, APAC, the UK, and Europe🚀 25,000+ careers launched – and counting🤝 300+ trusted client partners"
Additional Considerations:
"FDM Group, Inc. is registered to operate and hire employees in select states within the US. We will consider employment applications exclusively from candidates who are either residing in one of the following states or willing to relocate to them: Arizona, California, Colorado, Connecticut, Delaware, Florida, Georgia, Illinois, Indiana, Massachusetts, Maryland, Minnesota, North Carolina, New Jersey, New York, Pennsylvania, Tennessee, Texas, Utah, and Virginia."
We also have schedule info: hybrid 3 days per week.
Now we need to output HTML fragment.
We'll structure:
About the role
for section headings (e.g. ...)". Likely they expect only those headings. But we could treat About FDM as part of About the role? Might be redundant. However, we need to preserve all substantive info; we could include a paragraph after About the role that includes FDM description. That's fine.
Additional Considerations (states) is also substantive; we could include under a section like "Location / Eligibility" but not in allowed headings. Could we add a heading like "Location"? Not in list but maybe okay. But to be safe, we could incorporate that info into a paragraph under About the role or a new section "Eligibility". The instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those are typical. I'd include a section for "Location" maybe as Location
. But they didn't list Location as example; but it's not prohibited. However, they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exhaustive. So we can add other headings as needed.
Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Schedule, Location (or Additional Considerations). We'll omit Benefits and Pay.
Now we need to extract content.
Let's parse the posting:
About The Role:
"This position requires the successful candidate to work on a W2 directly with FDM. We cannot accept C2C, 1099 or employment sponsorship (e.g. H1-B) for this position. FDM is a global business and technology consultancy delivering client and industry driven solutions through our 5 core specialist Practices; Software Engineering, Data & Analytics, IT Operations, Change & Transformation, and Risk, Regulation & Compliance. FDM is seeking a Solution Architect located in Waco to support a project in the Insurance sector. Involvement in this project is anticipated to last initially 12 months but may be extended.This role will be hybrid with requirements to be in office 3 days per week. We're are seeking a Lead Solution Architect to design and guide the delivery of enterprise business solutions across the Microsoft technology ecosystem. This role will partner with business and technical stakeholders to translate requirements into practical, scalable solutions and provide the technical leadership needed to ensure successful implementation. The ideal candidate brings deep experience with Microsoft business platforms and can move seamlessly from solution design to implementation oversight, ensuring solutions are secure, supportable, and aligned with business objectives."
Note there is a typo "We're are". We'll keep as is.
Key Responsibilities (list):
- Design end-to-end business solutions leveraging Microsoft technologies.
- Translate business requirements into scalable technical architectures.
- Lead solution reviews, architecture discussions, and proof-of-concept activities.
- Provide technical oversight throughout implementation and serve as the primary architectural authority.
- Transition solution designs to development, engineering, and support teams.
- Establish and maintain platform standards, governance, and best practices.
- Identify opportunities for automation, process improvement, and platform optimization.
- Partner with business leaders, infrastructure teams, developers, and vendors to ensure successful solution delivery.
- Mentor technical teams and serve as a senior escalation point for complex issues.
About You:
Required Experience:
- 7+ years of experience in solution architecture, enterprise applications, platform engineering, or a related technology field.
- Proven experience designing and delivering enterprise business solutions.
- Strong understanding of application architecture, integration, security, and cloud technologies.
- Experience leading solutions from concept through implementation and operational handoff.
- Ability to influence technical decisions and lead without direct authority.
Technical Expertise:
- Experience with several of the following:
- Microsoft Dynamics 365
- Microsoft Teams
- SharePoint / ShareNet
- Power Apps
- Power Automate
- Power BI
- Microsoft Power Platform
- Exchange Online / Microsoft 365
- Microsoft Azure
- Enterprise integrations, APIs, and workflow automation
Preferred Qualifications:
- Microsoft, Azure, Dynamics 365, or Power Platform certifications.
- Agile, Scrum, or SAFe experience.
- Insurance industry experience preferred.
- Experience establishing governance and standards for Microsoft business platforms.
What Success Looks Like:
- Designs practical, scalable Microsoft-based solutions that meet business needs.
- Provides clear direction to implementation teams and drives successful delivery.
- Ensures solutions are secure, supportable, and aligned with enterprise standards.
- Delivers measurable improvements in efficiency, automation, and user experience.
- Serves as a trusted advisor to both business and technical stakeholders.
- This is a senior individual contributor role that combines solution architecture, technical leadership, and implementation oversight across the Microsoft technology ecosystem.
About FDM:
"FDM powers the people behind tech and innovation. We spot trends, find top talent, and help businesses stay ahead. With 35+ years of experience, we coach, mentor, and launch fresh thinkers from diverse backgrounds into world-class careers. Partnering with top global companies, we deliver the right talent at the right time—while guiding our people toward exponential growth. 🌍 Global impact – 18 centers across North America, APAC, the UK, and Europe🚀 25,000+ careers launched – and counting🤝 300+ trusted client partners"
Additional Considerations:
"FDM Group, Inc. is registered to operate and hire employees in select states within the US. We will consider employment applications exclusively from candidates who are either residing in one of the following states or willing to relocate to them: Arizona, California, Colorado, Connecticut, Delaware, Florida, Georgia, Illinois, Indiana, Massachusetts, Maryland, Minnesota, North Carolina, New Jersey, New York, Pennsylvania, Tennessee, Texas, Utah, and Virginia."
We also have schedule info: hybrid 3 days per week.
Now we need to output HTML fragment.
We'll structure:
About the role
Location
. But they didn't list Location as example; but it's not prohibited. However, they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exhaustive. So we can add other headings as needed.
Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Schedule, Location (or Additional Considerations). We'll omit Benefits and Pay.
Now we need to extract content.
Let's parse the posting:
About The Role:
"This position requires the successful candidate to work on a W2 directly with FDM. We cannot accept C2C, 1099 or employment sponsorship (e.g. H1-B) for this position. FDM is a global business and technology consultancy delivering client and industry driven solutions through our 5 core specialist Practices; Software Engineering, Data & Analytics, IT Operations, Change & Transformation, and Risk, Regulation & Compliance. FDM is seeking a Solution Architect located in Waco to support a project in the Insurance sector. Involvement in this project is anticipated to last initially 12 months but may be extended.This role will be hybrid with requirements to be in office 3 days per week. We're are seeking a Lead Solution Architect to design and guide the delivery of enterprise business solutions across the Microsoft technology ecosystem. This role will partner with business and technical stakeholders to translate requirements into practical, scalable solutions and provide the technical leadership needed to ensure successful implementation. The ideal candidate brings deep experience with Microsoft business platforms and can move seamlessly from solution design to implementation oversight, ensuring solutions are secure, supportable, and aligned with business objectives."
Note there is a typo "We're are". We'll keep as is.
Key Responsibilities (list):
- Design end-to-end business solutions leveraging Microsoft technologies.
- Translate business requirements into scalable technical architectures.
- Lead solution reviews, architecture discussions, and proof-of-concept activities.
- Provide technical oversight throughout implementation and serve as the primary architectural authority.
- Transition solution designs to development, engineering, and support teams.
- Establish and maintain platform standards, governance, and best practices.
- Identify opportunities for automation, process improvement, and platform optimization.
- Partner with business leaders, infrastructure teams, developers, and vendors to ensure successful solution delivery.
- Mentor technical teams and serve as a senior escalation point for complex issues.
About You:
Required Experience:
- 7+ years of experience in solution architecture, enterprise applications, platform engineering, or a related technology field.
- Proven experience designing and delivering enterprise business solutions.
- Strong understanding of application architecture, integration, security, and cloud technologies.
- Experience leading solutions from concept through implementation and operational handoff.
- Ability to influence technical decisions and lead without direct authority.
Technical Expertise:
- Experience with several of the following:
- Microsoft Dynamics 365
- Microsoft Teams
- SharePoint / ShareNet
- Power Apps
- Power Automate
- Power BI
- Microsoft Power Platform
- Exchange Online / Microsoft 365
- Microsoft Azure
- Enterprise integrations, APIs, and workflow automation
Preferred Qualifications:
- Microsoft, Azure, Dynamics 365, or Power Platform certifications.
- Agile, Scrum, or SAFe experience.
- Insurance industry experience preferred.
- Experience establishing governance and standards for Microsoft business platforms.
What Success Looks Like:
- Designs practical, scalable Microsoft-based solutions that meet business needs.
- Provides clear direction to implementation teams and drives successful delivery.
- Ensures solutions are secure, supportable, and aligned with enterprise standards.
- Delivers measurable improvements in efficiency, automation, and user experience.
- Serves as a trusted advisor to both business and technical stakeholders.
- This is a senior individual contributor role that combines solution architecture, technical leadership, and implementation oversight across the Microsoft technology ecosystem.
About FDM:
"FDM powers the people behind tech and innovation. We spot trends, find top talent, and help businesses stay ahead. With 35+ years of experience, we coach, mentor, and launch fresh thinkers from diverse backgrounds into world-class careers. Partnering with top global companies, we deliver the right talent at the right time—while guiding our people toward exponential growth. 🌍 Global impact – 18 centers across North America, APAC, the UK, and Europe🚀 25,000+ careers launched – and counting🤝 300+ trusted client partners"
Additional Considerations:
"FDM Group, Inc. is registered to operate and hire employees in select states within the US. We will consider employment applications exclusively from candidates who are either residing in one of the following states or willing to relocate to them: Arizona, California, Colorado, Connecticut, Delaware, Florida, Georgia, Illinois, Indiana, Massachusetts, Maryland, Minnesota, North Carolina, New Jersey, New York, Pennsylvania, Tennessee, Texas, Utah, and Virginia."
We also have schedule info: hybrid 3 days per week.
Now we need to output HTML fragment.
We'll structure:
About the role
... (combined paragraph)
Responsibilities
- ...
Requirements
- ... (Required Experience items)
Technical Expertise
- ... (list of technologies)
Preferred Qualifications
- ...
What Success Looks Like
- ...
About FDM
...
Location / Eligibility
... (states list)
Schedule
This role is hybrid with a requirement to be in the office 3 days per week.
We need to ensure we don't include filler like "commensurate with experience". Not present. We must not repeat job title as heading. We didn't. We must not put Job ID/requisition numbers as headings. None. We must remove boilerplate: EEO etc. Not present. We must remove duplicated lines. None. We must remove application instructions. None. Now produce HTML. Be careful to escape any special characters? Not needed. Let's craft the About the role paragraph: combine the two paragraphs. Paragraph: "This position requires the successful candidate to work on a W2 directly with FDM. We cannot accept C2C, 1099 or employment sponsorship (e.g. H1-B) for this position. FDM is a global business and technology consultancy delivering client and industry driven solutions through our 5 core specialist Practices; Software Engineering, Data & Analytics, IT Operations, Change & Transformation, and Risk, Regulation & Compliance. FDM is seeking a Solution Architect located in Waco to support a project in the Insurance sector. Involvement in this project is anticipated to last initially 12 months but may be extended. This role will be hybrid with requirements to be in office 3 days per week. We're are seeking a Lead Solution Architect to design and guide the delivery of enterprise business solutions across the Microsoft technology ecosystem. This role will partner with business and technical stakeholders to translate requirements into practical, scalable solutions and provide the technical leadership needed to ensure successful implementation. The ideal candidate brings deep experience with Microsoft business platforms and can move seamlessly from solution design to implementation oversight, ensuring solutions are secure, supportable, and aligned with business objectives." Note there is a double period after "extended.This". We'll keep as is or fix? We should preserve