Sr. Power Platform Developer – ECM Migration
Alpha Omega · Arlington, VA · 1 mo ago
$126k–$170k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Application Deadline: November 24, 2026" (application instruction). Also remove "NOTE: This role may require nights and weekend migration work..." but schedule info is there; we need to include schedule if present. The note about schedule: "NOTE: This role may require nights and weekend migration work. The schedule will allow for comp time, or flexible scheduling. (e.g. Worked Saturday and Sunday, candidate would take off Monday and Tuesday to balance out the work week and hours.)" That's schedule info. So we need a Schedule section.
Pay: Salary range info present: "The likely salary range for this position is $126,000 - $170,000." Also note about not guarantee. We'll include Pay section with that info.
Benefits: list of benefits present. We'll include Benefits section.
About the role: maybe a paragraph summarizing role. Could use the description after job title: "Alpha Omega is seeking a qualified Microsoft Power Platform, SharePoint Online, and Copilot Developer to join one of our Prime Federal Contracts Remotely in Arlington, VA. Federal Client requires US citizenship. The agency uses Microsoft Power Platform, SharePoint Online, and Microsoft Copilot to connect certified Citizen Developers with tools that automate business processes, improve collaboration, and support mission-critical tasks. Candidates must have proven experience developing in Power Platform, SharePoint Online, and Copilot, including building, configuring, and optimizing solutions that drive business outcomes. In addition to providing guidance and fostering development, candidates should be able to interface with customer leadership and users of all levels, developing, producing, and stewarding well-governed, well-supported enterprise solutions. The Developer will assist with every stage of the development process, as well as give insights and feedback on continuous operations and support. They must work independently, proactively communicate solutions, and self-start problem-solving during development and discovery phases."
That's about the role.
Responsibilities: list from "Key Responsibilities" bullet points. We'll extract each line after "Lead and participate..." etc. We'll put as
for each heading only if content exists. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Application Deadline: November 24, 2026" (application instruction). Also remove "NOTE: This role may require nights and weekend migration work..." but schedule info is there; we need to include schedule if present. The note about schedule: "NOTE: This role may require nights and weekend migration work. The schedule will allow for comp time, or flexible scheduling. (e.g. Worked Saturday and Sunday, candidate would take off Monday and Tuesday to balance out the work week and hours.)" That's schedule info. So we need a Schedule section.
Pay: Salary range info present: "The likely salary range for this position is $126,000 - $170,000." Also note about not guarantee. We'll include Pay section with that info.
Benefits: list of benefits present. We'll include Benefits section.
About the role: maybe a paragraph summarizing role. Could use the description after job title: "Alpha Omega is seeking a qualified Microsoft Power Platform, SharePoint Online, and Copilot Developer to join one of our Prime Federal Contracts Remotely in Arlington, VA. Federal Client requires US citizenship. The agency uses Microsoft Power Platform, SharePoint Online, and Microsoft Copilot to connect certified Citizen Developers with tools that automate business processes, improve collaboration, and support mission-critical tasks. Candidates must have proven experience developing in Power Platform, SharePoint Online, and Copilot, including building, configuring, and optimizing solutions that drive business outcomes. In addition to providing guidance and fostering development, candidates should be able to interface with customer leadership and users of all levels, developing, producing, and stewarding well-governed, well-supported enterprise solutions. The Developer will assist with every stage of the development process, as well as give insights and feedback on continuous operations and support. They must work independently, proactively communicate solutions, and self-start problem-solving during development and discovery phases."
That's about the role.
Responsibilities: list from "Key Responsibilities" bullet points. We'll extract each line after "Lead and participate..." etc. We'll put as - .
Requirements: maybe combine qualifications/experience? The posting has sections: Education Required Qualifications, Experience/Skills, Required Certifications. We could separate into Requirements (maybe experience) and Qualifications (education). But we need to decide which sections to include. The instruction: Prefer a few substantive sections over many thin ones. We can combine similar info. But we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We have content for About the role, Responsibilities, Requirements (experience), Qualifications (education), Skills (maybe technical skills), Benefits, Pay, Schedule.
We must not create sections with filler like "commensurate with experience". We have actual content.
Let's extract:
About the role: as above.
Responsibilities: list:
- Lead and participate in the requirements gathering, design, development, testing, deployment, and retirement phases of Power Platform, SharePoint Online, and Copilot solutions.
- Build custom applications, workflows, and automations using Power Apps, Power Automate, Dataverse, SharePoint Framework (SPFx), and Copilot integrations.
- Develop, maintain, and optimize Copilot extensions, prompts, and conversational experiences to improve productivity and user outcomes.
- Test all developed components independently, documenting tests and results.
- Create comprehensive test plans and perform knowledge transfer to QA teams.
- Document solution architectures, dependencies, deployment procedures, and user-facing guidance.
- Participate in code reviews for Power Platform, SharePoint, Azure Services, and custom connectors.
- Mentor junior developers and delegate tasks as needed while ensuring quality and timely completion.
(Note: The note about nights/weekend migration work is schedule, not responsibility.)
Requirements: Experience/Skills section includes many bullet-like sentences. We'll capture as list.
From "Experience/Skills" paragraph:
- Federal Client requires US citizenship. (maybe include as requirement)
- Must have 5+ years of experience in at least 1 of the following 4 key areas:
- SharePoint Document Management, DMS / Content Management (Enterprise Scale)
- Enterprise Network Share File Analysis (NFS, SMB, etc.)
- Records Management (Enterprise Scale Records Management, Purview, Retention, Lifecycle, Audit, Insider Risk, Etc.)
- Network Share Migration (Enterprise Scale On-Prem to Cloud Migrations)
- 5+ years' experience developing solutions in Microsoft Power Platform (Canvas apps, Model-driven apps, Dataverse, Power BI dashboards & reports, Power Automate).
- 5+ years' experience developing and customizing SharePoint Online solutions (SPFx, JSON, workflows, integration with Power Platform).
- 2+ years' experience developing with Microsoft Copilot (Copilot Studio, prompt engineering, Copilot integration with Power Platform and M365 apps).
- 5+ years as at least two of the following: Power Platform Admin, SharePoint Admin, Azure/Entra ID Admin, Dynamics 365 Admin, Exchange Admin.
- 5-10 years developing solutions with other Microsoft products and related technologies (Microsoft 365, Azure, .NET, JavaScript).
- Experience with solution-based Power Platform development, including ALM and promoting solutions across DEV, QA, and PROD.
- Demonstrated ability to gather and translate business requirements into complex solutions spanning SharePoint Online, Power Platform, and Copilot technologies.
- Strong technical and non-technical documentation skills, including solution architecture, configuration, and user guides.
- Familiarity with custom connectors, Power Platform CoE, AI Builder, Power Virtual Agents, and Power Pages.
- Experience with Azure Entra (Azure AD) Service Principals, Azure resources that integrate with MPP, and Power BI development and publishing.
- Experience working with scripting/programming languages such as PowerShell, .NET, JavaScript, and Python in the context of Power Platform and SharePoint.
- Ability to act as a Subject Matter Expert (SME) on Power Platform, SharePoint Online, and Copilot development, governance, and best practices.
- Excellent oral and written communication skills.
We'll list these as
- .
Qualifications: Education Required Qualifications: "BS/BA in Computer Science, Information Systems Management, Computer Engineering, or similar."
Also maybe certifications: Required Certifications PL-900 required, PL-100, PL-200, or Copilot-related certifications preferred. Could be under Qualifications or Skills. We'll put under Qualifications.
Skills: maybe we could separate technical skills but we already have many in Requirements. Could combine but we need to follow headings list. We could put Skills as a summary of technical proficiencies: maybe list of technologies: Power Platform, SharePoint Online, Copilot, Power Apps, Power Automate, Dataverse, SPFx, JSON, Power BI, PowerShell, .NET, JavaScript, Python, Azure, etc. But we must not invent. We can extract from Requirements the specific technologies mentioned. However that may duplicate. Perhaps better to treat Requirements as experience, Qualifications as education+certifications, Skills as technical abilities (like "Power Platform Admin", "SharePoint Admin", etc). But risk of duplication.
Given instruction to prefer few substantive sections, we could merge Requirements and Qualifications into one section called Requirements (or Qualifications). But we must use headings only if content exists. We could choose to include About the role, Responsibilities, Requirements (covering experience, education, certifications), Benefits, Pay, Schedule. That's 5 sections. That seems reasonable and avoids thin sections.
Thus we will not include separate Qualifications or Skills headings.
We need to ensure we don't repeat job title. We'll not include any heading for job title.
We'll output HTML fragment:
About the role
...
Responsibilities
...
Requirements
...
Benefits
...
Pay
The likely salary range for this position is $126,000 - $170,000. This is not, however, a guarantee of compensation or salary.
Schedule
This role may require nights and weekend migration work. The schedule allows for comp time or flexible scheduling (e.g., working Saturday and Sunday could be balanced by taking Monday and Tuesday off).
We must ensure we preserve all substantive information. Let's verify we didn't drop any important info.
From About the role we captured the paragraph after job title. Did we miss any details like "Hybrid, Arlington, VA" location? That's location info; maybe we should include in About the role or a separate section? The instruction says we can include location in About the role. It's substantive. We'll add location: "Hybrid, Arlington, VA". Also mention "Federal Client requires US citizenship." Already in About the role? We included that. Good.
We also need to include "Clearance Required: Public Trust". That's a requirement. Should be in Requirements. We'll add.
Also "Work Location: Hybrid, Arlington, VA". Already.
Also "Alpha Omega is seeking a qualified Microsoft Power Platform, SharePoint Online, and Copilot Developer to join one of our Prime Federal Contracts Remotely in Arlington, VA." Already.
Also "The agency uses Microsoft Power Platform, SharePoint Online, and Microsoft Copilot to connect certified Citizen Developers with tools that automate business processes, improve collaboration, and support mission-critical tasks." Already.
Also "Candidates must have proven experience developing in Power Platform, SharePoint Online, and Copilot, including building, configuring, and optimizing solutions that drive business outcomes." Already.
Also "In addition to providing guidance and fostering development, candidates should be able to interface with customer leadership and users of all levels, developing, producing, and stewarding well-governed, well-supported enterprise solutions." Already.
Also "The Developer will assist with every stage of the development process, as well as give insights and feedback on continuous operations and support. They must work independently, proactively communicate solutions, and self-start problem-solving during development and discovery phases." Already.
Now Responsibilities list we captured.
Now Requirements list: need to include:
- Clearance Required: Public Trust.
- Federal Client requires US citizenship.
- Must have 5+ years of experience in at least 1 of the following 4 key areas: (list)
- 5+ years' experience developing solutions in Microsoft Power Platform (Canvas apps, Model-driven apps, Dataverse, Power BI dashboards & reports, Power Automate).
- 5+ years' experience developing and customizing SharePoint Online solutions (SPFx, JSON, workflows, integration with Power Platform).
- 2+ years' experience developing with Microsoft Copilot (Copilot Studio, prompt engineering, Copilot integration with Power Platform and M365 apps).
- 5+ years as at least two of the following: Power Platform Admin, SharePoint Admin, Azure/Entra ID Admin, Dynamics 365 Admin, Exchange Admin.
- 5-10 years developing solutions with other Microsoft products and related technologies (Microsoft 365, Azure, .NET, JavaScript).
- Experience with solution-based Power Platform development, including ALM and promoting solutions across DEV, QA, and PROD.
- Demonstrated ability to gather and translate business requirements into complex solutions spanning SharePoint Online, Power Platform, and Copilot technologies.
- Strong technical and non-technical documentation skills, including solution architecture, configuration, and user guides.
- Familiarity with
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
- ...
Pay
The likely salary range for this position is $126,000 - $170,000. This is not, however, a guarantee of compensation or salary.
Schedule
This role may require nights and weekend migration work. The schedule allows for comp time or flexible scheduling (e.g., working Saturday and Sunday could be balanced by taking Monday and Tuesday off).
We must ensure we preserve all substantive information. Let's verify we didn't drop any important info. From About the role we captured the paragraph after job title. Did we miss any details like "Hybrid, Arlington, VA" location? That's location info; maybe we should include in About the role or a separate section? The instruction says we can include location in About the role. It's substantive. We'll add location: "Hybrid, Arlington, VA". Also mention "Federal Client requires US citizenship." Already in About the role? We included that. Good. We also need to include "Clearance Required: Public Trust". That's a requirement. Should be in Requirements. We'll add. Also "Work Location: Hybrid, Arlington, VA". Already. Also "Alpha Omega is seeking a qualified Microsoft Power Platform, SharePoint Online, and Copilot Developer to join one of our Prime Federal Contracts Remotely in Arlington, VA." Already. Also "The agency uses Microsoft Power Platform, SharePoint Online, and Microsoft Copilot to connect certified Citizen Developers with tools that automate business processes, improve collaboration, and support mission-critical tasks." Already. Also "Candidates must have proven experience developing in Power Platform, SharePoint Online, and Copilot, including building, configuring, and optimizing solutions that drive business outcomes." Already. Also "In addition to providing guidance and fostering development, candidates should be able to interface with customer leadership and users of all levels, developing, producing, and stewarding well-governed, well-supported enterprise solutions." Already. Also "The Developer will assist with every stage of the development process, as well as give insights and feedback on continuous operations and support. They must work independently, proactively communicate solutions, and self-start problem-solving during development and discovery phases." Already. Now Responsibilities list we captured. Now Requirements list: need to include: - Clearance Required: Public Trust. - Federal Client requires US citizenship. - Must have 5+ years of experience in at least 1 of the following 4 key areas: (list) - 5+ years' experience developing solutions in Microsoft Power Platform (Canvas apps, Model-driven apps, Dataverse, Power BI dashboards & reports, Power Automate). - 5+ years' experience developing and customizing SharePoint Online solutions (SPFx, JSON, workflows, integration with Power Platform). - 2+ years' experience developing with Microsoft Copilot (Copilot Studio, prompt engineering, Copilot integration with Power Platform and M365 apps). - 5+ years as at least two of the following: Power Platform Admin, SharePoint Admin, Azure/Entra ID Admin, Dynamics 365 Admin, Exchange Admin. - 5-10 years developing solutions with other Microsoft products and related technologies (Microsoft 365, Azure, .NET, JavaScript). - Experience with solution-based Power Platform development, including ALM and promoting solutions across DEV, QA, and PROD. - Demonstrated ability to gather and translate business requirements into complex solutions spanning SharePoint Online, Power Platform, and Copilot technologies. - Strong technical and non-technical documentation skills, including solution architecture, configuration, and user guides. - Familiarity with