Senior SharePoint Developer
for each section heading. Use - for any list of duties/requirements/benefits, and
for prose.
We need to avoid repeating job title as heading.
We need to drop minor metadata like location, citizenship maybe into a short
or drop it? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So location and citizenship can be folded into a short
. We'll include a paragraph at top maybe.
We need to include sections only when posting has real specific content.
We have:
- About the role: maybe the introductory paragraph describing the role and remote work etc. Could be considered "About the role". We'll put that in
.
- Responsibilities: the Position Description bullet list.
- Requirements: maybe the Position Requirements bullet list.
- Qualifications: the Primary Requirements bullet list (or maybe combine with Requirements). But we have both Position Requirements and Primary Requirements; they overlap. We could treat Position Requirements as "Requirements" and Primary Requirements as "Qualifications". Or we could combine but better to separate.
- Skills: maybe list of specific technical skills: SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform, SPFx, Nintex Automation (K2), PowerShell, Windows Workflow Foundation, Excel services, Visual Studio, Nintex Workflows, Power Platform, Sharegate Migration Tool, .NET technologies with C# and ASP.Net, etc. Could be a Skills section.
But we need to avoid duplication: many of those appear also in requirements. We could still list them under Skills.
We need to preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points.
Let's extract bullet points:
Position Description (responsibilities):
- Designing and developing custom solutions using SharePoint Framework (SPFx), Power Platform, and Microsoft Graph to meet evolving business needs
- Leading the migration of legacy SharePoint environments (e.g., SharePoint SE/2016/2019) to SharePoint Online, ensuring data integrity and minimal disruption
- Building and maintaining Power Automate flows and Power Apps to streamline business processes and improve operational efficiency
- Integrating SharePoint with Microsoft Teams, OneDrive, and other M365 services to enhance collaboration and document management
- Ensuring all solutions align with agency governance policies, security standards, and compliance requirements
Position Requirements (requirements):
- Excellent Customer Focus and Communication skills
- Expert proficiency with SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform
- Hands-on experience with SPFx
- Extensive experience with workflow development with proficiency in Nintex Automation (K2)
- Experience implementing and deploying custom SharePoint features to enhance out of box SharePoint functionality
- Ability to convert business requirements into technical solutions using the appropriate and applicable SharePoint web part(s) using a combination of workflows and Web Development technologies
- SharePoint development experience using PowerShell, Windows Workflow Foundation, and Excel services
- Demonstrated experience utilizing Visual Studio for implementing local and enterprise-wide enhancements and features
- Experience with Nintex Workflows, Power Platform, and Sharegate Migration Tool
- 5 + years of professional development experience using.Net technologies with C# and ASP.Net
Primary Requirements (qualifications):
- 7+ years developing solutions on SharePoint with 4+ years focused on SharePoint Online/SPFx and Power Platform
- 5 + years of professional development experience using.Net technologies with C# and ASP.Net
- Strong Sharepoint SE/2016/2019 and Nintex/K2 experience
- Led enterprise migrations
- Delivered 3+ complex SPFx solutions
- Implemented Power Automate workflows at scale
- Candidates MUST be a US Citizen and be able to obtain a Position of Public Trust Clearance.
- Must not have traveled outside the US for a combined total of 6 months or more in last 5 years and have resided in the US for the last 5 years
Note: Some duplication: US Citizen and clearance appears also earlier. We'll include only once maybe in Qualifications or About the role.
We need to avoid repeating same content. We'll keep US Citizen and clearance in Qualifications (or maybe About the role). The travel restriction also.
Now we need to decide sections:
- About the role: maybe a short paragraph summarizing the role: "We are seeking a Senior SharePoint Developer to join our team of qualified, diverse individuals supporting a Federal Government customer in Rosslyn, VA. This position will allow for remote work throughout the US; however it is preferred that the selected individual lives within driving distance of Arlington VA so that they are able to come into the office if needed." Also include location remote? We'll put that.
- Responsibilities: the Position Description list.
- Requirements: the Position Requirements list (maybe combine with some skills). But we also have Skills section maybe separate.
- Qualifications: the Primary Requirements list (including years, citizenship, clearance, travel).
- Skills: maybe list of specific technical skills: SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform, SPFx, Nintex Automation (K2), PowerShell, Windows Workflow Foundation, Excel services, Visual Studio, Nintex Workflows, Power Platform, Sharegate Migration Tool, .NET technologies with C# and ASP.Net. However many of these are already in Requirements/Qualifications. To avoid duplication, we could decide not to create a Skills section if it would just repeat. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Skills into one section? But we need to follow headings: we can have Requirements and Qualifications. Skills may be redundant. Let's see if we can extract unique skills not covered elsewhere: The Position Requirements includes expert proficiency with SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform; hands-on experience with SPFx; extensive experience with workflow development with proficiency in Nintex Automation (K2); experience implementing and deploying custom SharePoint features; ability to convert business requirements into technical solutions using appropriate SharePoint web part(s) using workflows and Web Development technologies; SharePoint development experience using PowerShell, Windows Workflow Foundation, and Excel services; demonstrated experience utilizing Visual Studio for implementing local and enterprise-wide enhancements and features; experience with Nintex Workflows, Power Platform, and Sharegate Migration Tool; 5+ years of professional development experience using .Net technologies with C# and ASP.Net.
Primary Requirements includes: 7+ years developing solutions on SharePoint with 4+ years focused on SharePoint Online/SPFx and Power Platform; 5+ years of professional development experience using .Net technologies with C# and ASP.Net; Strong Sharepoint SE/2016/2019 and Nintex/K2 experience; Led enterprise migrations; Delivered 3+ complex SPFx solutions; Implemented Power Automate workflows at scale; US Citizen; clearance; travel restriction.
Thus many skills are covered. We could create a Skills section that lists the specific technologies: SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform, SPFx, Nintex Automation (K2), PowerShell, Windows Workflow Foundation, Excel services, Visual Studio, Nintex Workflows, Sharegate Migration Tool, .NET/C#/ASP.NET. But that duplicates content from Requirements. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we put them in Skills section, we are not losing info, just reorganizing. But we also have them in Requirements; we would be duplicating. Duplication is allowed? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It says remove duplicated lines. So we should avoid duplicating the same lines. So we should not repeat the same bullet points in multiple sections. So we need to allocate each piece of info to one section only.
Thus we need to decide where each piece goes.
We have:
- Intro paragraph (About the role)
- Responsibilities (list of duties)
- Requirements (maybe the Position Requirements list)
- Qualifications (Primary Requirements list)
- Skills (maybe we can extract unique technical skills not already captured in Requirements/Qualifications). But many are captured. Let's see if any technical skill is not captured elsewhere: The Position Requirements includes expert proficiency with SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform; hands-on experience with SPFx; extensive experience with workflow development with proficiency in Nintex Automation (K2); experience implementing and deploying custom SharePoint features; ability to convert business requirements into technical solutions using appropriate SharePoint web part(s) using workflows and Web Development technologies; SharePoint development experience using PowerShell, Windows Workflow Foundation, and Excel services; demonstrated experience utilizing Visual Studio for implementing local and enterprise-wide enhancements and features; experience with Nintex Workflows, Power Platform, and Sharegate Migration Tool; 5+ years of professional development experience using .Net technologies with C# and ASP.Net.
Primary Requirements includes: 7+ years developing solutions on SharePoint with 4+ years focused on SharePoint Online/SPFx and Power Platform; 5+ years of professional development experience using .Net technologies with C# and ASP.Net; Strong Sharepoint SE/2016/2019 and Nintex/K2 experience; Led enterprise migrations; Delivered 3+ complex SPFx solutions; Implemented Power Automate workflows at scale; US Citizen; clearance; travel restriction.
Thus the technical skills are largely covered in Position Requirements. The Primary Requirements adds years of experience, leadership, deliverables, etc. So we could treat Position Requirements as "Requirements" and Primary Requirements as "Qualifications". Then we don't need a separate Skills section because the technical skills are already in Requirements. However we might want to highlight specific skills like SPFx, Power Platform, etc. But they are already there.
Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications.
We need to ensure we include all substantive info: intro paragraph, responsibilities list, requirements list, qualifications list (including citizenship, clearance, travel restriction). Also we need to include location remote? The intro paragraph can mention remote work and preferred location.
Let's craft:
About the role
We are seeking a Senior SharePoint Developer to join our team of qualified, diverse individuals supporting a Federal Government customer in Rosslyn, VA. This position
for prose. We need to avoid repeating job title as heading. We need to drop minor metadata like location, citizenship maybe into a short
or drop it? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So location and citizenship can be folded into a short
. We'll include a paragraph at top maybe. We need to include sections only when posting has real specific content. We have: - About the role: maybe the introductory paragraph describing the role and remote work etc. Could be considered "About the role". We'll put that in
. - Responsibilities: the Position Description bullet list. - Requirements: maybe the Position Requirements bullet list. - Qualifications: the Primary Requirements bullet list (or maybe combine with Requirements). But we have both Position Requirements and Primary Requirements; they overlap. We could treat Position Requirements as "Requirements" and Primary Requirements as "Qualifications". Or we could combine but better to separate. - Skills: maybe list of specific technical skills: SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform, SPFx, Nintex Automation (K2), PowerShell, Windows Workflow Foundation, Excel services, Visual Studio, Nintex Workflows, Power Platform, Sharegate Migration Tool, .NET technologies with C# and ASP.Net, etc. Could be a Skills section. But we need to avoid duplication: many of those appear also in requirements. We could still list them under Skills. We need to preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points. Let's extract bullet points: Position Description (responsibilities): - Designing and developing custom solutions using SharePoint Framework (SPFx), Power Platform, and Microsoft Graph to meet evolving business needs - Leading the migration of legacy SharePoint environments (e.g., SharePoint SE/2016/2019) to SharePoint Online, ensuring data integrity and minimal disruption - Building and maintaining Power Automate flows and Power Apps to streamline business processes and improve operational efficiency - Integrating SharePoint with Microsoft Teams, OneDrive, and other M365 services to enhance collaboration and document management - Ensuring all solutions align with agency governance policies, security standards, and compliance requirements Position Requirements (requirements): - Excellent Customer Focus and Communication skills - Expert proficiency with SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform - Hands-on experience with SPFx - Extensive experience with workflow development with proficiency in Nintex Automation (K2) - Experience implementing and deploying custom SharePoint features to enhance out of box SharePoint functionality - Ability to convert business requirements into technical solutions using the appropriate and applicable SharePoint web part(s) using a combination of workflows and Web Development technologies - SharePoint development experience using PowerShell, Windows Workflow Foundation, and Excel services - Demonstrated experience utilizing Visual Studio for implementing local and enterprise-wide enhancements and features - Experience with Nintex Workflows, Power Platform, and Sharegate Migration Tool - 5 + years of professional development experience using.Net technologies with C# and ASP.Net Primary Requirements (qualifications): - 7+ years developing solutions on SharePoint with 4+ years focused on SharePoint Online/SPFx and Power Platform - 5 + years of professional development experience using.Net technologies with C# and ASP.Net - Strong Sharepoint SE/2016/2019 and Nintex/K2 experience - Led enterprise migrations - Delivered 3+ complex SPFx solutions - Implemented Power Automate workflows at scale - Candidates MUST be a US Citizen and be able to obtain a Position of Public Trust Clearance. - Must not have traveled outside the US for a combined total of 6 months or more in last 5 years and have resided in the US for the last 5 years Note: Some duplication: US Citizen and clearance appears also earlier. We'll include only once maybe in Qualifications or About the role. We need to avoid repeating same content. We'll keep US Citizen and clearance in Qualifications (or maybe About the role). The travel restriction also. Now we need to decide sections: - About the role: maybe a short paragraph summarizing the role: "We are seeking a Senior SharePoint Developer to join our team of qualified, diverse individuals supporting a Federal Government customer in Rosslyn, VA. This position will allow for remote work throughout the US; however it is preferred that the selected individual lives within driving distance of Arlington VA so that they are able to come into the office if needed." Also include location remote? We'll put that. - Responsibilities: the Position Description list. - Requirements: the Position Requirements list (maybe combine with some skills). But we also have Skills section maybe separate. - Qualifications: the Primary Requirements list (including years, citizenship, clearance, travel). - Skills: maybe list of specific technical skills: SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform, SPFx, Nintex Automation (K2), PowerShell, Windows Workflow Foundation, Excel services, Visual Studio, Nintex Workflows, Power Platform, Sharegate Migration Tool, .NET technologies with C# and ASP.Net. However many of these are already in Requirements/Qualifications. To avoid duplication, we could decide not to create a Skills section if it would just repeat. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Skills into one section? But we need to follow headings: we can have Requirements and Qualifications. Skills may be redundant. Let's see if we can extract unique skills not covered elsewhere: The Position Requirements includes expert proficiency with SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform; hands-on experience with SPFx; extensive experience with workflow development with proficiency in Nintex Automation (K2); experience implementing and deploying custom SharePoint features; ability to convert business requirements into technical solutions using appropriate SharePoint web part(s) using workflows and Web Development technologies; SharePoint development experience using PowerShell, Windows Workflow Foundation, and Excel services; demonstrated experience utilizing Visual Studio for implementing local and enterprise-wide enhancements and features; experience with Nintex Workflows, Power Platform, and Sharegate Migration Tool; 5+ years of professional development experience using .Net technologies with C# and ASP.Net. Primary Requirements includes: 7+ years developing solutions on SharePoint with 4+ years focused on SharePoint Online/SPFx and Power Platform; 5+ years of professional development experience using .Net technologies with C# and ASP.Net; Strong Sharepoint SE/2016/2019 and Nintex/K2 experience; Led enterprise migrations; Delivered 3+ complex SPFx solutions; Implemented Power Automate workflows at scale; US Citizen; clearance; travel restriction. Thus many skills are covered. We could create a Skills section that lists the specific technologies: SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform, SPFx, Nintex Automation (K2), PowerShell, Windows Workflow Foundation, Excel services, Visual Studio, Nintex Workflows, Sharegate Migration Tool, .NET/C#/ASP.NET. But that duplicates content from Requirements. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we put them in Skills section, we are not losing info, just reorganizing. But we also have them in Requirements; we would be duplicating. Duplication is allowed? The instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It says remove duplicated lines. So we should avoid duplicating the same lines. So we should not repeat the same bullet points in multiple sections. So we need to allocate each piece of info to one section only. Thus we need to decide where each piece goes. We have: - Intro paragraph (About the role) - Responsibilities (list of duties) - Requirements (maybe the Position Requirements list) - Qualifications (Primary Requirements list) - Skills (maybe we can extract unique technical skills not already captured in Requirements/Qualifications). But many are captured. Let's see if any technical skill is not captured elsewhere: The Position Requirements includes expert proficiency with SharePoint SE/2016, SharePoint Online, SharePoint Designer, Power Platform; hands-on experience with SPFx; extensive experience with workflow development with proficiency in Nintex Automation (K2); experience implementing and deploying custom SharePoint features; ability to convert business requirements into technical solutions using appropriate SharePoint web part(s) using workflows and Web Development technologies; SharePoint development experience using PowerShell, Windows Workflow Foundation, and Excel services; demonstrated experience utilizing Visual Studio for implementing local and enterprise-wide enhancements and features; experience with Nintex Workflows, Power Platform, and Sharegate Migration Tool; 5+ years of professional development experience using .Net technologies with C# and ASP.Net. Primary Requirements includes: 7+ years developing solutions on SharePoint with 4+ years focused on SharePoint Online/SPFx and Power Platform; 5+ years of professional development experience using .Net technologies with C# and ASP.Net; Strong Sharepoint SE/2016/2019 and Nintex/K2 experience; Led enterprise migrations; Delivered 3+ complex SPFx solutions; Implemented Power Automate workflows at scale; US Citizen; clearance; travel restriction. Thus the technical skills are largely covered in Position Requirements. The Primary Requirements adds years of experience, leadership, deliverables, etc. So we could treat Position Requirements as "Requirements" and Primary Requirements as "Qualifications". Then we don't need a separate Skills section because the technical skills are already in Requirements. However we might want to highlight specific skills like SPFx, Power Platform, etc. But they are already there. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications. We need to ensure we include all substantive info: intro paragraph, responsibilities list, requirements list, qualifications list (including citizenship, clearance, travel restriction). Also we need to include location remote? The intro paragraph can mention remote work and preferred location. Let's craft:
About the role
We are seeking a Senior SharePoint Developer to join our team of qualified, diverse individuals supporting a Federal Government customer in Rosslyn, VA. This position