Senior Power Platform Solutions Architect
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to extract substantive content: Overview (company description) could be "About the role"? Actually "Overview" is about the company and mission. Could be considered "About the role"? Might be better to have "About the role" section summarizing the role description: The role is Senior Power Platform Solutions Architect supporting Army T2COM mission, hybrid position in Fort Eustis, Virginia. Provide technical leadership etc. That's covered in Responsibilities. So maybe we can have sections: Responsibilities, Qualifications, Benefits, Pay. Also maybe "Skills" could be derived from qualifications but we can keep Qualifications.
We must not create sections with filler. Pay is given: Pay range $150,000 - $170,000 annually. So we can have a Pay section with that info. Benefits: they list benefit package: Medical, dental and vision plans, Life Insurance, Short Term Disability insurance (where applicable), Voluntary ancillary benefit options, 401k retirement benefits with employer matching contributions. Also mention they comply with benefit and pay transparency laws. So we can have Benefits section with those items as list.
Schedule: Not mentioned (hybrid position but not schedule specifics). So we should not create Schedule section.
Skills: Could be derived from qualifications but we might not need separate Skills section if Qualifications covers. The instruction says prefer few substantive sections over many thin ones. So we can have Responsibilities, Qualifications, Benefits, Pay. Possibly also "About the role" could be omitted if we have Responsibilities covering role description. But we might include a brief overview as About the role: The company description and role location. However that might be considered filler? The overview includes company description which is substantive. Could be placed under About the role. But we already have Responsibilities covering duties. The overview is about company and mission; maybe we can put that in a short paragraph under About the role.
Let's decide: Include About the role (company overview and position location/hybrid). Then Responsibilities (list). Then Qualifications (list). Then Benefits (list). Then Pay (maybe a paragraph). Avoid duplication.
Now we need to strip boilerplate: EEO, application instructions, contact info, etc. Also remove duplicated lines. Also remove "Benefit And Compensation Transparency" heading? We'll keep benefits and pay.
We need to preserve all substantive information: So we need to include details like location Fort Eustis, Virginia, hybrid position, supporting U.S. Army T2COM mission, etc. Those are in Responsibilities overview. Also mention "Serve as the senior technical architect and subject-matter expert..." etc. All those are responsibilities.
Qualifications: Bachelor's degree, 8+ years experience, 5+ years hands-on Power Platform, strong experience with list, demonstrated experience designing enterprise-scale solutions, experience developing architecture docs, strong understanding of application security, experience with Power Platform ALM, experience working in DoD/federal, ability to communicate, etc. Also Preferred Qualifications list: certifications, Azure, experience supporting Army, DoD RMF, etc., experience with Azure Government, Azure Functions, Logic Apps, API Management, Azure SQL, Azure DevOps, establishing CoE, Active Secret security clearance.
We need to include all that. Should we separate Preferred Qualifications? Could be part of Qualifications section as a list with note "Preferred". But we can keep as part of Qualifications.
We need to use
- for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Qualifications we need a list. For Benefits we need a list.
We need to use
for prose. So any paragraph text not in list goes in
.
We must not repeat job title as heading. So no
Senior Power Platform Solutions Architect
. Good.
We must not include Job ID/requisition numbers.
We must not include application instructions, EEO, contact info, etc.
Now craft HTML.
Structure:
About the role
ITA International is a tech-enabled professional services company headquartered in Newport News, Virginia, with a global presence and over 200 employees. The company leverages subject‑matter expertise, data analytics, and technology to deliver mission‑focused solutions for customers. This position is for a Senior Power Platform Solutions Architect supporting the U.S. Army T2COM mission, located in Fort Eustis, Virginia, in a hybrid work arrangement.
Responsibilities
- Provide technical leadership and enterprise‑level architecture expertise for the design, development, integration, deployment, and sustainment of solutions built on the Microsoft Power Platform (Power Apps, Power Automate, Power BI, Co‑Pilot Studio, Dataverse) and related Microsoft 365 and Azure services.
- Work closely with government stakeholders, functional leaders, developers, data professionals, cybersecurity personnel, and other technical teams to translate mission requirements into secure, scalable, maintainable, and enterprise‑ready solutions.
- Help establish and enforce Power Platform architecture standards, governance, application lifecycle management, security practices, and development methodologies appropriate for a DoD environment.
- Serve as the senior technical architect and subject‑matter expert for Microsoft Power Platform solutions supporting Army T2COM mission requirements.
- Lead the architecture, design, and implementation of enterprise Power Apps, Power Automate workflows, Power BI analytics, Co‑Pilot studio, Dataverse solutions, and integrations with Microsoft 365, Azure, and enterprise systems.
- Translate complex operational and business requirements into scalable technical architectures and actionable implementation plans.
- Develop solution architectures, technical designs, integration patterns, data models, system interfaces, and implementation roadmaps.
- Establish Power Platform architecture and development standards that promote scalability, maintainability, security, performance, and reuse.
- Design solutions that align with Army, DoD, and organizational cybersecurity, data governance, identity, and compliance requirements.
- Provide technical leadership across the full application lifecycle, including requirements analysis, architecture, development, testing, deployment, operations, and sustainment.
- Develop and implement Application Lifecycle Management (ALM) practices using appropriate Power Platform environments, solutions, pipelines, source control, and deployment methodologies.
- Establish and maintain Power Platform governance, including environment strategy, data loss prevention policies, connector management, security roles, licensing considerations, and administrative controls.
- Assess existing applications and workflows for modernization opportunities, technical debt, performance issues, security concerns, and opportunities for consolidation or reuse.
- Lead integration efforts between Power Platform and enterprise applications, databases, APIs, Azure services, Microsoft 365, and other mission systems.
- Partner with cybersecurity and infrastructure teams to ensure solutions meet applicable RMF, STIG, Zero Trust, identity/access management, and security control requirements.
- Develop and maintain architecture documentation, system diagrams, interface specifications, technical standards, and other engineering artifacts.
- Collaborate with government leadership and mission stakeholders to prioritize technical initiatives and align Power Platform capabilities with organizational objectives.
- Architect secure API and custom connector integrations, defining authentication and authorization patterns—including OAuth and app registrations—and guiding teams through Swagger/OpenAPI, URLs, access requirements, and proactive resolution of integration challenges.
- Define Power Platform environment, deployment, and integration strategies, leveraging the Power Platform Admin Center, Dataverse, gateways, security capabilities, and application connections across Azure, AWS, Palantir, and other enterprise data platforms.
- Monitor Microsoft Power Platform and Azure capabilities and recommend new technologies and services that provide measurable mission value.
- Support transition of solutions into production and provide technical oversight for sustainment and continuous improvement activities.
Qualifications
- Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related technical discipline, or equivalent professional experience.
- 8+ years of experience in software engineering, enterprise architecture, cloud architecture, or related technical disciplines.
- 5+ years of hands‑on experience designing and implementing Microsoft Power Platform solutions.
- Strong experience with Microsoft Power Apps, Power Automate, Power BI, Dataverse, Power Platform administration and governance, Microsoft 365, Azure services and integrations, REST APIs and system integration, data modeling and relational databases.
- Demonstrated experience designing enterprise‑scale solutions rather than solely developing individual applications or workflows.
- Experience developing architecture documentation, technical designs, integration diagrams, and implementation strategies.
- Strong understanding of application security, identity and access management, data protection, and enterprise governance.
- Experience with Power Platform ALM, including environments, solutions, deployment pipelines, source control, and release management.
- Experience working in a DoD, federal government, or similarly regulated environment.
- Ability to communicate complex technical concepts to both technical and non‑technical stakeholders.
- Strong analytical, problem‑solving, communication, and technical leadership skills.
- Preferred qualifications:
- Microsoft Power Platform Solution Architect certification or comparable Microsoft certification.
- Microsoft Certified: Power Platform Functional Consultant, Developer, or related certification.
- Azure Solutions Architect Expert or related Azure certification.
- Experience supporting U.S. Army, Department of Defense, or other federal mission environments.
- Experience with DoD RMF, DISA STIGs, FedRAMP, FISMA, NIST, Zero Trust Architecture, or related security/compliance frameworks.
- Experience implementing Power Platform within an Azure Government or other government cloud environment.
- Experience with Azure Functions, Logic Apps, API Management, Azure SQL, Azure DevOps, and/or other Azure integration technologies.
- Experience establishing enterprise Power Platform Center of Excellence (CoE) capabilities.
- Active Secret security clearance.
But note: nested inside is not ideal but allowed. However we could keep Preferred Qualifications as a separate after a note. But instruction: use
- for any list. So we can have a
for "Preferred qualifications:" then a
. That's fine.
We need to avoid duplicate content. Ensure we didn't repeat.
Now Benefits section:
Benefits
- Medical, dental and vision plans
- Life Insurance
- Short Term Disability insurance (where applicable)
- Voluntary ancillary benefit options
- 401k retirement benefits with employer matching contributions
Pay section:
Pay
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to extract substantive content: Overview (company description) could be "About the role"? Actually "Overview" is about the company and mission. Could be considered "About the role"? Might be better to have "About the role" section summarizing the role description: The role is Senior Power Platform Solutions Architect supporting Army T2COM mission, hybrid position in Fort Eustis, Virginia. Provide technical leadership etc. That's covered in Responsibilities. So maybe we can have sections: Responsibilities, Qualifications, Benefits, Pay. Also maybe "Skills" could be derived from qualifications but we can keep Qualifications. We must not create sections with filler. Pay is given: Pay range $150,000 - $170,000 annually. So we can have a Pay section with that info. Benefits: they list benefit package: Medical, dental and vision plans, Life Insurance, Short Term Disability insurance (where applicable), Voluntary ancillary benefit options, 401k retirement benefits with employer matching contributions. Also mention they comply with benefit and pay transparency laws. So we can have Benefits section with those items as list. Schedule: Not mentioned (hybrid position but not schedule specifics). So we should not create Schedule section. Skills: Could be derived from qualifications but we might not need separate Skills section if Qualifications covers. The instruction says prefer few substantive sections over many thin ones. So we can have Responsibilities, Qualifications, Benefits, Pay. Possibly also "About the role" could be omitted if we have Responsibilities covering role description. But we might include a brief overview as About the role: The company description and role location. However that might be considered filler? The overview includes company description which is substantive. Could be placed under About the role. But we already have Responsibilities covering duties. The overview is about company and mission; maybe we can put that in a short paragraph under About the role. Let's decide: Include About the role (company overview and position location/hybrid). Then Responsibilities (list). Then Qualifications (list). Then Benefits (list). Then Pay (maybe a paragraph). Avoid duplication. Now we need to strip boilerplate: EEO, application instructions, contact info, etc. Also remove duplicated lines. Also remove "Benefit And Compensation Transparency" heading? We'll keep benefits and pay. We need to preserve all substantive information: So we need to include details like location Fort Eustis, Virginia, hybrid position, supporting U.S. Army T2COM mission, etc. Those are in Responsibilities overview. Also mention "Serve as the senior technical architect and subject-matter expert..." etc. All those are responsibilities. Qualifications: Bachelor's degree, 8+ years experience, 5+ years hands-on Power Platform, strong experience with list, demonstrated experience designing enterprise-scale solutions, experience developing architecture docs, strong understanding of application security, experience with Power Platform ALM, experience working in DoD/federal, ability to communicate, etc. Also Preferred Qualifications list: certifications, Azure, experience supporting Army, DoD RMF, etc., experience with Azure Government, Azure Functions, Logic Apps, API Management, Azure SQL, Azure DevOps, establishing CoE, Active Secret security clearance. We need to include all that. Should we separate Preferred Qualifications? Could be part of Qualifications section as a list with note "Preferred". But we can keep as part of Qualifications. We need to use
- for any list of duties/requirements/benefits. So for Responsibilities we need a list. For Qualifications we need a list. For Benefits we need a list.
We need to use
for prose. So any paragraph text not in list goes in
. We must not repeat job title as heading. So no
Senior Power Platform Solutions Architect
. Good. We must not include Job ID/requisition numbers. We must not include application instructions, EEO, contact info, etc. Now craft HTML. Structure:About the role
ITA International is a tech-enabled professional services company headquartered in Newport News, Virginia, with a global presence and over 200 employees. The company leverages subject‑matter expertise, data analytics, and technology to deliver mission‑focused solutions for customers. This position is for a Senior Power Platform Solutions Architect supporting the U.S. Army T2COM mission, located in Fort Eustis, Virginia, in a hybrid work arrangement.
Responsibilities
- Provide technical leadership and enterprise‑level architecture expertise for the design, development, integration, deployment, and sustainment of solutions built on the Microsoft Power Platform (Power Apps, Power Automate, Power BI, Co‑Pilot Studio, Dataverse) and related Microsoft 365 and Azure services.
- Work closely with government stakeholders, functional leaders, developers, data professionals, cybersecurity personnel, and other technical teams to translate mission requirements into secure, scalable, maintainable, and enterprise‑ready solutions.
- Help establish and enforce Power Platform architecture standards, governance, application lifecycle management, security practices, and development methodologies appropriate for a DoD environment.
- Serve as the senior technical architect and subject‑matter expert for Microsoft Power Platform solutions supporting Army T2COM mission requirements.
- Lead the architecture, design, and implementation of enterprise Power Apps, Power Automate workflows, Power BI analytics, Co‑Pilot studio, Dataverse solutions, and integrations with Microsoft 365, Azure, and enterprise systems.
- Translate complex operational and business requirements into scalable technical architectures and actionable implementation plans.
- Develop solution architectures, technical designs, integration patterns, data models, system interfaces, and implementation roadmaps.
- Establish Power Platform architecture and development standards that promote scalability, maintainability, security, performance, and reuse.
- Design solutions that align with Army, DoD, and organizational cybersecurity, data governance, identity, and compliance requirements.
- Provide technical leadership across the full application lifecycle, including requirements analysis, architecture, development, testing, deployment, operations, and sustainment.
- Develop and implement Application Lifecycle Management (ALM) practices using appropriate Power Platform environments, solutions, pipelines, source control, and deployment methodologies.
- Establish and maintain Power Platform governance, including environment strategy, data loss prevention policies, connector management, security roles, licensing considerations, and administrative controls.
- Assess existing applications and workflows for modernization opportunities, technical debt, performance issues, security concerns, and opportunities for consolidation or reuse.
- Lead integration efforts between Power Platform and enterprise applications, databases, APIs, Azure services, Microsoft 365, and other mission systems.
- Partner with cybersecurity and infrastructure teams to ensure solutions meet applicable RMF, STIG, Zero Trust, identity/access management, and security control requirements.
- Develop and maintain architecture documentation, system diagrams, interface specifications, technical standards, and other engineering artifacts.
- Collaborate with government leadership and mission stakeholders to prioritize technical initiatives and align Power Platform capabilities with organizational objectives.
- Architect secure API and custom connector integrations, defining authentication and authorization patterns—including OAuth and app registrations—and guiding teams through Swagger/OpenAPI, URLs, access requirements, and proactive resolution of integration challenges.
- Define Power Platform environment, deployment, and integration strategies, leveraging the Power Platform Admin Center, Dataverse, gateways, security capabilities, and application connections across Azure, AWS, Palantir, and other enterprise data platforms.
- Monitor Microsoft Power Platform and Azure capabilities and recommend new technologies and services that provide measurable mission value.
- Support transition of solutions into production and provide technical oversight for sustainment and continuous improvement activities.
Qualifications
- Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related technical discipline, or equivalent professional experience.
- 8+ years of experience in software engineering, enterprise architecture, cloud architecture, or related technical disciplines.
- 5+ years of hands‑on experience designing and implementing Microsoft Power Platform solutions.
- Strong experience with Microsoft Power Apps, Power Automate, Power BI, Dataverse, Power Platform administration and governance, Microsoft 365, Azure services and integrations, REST APIs and system integration, data modeling and relational databases.
- Demonstrated experience designing enterprise‑scale solutions rather than solely developing individual applications or workflows.
- Experience developing architecture documentation, technical designs, integration diagrams, and implementation strategies.
- Strong understanding of application security, identity and access management, data protection, and enterprise governance.
- Experience with Power Platform ALM, including environments, solutions, deployment pipelines, source control, and release management.
- Experience working in a DoD, federal government, or similarly regulated environment.
- Ability to communicate complex technical concepts to both technical and non‑technical stakeholders.
- Strong analytical, problem‑solving, communication, and technical leadership skills.
- Preferred qualifications:
- Microsoft Power Platform Solution Architect certification or comparable Microsoft certification.
- Microsoft Certified: Power Platform Functional Consultant, Developer, or related certification.
- Azure Solutions Architect Expert or related Azure certification.
- Experience supporting U.S. Army, Department of Defense, or other federal mission environments.
- Experience with DoD RMF, DISA STIGs, FedRAMP, FISMA, NIST, Zero Trust Architecture, or related security/compliance frameworks.
- Experience implementing Power Platform within an Azure Government or other government cloud environment.
- Experience with Azure Functions, Logic Apps, API Management, Azure SQL, Azure DevOps, and/or other Azure integration technologies.
- Experience establishing enterprise Power Platform Center of Excellence (CoE) capabilities.
- Active Secret security clearance.
- inside
- for any list. So we can have a
for "Preferred qualifications:" then a
- . That's fine.
We need to avoid duplicate content. Ensure we didn't repeat.
Now Benefits section:
- Medical, dental and vision plans
- Life Insurance
- Short Term Disability insurance (where applicable)
- Voluntary ancillary benefit options
- 401k retirement benefits with employer matching contributions
Benefits
Pay
- is not ideal but allowed. However we could keep Preferred Qualifications as a separate
- after a
note. But instruction: use