Mid-Level Power Platform/Cloud Platform Developer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: About the role (maybe from "What We Are Looking For" paragraph). Responsibilities (the Duties/Responsibilities list). Requirements (maybe Minimum Skills and Requirements). Qualifications (maybe Preferred Qualifications). Skills (maybe combine? But we have Skills/Experience heading; we could treat Skills as the combined skills/experience. However we already have Requirements and Qualifications; maybe we can put Skills as a separate section summarizing skills? But the instruction: prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those specific names if content exists. We have content for Requirements (minimum skills) and Qualifications (preferred). So we can include both.
Skills section: maybe we could treat the Skills/Experience as Skills section, but we already have Requirements and Qualifications covering that. Could omit Skills to avoid thin sections. However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; only include when posting has real specific content. We have content for Skills/Experience; but we already split into Requirements and Qualifications. Could still include Skills as a summary of both? Might be redundant. Better to include Requirements and Qualifications, and maybe Skills not needed. But we have also a list of skills in the Minimum Skills and Requirements (which are skills). So we could treat that as Requirements. Preferred Qualifications as Qualifications. So we can omit Skills.
Benefits: from Why Join EnSafe? we have several paragraphs. We'll put that under Benefits.
Now we need to preserve all substantive information: include the location info (Jacksonville or Titusville, FL, onsite, relocation offered). That's part of About the role? Could be in About the role paragraph. We'll include that.
We need to remove boilerplate: EEO, AI use in Hiring, Applicant Privacy Notice, etc. Also remove the final lines about checking us out on the web? That's maybe not boilerplate but could be considered promotional; but it's substantive? It's a link to website. Might be considered not essential but could be kept? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Check us out on the web at www.ensafe.com" is not legal/EEO; it's promotional but maybe okay to keep? It's not application instructions. It's not duplicated. I'd keep it as part of About EnSafe? Actually there is an "About EnSafe" paragraph later. That is substantive about company. Should we include that? Could be part of Benefits or About the role? The posting includes "About EnSafe" after Why Join EnSafe? It's about company history. Could be considered part of Benefits or maybe a separate section? Not in the list of headings. We could incorporate into Benefits or maybe a separate "About the company" but not allowed headings. So we could append to Benefits section as extra paragraphs.
We must preserve all substantive information; we can include it in Benefits or maybe a separate
under Benefits.
We must not include the EEO paragraph at the end. Also remove "Applicant Privacy Notice | AI use in Hiring". Also remove the line "EnSafe is committed to being an EEO employer..." etc.
Now craft HTML.
Structure:
About the role
...
Responsibilities
- ... each duty
Requirements
- ... each minimum skill/requirement
Qualifications
- ... each preferred qualification
Benefits
... paragraphs from Why Join EnSafe? and About EnSafe maybe
We need to ensure we don't include headings with empty content.
Now extract content.
About the role: The posting starts: "Do you like working with different project teams in a fast-paced environment? Are you interested in joining an organization focused on making a positive impact? If so, we’d like to talk with you about growing with us. EnSafe is accepting applications for a Mid-Level Power Platform/Cloud Platform Developer based out of either our Jacksonville or Titusville, FL, office. This position will work onsite at one of the listed FL locations. If needed, relocations will be offered to meet this expectation. What We Are Looking For As part of our Environmental Information Systems (EIS) services group, you will design, develop, and support Microsoft Power Platform and cloud-based business solutions that empower project teams across disciplines such as GIS, data management, environmental compliance, Environmental Health and Safety (EHS), field services, reporting, and client-driven EHS solutions. This position is intended for a mid-level developer who can take ownership of assigned solutions, work directly with internal and external stakeholders, translate business needs into functional applications, and help improve how project teams collect, manage, automate, and report data. The ideal candidate will have hands-on experience with Microsoft Power Platform, SharePoint Online, Microsoft 365, and related cloud technologies, along with the ability to communicate technical concepts clearly to non-technical users."
We can combine the initial invitation and the "What We Are Looking For" into About the role paragraph.
Now Responsibilities: list under "Duties/Responsibilities In this role, you will:" then bullet points each starting with a verb. We'll extract each bullet.
Let's list them:
- Design, develop, test, and maintain business solutions using Microsoft Power Platform, including Power Apps, Power Apps Code Apps, Power Automate, Power BI, Dataverse, and SharePoint Online.
- Build and support Microsoft 365 solutions, including SharePoint sites, lists, libraries, Teams integrations, permissions structures, document automation workflows, and collaboration tools.
- Develop canvas apps and other user-friendly interfaces that support office, field, mobile, and client-facing business processes.
- Create automated workflows for notifications, approvals, data routing, document generation, reporting, and system integrations.
- Support data collection and field technology solutions using tools such as FastField Forms, ArcGIS Field Maps, Tablogs, Power Apps, SharePoint, and other approved platforms.
- Work with project managers, technical staff, and client stakeholders to gather requirements, document workflows, identify process improvements, and recommend practical technology solutions.
- Integrate Microsoft 365 solutions with external systems using APIs, custom connectors, HTTP actions, Office Scripts, Power Query, or other approved integration methods.
- Develop and maintain Power BI dashboards, reports, and datasets using SharePoint, Dataverse, Excel, SQL, APIs, and other business data sources.
- Help normalize, clean, transform, and model data for reporting, automation, and integration across systems.
- Troubleshoot application, automation, permissions, data connection, and user access issues.
- Participate in solution design, technical documentation, testing plans, deployment planning, user guidance, and long-term support procedures.
- Support existing internal and client-facing applications by resolving issues, improving performance, enhancing usability, and adding new functionality.
- Contribute to reusable development patterns, templates, documentation standards, and best practices for the EIS technology team.
- Apply a practical understanding of large language models, generative AI capabilities, prompt design, responsible AI use, and appropriate AI-assisted development practices to improve business solutions and user productivity.
- Collaborate with EIS team members to address technical challenges across multiple projects in environmental consulting, EHS compliance, site remediation, data management, and cloud-based project delivery.
- Generate training materials, user guides, video tutorials, and other support documentation to improve adoption of developed solutions.
Now Requirements (Minimum Skills and Requirements): list after "Minimum Skills and Requirements:" then bullet points.
- Bachelor’s or Associate’s Degree in Computer Science, Information Technology, Engineering, Data Science, Environmental Science, or a related technical field — or equivalent professional experience, training, or certifications.
- 3–6 years of experience developing business applications, automations, reporting solutions, databases, or cloud-based systems.
- Hands-on experience developing with Microsoft Power Platform, especially Power Apps and Power Automate.
- Experience configuring and supporting SharePoint Online sites, lists, libraries, views, permissions, pages, and document management structures.
- Working knowledge of Microsoft 365 services, including Teams, Outlook, OneDrive, Excel, Forms, Planner, and related collaboration tools.
- Ability to gather requirements from business users and translate them into functional, maintainable technical solutions.
- Understanding of relational data concepts, data modeling, and structured data management.
- Experience troubleshooting Power Apps formulas, Power Automate flow failures, connector issues, user permissions, and data source problems.
- Strong attention to detail and ability to independently manage assigned tasks from requirements through testing and support.
- Ability to communicate technical concepts clearly to both technical and non-technical audiences.
- Excellent written and verbal communication skills.
- Basic understanding of large language models, generative AI tools, prompt engineering concepts, responsible AI use, and how to appropriately apply AI capabilities in business and technology workflows.
- Demonstrated ability to learn new tools, platforms, and frameworks quickly.
Now Qualifications (Preferred Qualifications): list after "Preferred Qualifications" then bullet points.
- Experience with Dataverse, model-driven apps, Power Pages, managed solutions, environment strategy, or Power Platform application lifecycle management.
- Experience with Power BI, Power Query, DAX, data modeling, dashboard development, and report publishing.
- Experience with SharePoint JSON formatting, content types, managed metadata, calculated columns, lookup columns, and permission design.
- Experience using REST APIs, HTTP actions, custom connectors, Microsoft Graph, or third-party system integrations.
- Experience with Office Scripts, JavaScript, TypeScript, HTML, CSS, SQL, Python, PowerShell, or other scripting/programming languages.
- Experience developing web applications, including responsive user interfaces, front-end or full-stack development, application integrations, or cloud-hosted business applications.
- Experience designing, configuring, or developing custom AI agents, copilots, chatbots, or AI-assisted workflow solutions using tools such as Copilot Studio, Azure AI services, Azure AI Foundry, Microsoft 365 Copilot extensibility, or similar platforms.
- Experience supporting environmental, EHS, compliance, engineering, field data collection, GIS, or consulting workflows.
- Experience developing mobile-friendly or offline-capable Power Apps.
- Familiarity with low-code mobile form builders such as FastField, ArcGIS Field Maps, Tablogs, Survey123, or similar platforms.
- Experience working in Microsoft Government Community Cloud (GCC), GCC High, or other regulated Microsoft 365 environments.
- Familiarity with solution documentation, version control, development/test/production environments, and release management practices.
- Microsoft certifications such as Power Platform Fundamentals (PL-900), Power Platform App Maker (PL-100), Power Platform Functional Consultant (PL-200), Power Platform Developer (PL-400), Power BI Data Analyst (PL-30
for prose. We need to decide sections: About the role (maybe from "What We Are Looking For" paragraph). Responsibilities (the Duties/Responsibilities list). Requirements (maybe Minimum Skills and Requirements). Qualifications (maybe Preferred Qualifications). Skills (maybe combine? But we have Skills/Experience heading; we could treat Skills as the combined skills/experience. However we already have Requirements and Qualifications; maybe we can put Skills as a separate section summarizing skills? But the instruction: prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But they ask to use headings for those specific names if content exists. We have content for Requirements (minimum skills) and Qualifications (preferred). So we can include both. Skills section: maybe we could treat the Skills/Experience as Skills section, but we already have Requirements and Qualifications covering that. Could omit Skills to avoid thin sections. However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must include all; only include when posting has real specific content. We have content for Skills/Experience; but we already split into Requirements and Qualifications. Could still include Skills as a summary of both? Might be redundant. Better to include Requirements and Qualifications, and maybe Skills not needed. But we have also a list of skills in the Minimum Skills and Requirements (which are skills). So we could treat that as Requirements. Preferred Qualifications as Qualifications. So we can omit Skills. Benefits: from Why Join EnSafe? we have several paragraphs. We'll put that under Benefits. Now we need to preserve all substantive information: include the location info (Jacksonville or Titusville, FL, onsite, relocation offered). That's part of About the role? Could be in About the role paragraph. We'll include that. We need to remove boilerplate: EEO, AI use in Hiring, Applicant Privacy Notice, etc. Also remove the final lines about checking us out on the web? That's maybe not boilerplate but could be considered promotional; but it's substantive? It's a link to website. Might be considered not essential but could be kept? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Check us out on the web at www.ensafe.com" is not legal/EEO; it's promotional but maybe okay to keep? It's not application instructions. It's not duplicated. I'd keep it as part of About EnSafe? Actually there is an "About EnSafe" paragraph later. That is substantive about company. Should we include that? Could be part of Benefits or About the role? The posting includes "About EnSafe" after Why Join EnSafe? It's about company history. Could be considered part of Benefits or maybe a separate section? Not in the list of headings. We could incorporate into Benefits or maybe a separate "About the company" but not allowed headings. So we could append to Benefits section as extra paragraphs. We must preserve all substantive information; we can include it in Benefits or maybe a separate
under Benefits. We must not include the EEO paragraph at the end. Also remove "Applicant Privacy Notice | AI use in Hiring". Also remove the line "EnSafe is committed to being an EEO employer..." etc. Now craft HTML. Structure:
About the role
...
Responsibilities
- ... each duty
Requirements
- ... each minimum skill/requirement
Qualifications
- ... each preferred qualification
Benefits
... paragraphs from Why Join EnSafe? and About EnSafe maybe
We need to ensure we don't include headings with empty content. Now extract content. About the role: The posting starts: "Do you like working with different project teams in a fast-paced environment? Are you interested in joining an organization focused on making a positive impact? If so, we’d like to talk with you about growing with us. EnSafe is accepting applications for a Mid-Level Power Platform/Cloud Platform Developer based out of either our Jacksonville or Titusville, FL, office. This position will work onsite at one of the listed FL locations. If needed, relocations will be offered to meet this expectation. What We Are Looking For As part of our Environmental Information Systems (EIS) services group, you will design, develop, and support Microsoft Power Platform and cloud-based business solutions that empower project teams across disciplines such as GIS, data management, environmental compliance, Environmental Health and Safety (EHS), field services, reporting, and client-driven EHS solutions. This position is intended for a mid-level developer who can take ownership of assigned solutions, work directly with internal and external stakeholders, translate business needs into functional applications, and help improve how project teams collect, manage, automate, and report data. The ideal candidate will have hands-on experience with Microsoft Power Platform, SharePoint Online, Microsoft 365, and related cloud technologies, along with the ability to communicate technical concepts clearly to non-technical users." We can combine the initial invitation and the "What We Are Looking For" into About the role paragraph. Now Responsibilities: list under "Duties/Responsibilities In this role, you will:" then bullet points each starting with a verb. We'll extract each bullet. Let's list them: - Design, develop, test, and maintain business solutions using Microsoft Power Platform, including Power Apps, Power Apps Code Apps, Power Automate, Power BI, Dataverse, and SharePoint Online. - Build and support Microsoft 365 solutions, including SharePoint sites, lists, libraries, Teams integrations, permissions structures, document automation workflows, and collaboration tools. - Develop canvas apps and other user-friendly interfaces that support office, field, mobile, and client-facing business processes. - Create automated workflows for notifications, approvals, data routing, document generation, reporting, and system integrations. - Support data collection and field technology solutions using tools such as FastField Forms, ArcGIS Field Maps, Tablogs, Power Apps, SharePoint, and other approved platforms. - Work with project managers, technical staff, and client stakeholders to gather requirements, document workflows, identify process improvements, and recommend practical technology solutions. - Integrate Microsoft 365 solutions with external systems using APIs, custom connectors, HTTP actions, Office Scripts, Power Query, or other approved integration methods. - Develop and maintain Power BI dashboards, reports, and datasets using SharePoint, Dataverse, Excel, SQL, APIs, and other business data sources. - Help normalize, clean, transform, and model data for reporting, automation, and integration across systems. - Troubleshoot application, automation, permissions, data connection, and user access issues. - Participate in solution design, technical documentation, testing plans, deployment planning, user guidance, and long-term support procedures. - Support existing internal and client-facing applications by resolving issues, improving performance, enhancing usability, and adding new functionality. - Contribute to reusable development patterns, templates, documentation standards, and best practices for the EIS technology team. - Apply a practical understanding of large language models, generative AI capabilities, prompt design, responsible AI use, and appropriate AI-assisted development practices to improve business solutions and user productivity. - Collaborate with EIS team members to address technical challenges across multiple projects in environmental consulting, EHS compliance, site remediation, data management, and cloud-based project delivery. - Generate training materials, user guides, video tutorials, and other support documentation to improve adoption of developed solutions. Now Requirements (Minimum Skills and Requirements): list after "Minimum Skills and Requirements:" then bullet points. - Bachelor’s or Associate’s Degree in Computer Science, Information Technology, Engineering, Data Science, Environmental Science, or a related technical field — or equivalent professional experience, training, or certifications. - 3–6 years of experience developing business applications, automations, reporting solutions, databases, or cloud-based systems. - Hands-on experience developing with Microsoft Power Platform, especially Power Apps and Power Automate. - Experience configuring and supporting SharePoint Online sites, lists, libraries, views, permissions, pages, and document management structures. - Working knowledge of Microsoft 365 services, including Teams, Outlook, OneDrive, Excel, Forms, Planner, and related collaboration tools. - Ability to gather requirements from business users and translate them into functional, maintainable technical solutions. - Understanding of relational data concepts, data modeling, and structured data management. - Experience troubleshooting Power Apps formulas, Power Automate flow failures, connector issues, user permissions, and data source problems. - Strong attention to detail and ability to independently manage assigned tasks from requirements through testing and support. - Ability to communicate technical concepts clearly to both technical and non-technical audiences. - Excellent written and verbal communication skills. - Basic understanding of large language models, generative AI tools, prompt engineering concepts, responsible AI use, and how to appropriately apply AI capabilities in business and technology workflows. - Demonstrated ability to learn new tools, platforms, and frameworks quickly. Now Qualifications (Preferred Qualifications): list after "Preferred Qualifications" then bullet points. - Experience with Dataverse, model-driven apps, Power Pages, managed solutions, environment strategy, or Power Platform application lifecycle management. - Experience with Power BI, Power Query, DAX, data modeling, dashboard development, and report publishing. - Experience with SharePoint JSON formatting, content types, managed metadata, calculated columns, lookup columns, and permission design. - Experience using REST APIs, HTTP actions, custom connectors, Microsoft Graph, or third-party system integrations. - Experience with Office Scripts, JavaScript, TypeScript, HTML, CSS, SQL, Python, PowerShell, or other scripting/programming languages. - Experience developing web applications, including responsive user interfaces, front-end or full-stack development, application integrations, or cloud-hosted business applications. - Experience designing, configuring, or developing custom AI agents, copilots, chatbots, or AI-assisted workflow solutions using tools such as Copilot Studio, Azure AI services, Azure AI Foundry, Microsoft 365 Copilot extensibility, or similar platforms. - Experience supporting environmental, EHS, compliance, engineering, field data collection, GIS, or consulting workflows. - Experience developing mobile-friendly or offline-capable Power Apps. - Familiarity with low-code mobile form builders such as FastField, ArcGIS Field Maps, Tablogs, Survey123, or similar platforms. - Experience working in Microsoft Government Community Cloud (GCC), GCC High, or other regulated Microsoft 365 environments. - Familiarity with solution documentation, version control, development/test/production environments, and release management practices. - Microsoft certifications such as Power Platform Fundamentals (PL-900), Power Platform App Maker (PL-100), Power Platform Functional Consultant (PL-200), Power Platform Developer (PL-400), Power BI Data Analyst (PL-30