SharePoint/PowerApp Developer
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 etc. 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.
We need to decide which sections to include. The posting includes:
- About Saliense (company description) – could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Saliense" describing company. Could we treat that as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can adapt: we have a company overview; maybe we can put under "About the role"? But that might be inaccurate. However we must not invent sections; we can include a section only if posting has real specific content for it. The posting does have a company description; we could put that under a heading like "About Saliense" but that's not in the allowed list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. So we should map content to those headings.
We have:
- Responsibilities: the list under "Roles & Responsibilities". That's a list of duties. So we can have Responsibilities
with - items.
- Qualifications: the list under "Qualifications". That's qualifications. So
Qualifications
with list.
- Benefits: the bullet list under "About Saliense" includes benefits: 20 Days PTO + 40 Hours of Paid Sick & Safe Time, 11 Federal Holidays + 2 Corporate Holidays, Health, Vision, Dental, and Life Insurance, 401(k) with Tiered Match & 100% Vesting, Parental Leave for Birthing and Non-Birthing Parents, Professional Development Reimbursement Program. Also mention "competitive compensation and benefits". So we can have Benefits
with list.
- Pay: Salary Range: $100,000 - $115,000. So we can have Pay
with containing that range and maybe note about factors.
- Schedule: "This position with be 5 days a week onsite in Chambersburg, PA." So schedule: 5 days a week onsite. So
Schedule
with .
- About the role: maybe we can include a brief prose about the role? The posting includes a paragraph about Saliense (company) and then "Join us at Saliense...". That's more about company. Could treat as "About the role"? Might be okay. But we already have responsibilities and qualifications; we could also have a short paragraph summarizing the role purpose. However the instruction: Prefer a few substantive sections over many thin ones. We already have Responsibilities, Qualifications, Benefits, Pay, Schedule. That's five sections. Adding About the role may be thin. But we could incorporate the company description into Benefits? No. Could we omit About the role section? The instruction says include a section ONLY when the posting has real, specific content for it. The posting does have a paragraph about Saliense and encouraging employees, etc. That's not exactly about the role but could be considered "About the role"? Might be considered filler? It's not boilerplate; it's substantive about company culture. Could be placed under a heading like "About Saliense" but not in allowed list. However we could treat it as "About the role" albeit not perfect but acceptable. 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 as examples. Safer to stick to those headings. We can put the company description under "About the role". It's not exactly about the role but it's the only place to put that prose. It's not filler; it's specific content about the company and its values. So we will include About the role
with
containing that paragraph.
We must not repeat the job title as a heading. No job title given explicitly; we can ignore.
We must not include duplicated lines, cookie/navigation/legal/EEO etc. There's none.
We must not include application instructions. None.
We must not include placeholder text like "commensurate with experience". Not present.
We need to preserve ALL substantive information. So we need to include all bullet points from responsibilities, qualifications, benefits, pay, schedule, and the company description.
We need to format lists as
- . For benefits, we have a list; we can bullet each.
For responsibilities, many items; each as
- .
For qualifications, many items; each as
- .
We need to ensure we don't lose any details.
Let's extract the content.
Company description paragraph:
"About Saliense At Saliense, we are committed to fostering a culture of continuous learning and professional growth. Our employees are encouraged to take on challenging and meaningful work, with ample opportunities for career advancement. We offer competitive compensation and benefits, including: 20 Days PTO + 40 Hours of Paid Sick & Safe Time11 Federal Holidays + 2 Corporate HolidaysHealth, Vision, Dental, and Life Insurance401(k) with Tiered Match & 100% VestingParental Leave for Birthing and Non-Birthing ParentsProfessional Development Reimbursement Program We believe in empowering our team members to achieve their professional goals while contributing to impactful projects that make a difference. Join us at Saliense and be part of a growing organization dedicated to innovation, collaboration, and excellence. Visit www.saliense.com to learn more. There are many more - connect with us to get a preview of the full benefits package."
Note there are some missing spaces: "Safe Time11 Federal Holidays" etc. We need to preserve as is? Probably we should keep the text but maybe add spaces for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the exact text, but we can fix obvious typos? The missing space is likely a formatting error; but preserving exactly might be required. However we could add a space to make it readable but that would be altering. I'd keep as is but maybe add a space after "Time" before "11"? The original: "20 Days PTO + 40 Hours of Paid Sick & Safe Time11 Federal Holidays + 2 Corporate Holidays". It's missing a space. If we keep exactly, it's "Safe Time11". That seems odd but it's the source. I'd keep exactly as given.
Similarly "Health, Vision, Dental, and Life Insurance401(k)" missing space. We'll keep as is.
We'll just copy the paragraph as is.
Now Responsibilities list:
- Design, develop, and maintain custom Power Apps solutions, including canvas apps, model-driven apps, and portals, to support mission-critical business processes.
- Create, configure, and manage SharePoint Online sites, document libraries, lists, and content types to enable effective collaboration and information management.
- Build and optimize automated workflows using Power Automate to handle approvals, notifications, task assignments, and other business processes.
- Integrate Power Apps and SharePoint solutions with Microsoft Dataverse, SQL databases, REST APIs, and other Microsoft 365 tools to ensure seamless data flow.
- Configure and manage data connections, implement validation rules, and ensure real-time data synchronization across systems and applications.
- Customize the user interface and user experience of SharePoint sites and Power Apps to align with organizational branding and usability standards.
- Collaborate closely with stakeholders to gather, analyze, and refine business requirements and translate them into technical specifications and solution designs.
- Develop and maintain comprehensive technical documentation, including solution designs, data models, configuration details, and support procedures.
- Create user guides, job aids, and training materials to support adoption and ongoing use of Power Apps and SharePoint solutions.
- Conduct training sessions, demonstrations, and knowledge-transfer activities to ensure end-users and stakeholders are proficient with deployed tools.
- Integrate Power Apps and SharePoint data with Power BI to develop dashboards and reports that measure solution performance and business impact.
- Monitor, troubleshoot, and optimize existing solutions to improve performance, reliability, and user experience.
- Ensure all solutions and development practices align with NRE organizational goals, mission objectives, and applicable security and compliance requirements.
- Collaborate with cross-functional teams, including security, infrastructure, and operations, to support deployments, upgrades, and platform enhancements.
Note: There's a typo "NRE" maybe should be "NR"? but we keep.
Now Qualifications list:
- 5+ years of hands-on experience designing, developing, and deploying solutions using Microsoft Power Apps (canvas and model-driven apps, portals), SharePoint Online, and Power Automate.
- Bachelors Degree
- DoD/DoW Secret Clearance (active or able to obtain) required.
- IAT Level II Certification required (e.g., Security+ CE, CCNA Security, GSEC, or equivalent as defined by DoD 8570/8140).
- Proficiency in creating and managing SharePoint Online sites, lists, libraries, content types, and permissions to support secure collaboration.
- Demonstrated experience building automated workflows for approvals, notifications, task routing, and other business processes using Power Automate.
- Experience integrating Power Apps and SharePoint with Microsoft Dataverse, SQL Server or other SQL databases, REST APIs, and Microsoft 365 services.
- Strong understanding of data modeling, data connections, validation rules, and real-time data synchronization across systems.
- Proven ability to customize SharePoint and Power Apps solutions to align with organizational branding and UX/UI standards.
- Experience working directly with business and technical stakeholders to gather requirements, define use cases, and deliver scalable, mission-critical solutions.
- Ability to develop clear, comprehensive technical and end-user documentation, including training materials and support guides.
- Experience integrating solution data with Power BI to build reports and dashboards that track KPIs and solution effectiveness.
- Strong problem-solving skills and the ability to troubleshoot issues across the Microsoft 365 and Power Platform stack.
- Excellent verbal and written communication skills, with the ability to explain technical concepts to non-technical audiences.
Now Benefits list (from the company description):
- 20 Days PTO + 40 Hours of Paid Sick & Safe Time
- 11 Federal Holidays + 2 Corporate Holidays
- Health, Vision, Dental, and Life Insurance
- 401(k) with Tiered Match & 100% Vesting
- Parental Leave for Birthing and Non
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID etc. 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. We need to decide which sections to include. The posting includes: - About Saliense (company description) – could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Saliense" describing company. Could we treat that as "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can adapt: we have a company overview; maybe we can put under "About the role"? But that might be inaccurate. However we must not invent sections; we can include a section only if posting has real specific content for it. The posting does have a company description; we could put that under a heading like "About Saliense" but that's not in the allowed list. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings where appropriate. So we should map content to those headings.
We have:
- Responsibilities: the list under "Roles & Responsibilities". That's a list of duties. So we can have Responsibilities
with - items.
- Qualifications: the list under "Qualifications". That's qualifications. So
Qualifications
with list.
- Benefits: the bullet list under "About Saliense" includes benefits: 20 Days PTO + 40 Hours of Paid Sick & Safe Time, 11 Federal Holidays + 2 Corporate Holidays, Health, Vision, Dental, and Life Insurance, 401(k) with Tiered Match & 100% Vesting, Parental Leave for Birthing and Non-Birthing Parents, Professional Development Reimbursement Program. Also mention "competitive compensation and benefits". So we can have Benefits
with list.
- Pay: Salary Range: $100,000 - $115,000. So we can have Pay
with containing that range and maybe note about factors.
- Schedule: "This position with be 5 days a week onsite in Chambersburg, PA." So schedule: 5 days a week onsite. So
Schedule
with .
- About the role: maybe we can include a brief prose about the role? The posting includes a paragraph about Saliense (company) and then "Join us at Saliense...". That's more about company. Could treat as "About the role"? Might be okay. But we already have responsibilities and qualifications; we could also have a short paragraph summarizing the role purpose. However the instruction: Prefer a few substantive sections over many thin ones. We already have Responsibilities, Qualifications, Benefits, Pay, Schedule. That's five sections. Adding About the role may be thin. But we could incorporate the company description into Benefits? No. Could we omit About the role section? The instruction says include a section ONLY when the posting has real, specific content for it. The posting does have a paragraph about Saliense and encouraging employees, etc. That's not exactly about the role but could be considered "About the role"? Might be considered filler? It's not boilerplate; it's substantive about company culture. Could be placed under a heading like "About Saliense" but not in allowed list. However we could treat it as "About the role" albeit not perfect but acceptable. 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 as examples. Safer to stick to those headings. We can put the company description under "About the role". It's not exactly about the role but it's the only place to put that prose. It's not filler; it's specific content about the company and its values. So we will include About the role
with
containing that paragraph.
We must not repeat the job title as a heading. No job title given explicitly; we can ignore.
We must not include duplicated lines, cookie/navigation/legal/EEO etc. There's none.
We must not include application instructions. None.
We must not include placeholder text like "commensurate with experience". Not present.
We need to preserve ALL substantive information. So we need to include all bullet points from responsibilities, qualifications, benefits, pay, schedule, and the company description.
We need to format lists as
- . For benefits, we have a list; we can bullet each.
For responsibilities, many items; each as
- .
For qualifications, many items; each as
- .
We need to ensure we don't lose any details.
Let's extract the content.
Company description paragraph:
"About Saliense At Saliense, we are committed to fostering a culture of continuous learning and professional growth. Our employees are encouraged to take on challenging and meaningful work, with ample opportunities for career advancement. We offer competitive compensation and benefits, including: 20 Days PTO + 40 Hours of Paid Sick & Safe Time11 Federal Holidays + 2 Corporate HolidaysHealth, Vision, Dental, and Life Insurance401(k) with Tiered Match & 100% VestingParental Leave for Birthing and Non-Birthing ParentsProfessional Development Reimbursement Program We believe in empowering our team members to achieve their professional goals while contributing to impactful projects that make a difference. Join us at Saliense and be part of a growing organization dedicated to innovation, collaboration, and excellence. Visit www.saliense.com to learn more. There are many more - connect with us to get a preview of the full benefits package."
Note there are some missing spaces: "Safe Time11 Federal Holidays" etc. We need to preserve as is? Probably we should keep the text but maybe add spaces for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the exact text, but we can fix obvious typos? The missing space is likely a formatting error; but preserving exactly might be required. However we could add a space to make it readable but that would be altering. I'd keep as is but maybe add a space after "Time" before "11"? The original: "20 Days PTO + 40 Hours of Paid Sick & Safe Time11 Federal Holidays + 2 Corporate Holidays". It's missing a space. If we keep exactly, it's "Safe Time11". That seems odd but it's the source. I'd keep exactly as given.
Similarly "Health, Vision, Dental, and Life Insurance401(k)" missing space. We'll keep as is.
We'll just copy the paragraph as is.
Now Responsibilities list:
- Design, develop, and maintain custom Power Apps solutions, including canvas apps, model-driven apps, and portals, to support mission-critical business processes.
- Create, configure, and manage SharePoint Online sites, document libraries, lists, and content types to enable effective collaboration and information management.
- Build and optimize automated workflows using Power Automate to handle approvals, notifications, task assignments, and other business processes.
- Integrate Power Apps and SharePoint solutions with Microsoft Dataverse, SQL databases, REST APIs, and other Microsoft 365 tools to ensure seamless data flow.
- Configure and manage data connections, implement validation rules, and ensure real-time data synchronization across systems and applications.
- Customize the user interface and user experience of SharePoint sites and Power Apps to align with organizational branding and usability standards.
- Collaborate closely with stakeholders to gather, analyze, and refine business requirements and translate them into technical specifications and solution designs.
- Develop and maintain comprehensive technical documentation, including solution designs, data models, configuration details, and support procedures.
- Create user guides, job aids, and training materials to support adoption and ongoing use of Power Apps and SharePoint solutions.
- Conduct training sessions, demonstrations, and knowledge-transfer activities to ensure end-users and stakeholders are proficient with deployed tools.
- Integrate Power Apps and SharePoint data with Power BI to develop dashboards and reports that measure solution performance and business impact.
- Monitor, troubleshoot, and optimize existing solutions to improve performance, reliability, and user experience.
- Ensure all solutions and development practices align with NRE organizational goals, mission objectives, and applicable security and compliance requirements.
- Collaborate with cross-functional teams, including security, infrastructure, and operations, to support deployments, upgrades, and platform enhancements.
Note: There's a typo "NRE" maybe should be "NR"? but we keep.
Now Qualifications list:
- 5+ years of hands-on experience designing, developing, and deploying solutions using Microsoft Power Apps (canvas and model-driven apps, portals), SharePoint Online, and Power Automate.
- Bachelors Degree
- DoD/DoW Secret Clearance (active or able to obtain) required.
- IAT Level II Certification required (e.g., Security+ CE, CCNA Security, GSEC, or equivalent as defined by DoD 8570/8140).
- Proficiency in creating and managing SharePoint Online sites, lists, libraries, content types, and permissions to support secure collaboration.
- Demonstrated experience building automated workflows for approvals, notifications, task routing, and other business processes using Power Automate.
- Experience integrating Power Apps and SharePoint with Microsoft Dataverse, SQL Server or other SQL databases, REST APIs, and Microsoft 365 services.
- Strong understanding of data modeling, data connections, validation rules, and real-time data synchronization across systems.
- Proven ability to customize SharePoint and Power Apps solutions to align with organizational branding and UX/UI standards.
- Experience working directly with business and technical stakeholders to gather requirements, define use cases, and deliver scalable, mission-critical solutions.
- Ability to develop clear, comprehensive technical and end-user documentation, including training materials and support guides.
- Experience integrating solution data with Power BI to build reports and dashboards that track KPIs and solution effectiveness.
- Strong problem-solving skills and the ability to troubleshoot issues across the Microsoft 365 and Power Platform stack.
- Excellent verbal and written communication skills, with the ability to explain technical concepts to non-technical audiences.
Now Benefits list (from the company description):
- 20 Days PTO + 40 Hours of Paid Sick & Safe Time
- 11 Federal Holidays + 2 Corporate Holidays
- Health, Vision, Dental, and Life Insurance
- 401(k) with Tiered Match & 100% Vesting
- Parental Leave for Birthing and Non
Responsibilities
with- items.
- Qualifications: the list under "Qualifications". That's qualifications. So
Qualifications
with list. - Benefits: the bullet list under "About Saliense" includes benefits: 20 Days PTO + 40 Hours of Paid Sick & Safe Time, 11 Federal Holidays + 2 Corporate Holidays, Health, Vision, Dental, and Life Insurance, 401(k) with Tiered Match & 100% Vesting, Parental Leave for Birthing and Non-Birthing Parents, Professional Development Reimbursement Program. Also mention "competitive compensation and benefits". So we can haveBenefits
with list. - Pay: Salary Range: $100,000 - $115,000. So we can havePay
withcontaining that range and maybe note about factors. - Schedule: "This position with be 5 days a week onsite in Chambersburg, PA." So schedule: 5 days a week onsite. So
Schedule
with. - About the role: maybe we can include a brief prose about the role? The posting includes a paragraph about Saliense (company) and then "Join us at Saliense...". That's more about company. Could treat as "About the role"? Might be okay. But we already have responsibilities and qualifications; we could also have a short paragraph summarizing the role purpose. However the instruction: Prefer a few substantive sections over many thin ones. We already have Responsibilities, Qualifications, Benefits, Pay, Schedule. That's five sections. Adding About the role may be thin. But we could incorporate the company description into Benefits? No. Could we omit About the role section? The instruction says include a section ONLY when the posting has real, specific content for it. The posting does have a paragraph about Saliense and encouraging employees, etc. That's not exactly about the role but could be considered "About the role"? Might be considered filler? It's not boilerplate; it's substantive about company culture. Could be placed under a heading like "About Saliense" but not in allowed list. However we could treat it as "About the role" albeit not perfect but acceptable. 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 as examples. Safer to stick to those headings. We can put the company description under "About the role". It's not exactly about the role but it's the only place to put that prose. It's not filler; it's specific content about the company and its values. So we will include
About the role
withcontaining that paragraph. We must not repeat the job title as a heading. No job title given explicitly; we can ignore. We must not include duplicated lines, cookie/navigation/legal/EEO etc. There's none. We must not include application instructions. None. We must not include placeholder text like "commensurate with experience". Not present. We need to preserve ALL substantive information. So we need to include all bullet points from responsibilities, qualifications, benefits, pay, schedule, and the company description. We need to format lists as
- . For benefits, we have a list; we can bullet each. For responsibilities, many items; each as
- . For qualifications, many items; each as
- . We need to ensure we don't lose any details. Let's extract the content. Company description paragraph: "About Saliense At Saliense, we are committed to fostering a culture of continuous learning and professional growth. Our employees are encouraged to take on challenging and meaningful work, with ample opportunities for career advancement. We offer competitive compensation and benefits, including: 20 Days PTO + 40 Hours of Paid Sick & Safe Time11 Federal Holidays + 2 Corporate HolidaysHealth, Vision, Dental, and Life Insurance401(k) with Tiered Match & 100% VestingParental Leave for Birthing and Non-Birthing ParentsProfessional Development Reimbursement Program We believe in empowering our team members to achieve their professional goals while contributing to impactful projects that make a difference. Join us at Saliense and be part of a growing organization dedicated to innovation, collaboration, and excellence. Visit www.saliense.com to learn more. There are many more - connect with us to get a preview of the full benefits package." Note there are some missing spaces: "Safe Time11 Federal Holidays" etc. We need to preserve as is? Probably we should keep the text but maybe add spaces for readability? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the exact text, but we can fix obvious typos? The missing space is likely a formatting error; but preserving exactly might be required. However we could add a space to make it readable but that would be altering. I'd keep as is but maybe add a space after "Time" before "11"? The original: "20 Days PTO + 40 Hours of Paid Sick & Safe Time11 Federal Holidays + 2 Corporate Holidays". It's missing a space. If we keep exactly, it's "Safe Time11". That seems odd but it's the source. I'd keep exactly as given. Similarly "Health, Vision, Dental, and Life Insurance401(k)" missing space. We'll keep as is. We'll just copy the paragraph as is. Now Responsibilities list: - Design, develop, and maintain custom Power Apps solutions, including canvas apps, model-driven apps, and portals, to support mission-critical business processes. - Create, configure, and manage SharePoint Online sites, document libraries, lists, and content types to enable effective collaboration and information management. - Build and optimize automated workflows using Power Automate to handle approvals, notifications, task assignments, and other business processes. - Integrate Power Apps and SharePoint solutions with Microsoft Dataverse, SQL databases, REST APIs, and other Microsoft 365 tools to ensure seamless data flow. - Configure and manage data connections, implement validation rules, and ensure real-time data synchronization across systems and applications. - Customize the user interface and user experience of SharePoint sites and Power Apps to align with organizational branding and usability standards. - Collaborate closely with stakeholders to gather, analyze, and refine business requirements and translate them into technical specifications and solution designs. - Develop and maintain comprehensive technical documentation, including solution designs, data models, configuration details, and support procedures. - Create user guides, job aids, and training materials to support adoption and ongoing use of Power Apps and SharePoint solutions. - Conduct training sessions, demonstrations, and knowledge-transfer activities to ensure end-users and stakeholders are proficient with deployed tools. - Integrate Power Apps and SharePoint data with Power BI to develop dashboards and reports that measure solution performance and business impact. - Monitor, troubleshoot, and optimize existing solutions to improve performance, reliability, and user experience. - Ensure all solutions and development practices align with NRE organizational goals, mission objectives, and applicable security and compliance requirements. - Collaborate with cross-functional teams, including security, infrastructure, and operations, to support deployments, upgrades, and platform enhancements. Note: There's a typo "NRE" maybe should be "NR"? but we keep. Now Qualifications list: - 5+ years of hands-on experience designing, developing, and deploying solutions using Microsoft Power Apps (canvas and model-driven apps, portals), SharePoint Online, and Power Automate. - Bachelors Degree - DoD/DoW Secret Clearance (active or able to obtain) required. - IAT Level II Certification required (e.g., Security+ CE, CCNA Security, GSEC, or equivalent as defined by DoD 8570/8140). - Proficiency in creating and managing SharePoint Online sites, lists, libraries, content types, and permissions to support secure collaboration. - Demonstrated experience building automated workflows for approvals, notifications, task routing, and other business processes using Power Automate. - Experience integrating Power Apps and SharePoint with Microsoft Dataverse, SQL Server or other SQL databases, REST APIs, and Microsoft 365 services. - Strong understanding of data modeling, data connections, validation rules, and real-time data synchronization across systems. - Proven ability to customize SharePoint and Power Apps solutions to align with organizational branding and UX/UI standards. - Experience working directly with business and technical stakeholders to gather requirements, define use cases, and deliver scalable, mission-critical solutions. - Ability to develop clear, comprehensive technical and end-user documentation, including training materials and support guides. - Experience integrating solution data with Power BI to build reports and dashboards that track KPIs and solution effectiveness. - Strong problem-solving skills and the ability to troubleshoot issues across the Microsoft 365 and Power Platform stack. - Excellent verbal and written communication skills, with the ability to explain technical concepts to non-technical audiences. Now Benefits list (from the company description): - 20 Days PTO + 40 Hours of Paid Sick & Safe Time - 11 Federal Holidays + 2 Corporate Holidays - Health, Vision, Dental, and Life Insurance - 401(k) with Tiered Match & 100% Vesting - Parental Leave for Birthing and Non