Microsoft Power Platform 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 (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to extract sections: maybe "About the role" could be the introductory paragraph about HonorVet Technologies? That is about the company, not role. Could be considered "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role if there is content. The posting includes: "HonorVet Technologies is a Service-Disabled Veteran-Owned IT staffing firm, ISO 9001 and ISO 27001 certified, working with federal agencies, state governments, and Fortune 500 enterprise clients across the US. What makes us different isn't a tagline; it's the way we work. We don't forward resumes and hope for the best. We take the time to understand where a professional like you are headed and only reach out when we genuinely believe there's a fit worth exploring." That's about the company, could be placed under About the role? Might be better as a short
before sections. But they said do NOT repeat the job title as a heading; they didn't forbid a paragraph before headings. So we can include a
with that company description.
Then we have Job Title line: "Job Title: Microsoft Power Platform Developer". Not to be used as heading. Could be included in a
maybe? But they said fold minor metadata into a short
or drop it. So we can include a
with Job Title, Location, Duration maybe.
Location: "Location: Raleigh NC, 27610 (Hybrid)". Duration: "Duration: 12 Months (Possible Extension)". Could be in same paragraph.
Then Job Description paragraph: "Client is seeking a Microsoft Power Platform Developer for the upgrade and development of an existing Geotechnical Application. In this role, you will be required to design, write, deploy and maintain a Low Code Web application and possible future and ongoing projects. You will also be required to contribute to design and planning sessions as well as formulate approaches for current coding tasks. Candidate must have strong application architecture, design, and development skills. To ensure success as a Microsoft Low Code, Developer should have a strong grasp of the Microsoft Power Platform (Power Apps, Power Automate, Power BI), Azure services, and related low‑code capabilities. You should be skilled in building scalable apps, automating business processes, and solving problems in a fast‑paced environment. Low Code Developer will be able to perform end‑to‑end solution delivery, including the creation, maintenance, and enhancement of Power Platform applications. This is not a power platform administration role. Candidates will require experience deploying solutions and working within Power Platform Environments."
Then "Key Responsibilities:" list. Then "Required Skills:" list. Then "Preferred skills:" list. Then contact info line: "If you are interested, feel free to reach out to me directly at aksham.kumar@honorvet.com or call/text at (551) 220-9887." That's application instruction, should be removed per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we drop that line.
Also note duplicated line: "Automated processes to meet business needs." appears twice; we need to preserve but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines: we should keep only one instance? It says remove duplicated lines. So we should remove duplicate line.
Now decide sections: We have Responsibilities (Key Responsibilities). We have Required Skills (Required Skills). We have Preferred skills (Preferred skills). Could combine Required and Preferred into Skills? But they said prefer a few substantive sections over many thin ones. Could have sections: Responsibilities, Requirements (maybe combine Required Skills), Skills (Preferred). Or we could have Requirements (Required Skills) and Skills (Preferred). Also maybe Qualifications? Not separate.
We also could have About the role: maybe include the initial company description and job description? But About the role could be a short paragraph summarizing role. However we already have Job Description paragraph. Could treat that as About the role. But they gave example headings; we can use About the role for the descriptive paragraph about the role (the Job Description). Then Responsibilities for the list. Then Requirements for Required Skills. Then Skills for Preferred skills.
We must not create empty sections. All have content.
We need to output HTML fragment: use
for each section heading. Inside each, use
for prose,
- for lists.
We need to ensure we don't include any extra markup like or . Just the fragment.
Let's craft:
HonorVet Technologies is a Service-Disabled Veteran-Owned IT staffing firm, ISO 9001 and ISO 27001 certified, working with federal agencies, state governments, and Fortune 500 enterprise clients across the US. What makes us different isn't a tagline; it's the way we work. We don't forward resumes and hope for the best. We take the time to understand where a professional like you are headed and only reach out when we genuinely believe there's a fit worth exploring.
Job Title: Microsoft Power Platform Developer
Location: Raleigh NC, 27610 (Hybrid)
Duration: 12 Months (Possible Extension)
Then About the role
with the Job Description paragraph (maybe trimmed). Ensure we keep all substantive info.
Then Responsibilities
with - items from Key Responsibilities.
Then
Requirements
with Required Skills list.
Then Skills
with Preferred skills list.
We need to ensure we don't include any boilerplate like "If you are interested...". Remove.
Now extract responsibilities list exactly as given, but remove duplicate line.
Key Responsibilities text:
"Designing and developing Microsoft Power Platform solutions for the organization (Power Apps, Power Automate, Power BI, Dataverse).Your responsibilities will also include developing business requirements, preparing change management documentation, coordinating solution release schedules, and providing testing and training support. You will work closely with a technical lead and actively participate in discussions throughout the development lifecycle.Debugging, optimizing, and maintaining existing low‑code applications and workflows.Identifying and mitigating technical risks and issues within Power Platform solutions.Collaborating closely with project teams, analysts, and other developers.Providing technical support and guidance to stakeholders on Power Platform capabilities.Reporting on project statuses and solution progress to senior team members.Partnering with IT management and business users to translate requirements into user stories and solution designs.Working with clients to prototype, refine, test, and troubleshoot applications and automated processes to meet business needs. Automated processes to meet business needs.Analyzing, defining, and documenting requirements related to data models, workflows, system integration, andbusiness processes."
We need to split into sensible bullet points. The original is a run-on sentence; we can break at periods. Let's extract each sentence:
1. Designing and developing Microsoft Power Platform solutions for the organization (Power Apps, Power Automate, Power BI, Dataverse).
2. Your responsibilities will also include developing business requirements, preparing change management documentation, coordinating solution release schedules, and providing testing and training support.
3. You will work closely with a technical lead and actively participate in discussions throughout the development lifecycle.
4. Debugging, optimizing, and maintaining existing low‑code applications and workflows.
5. Identifying and mitigating technical risks and issues within Power Platform solutions.
6. Collaborating closely with project teams, analysts, and other developers.
7. Providing technical support and guidance to stakeholders on Power Platform capabilities.
8. Reporting on project statuses and solution progress to senior team members.
9. Partnering with IT management and business users to translate requirements into user stories and solution designs.
10. Working with clients to prototype, refine, test, and troubleshoot applications and automated processes to meet business needs.
11. Automated processes to meet business needs. (duplicate of part of 10? Actually it's a fragment; we should remove duplicate line.)
12. Analyzing, defining, and documenting requirements related to data models, workflows, system integration, and business processes.
We should remove duplicate line #11.
Now Required Skills list:
"5 years of Expert experience in the Microsoft Power Platform environment developing solutions, particularly migrating exiting apps/solutions to the Power Platform. 5 years of Experience in MS SQL Technologies writing TSQL queries (Select, Insert, Delete, etc.)"
We can split into two bullet points.
Preferred skills list:
"1 years of Knowledgeable with Microsoft DevOps or another Agile tool for tracking work 1 years Planning skills, including scope and development timeline estimating Excellent interpersonal, writing, and communication skills.Ability to work independently and complete projects with minimal supervision."
We need to parse: It seems missing punctuation. We'll make bullet points:
- 1 year of experience with Microsoft DevOps or another Agile tool for tracking work
- 1 year of planning skills, including scope and development timeline estimating
- Excellent interpersonal, writing, and communication skills
- Ability to work independently and complete projects with minimal supervision
Now About the role paragraph: Use the Job Description paragraph (the block after "Job Description:").
Let's copy that paragraph exactly:
"Client is seeking a Microsoft Power Platform Developer for the upgrade and development of an existing Geotechnical Application. In this role, you will be required to design, write, deploy and maintain a Low Code Web application and possible future and ongoing projects. You will also be required to contribute to design and planning sessions as well as formulate approaches for current coding tasks. Candidate must have strong application architecture, design, and development skills. To ensure success as a Microsoft Low Code, Developer should have a strong grasp of the Microsoft Power Platform (Power Apps, Power Automate, Power BI), Azure services, and related low‑code capabilities. You should be skilled in building scalable apps, automating business processes, and solving problems in a fast‑paced environment. Low Code Developer will be able to perform end‑to‑end solution delivery, including the creation, maintenance, and enhancement of Power Platform applications. This is not a power platform administration role. Candidates will require experience deploying solutions and working within Power Platform Environments."
We need to ensure we keep all info.
Now construct HTML.
We'll start with a for company intro.
Then a
for job metadata (maybe using labels). Could also be a with line breaks using
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to extract sections: maybe "About the role" could be the introductory paragraph about HonorVet Technologies? That is about the company, not role. Could be considered "About the role"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role if there is content. The posting includes: "HonorVet Technologies is a Service-Disabled Veteran-Owned IT staffing firm, ISO 9001 and ISO 27001 certified, working with federal agencies, state governments, and Fortune 500 enterprise clients across the US. What makes us different isn't a tagline; it's the way we work. We don't forward resumes and hope for the best. We take the time to understand where a professional like you are headed and only reach out when we genuinely believe there's a fit worth exploring." That's about the company, could be placed under About the role? Might be better as a short
before sections. But they said do NOT repeat the job title as a heading; they didn't forbid a paragraph before headings. So we can include a
with that company description. Then we have Job Title line: "Job Title: Microsoft Power Platform Developer". Not to be used as heading. Could be included in a
maybe? But they said fold minor metadata into a short
or drop it. So we can include a
with Job Title, Location, Duration maybe. Location: "Location: Raleigh NC, 27610 (Hybrid)". Duration: "Duration: 12 Months (Possible Extension)". Could be in same paragraph. Then Job Description paragraph: "Client is seeking a Microsoft Power Platform Developer for the upgrade and development of an existing Geotechnical Application. In this role, you will be required to design, write, deploy and maintain a Low Code Web application and possible future and ongoing projects. You will also be required to contribute to design and planning sessions as well as formulate approaches for current coding tasks. Candidate must have strong application architecture, design, and development skills. To ensure success as a Microsoft Low Code, Developer should have a strong grasp of the Microsoft Power Platform (Power Apps, Power Automate, Power BI), Azure services, and related low‑code capabilities. You should be skilled in building scalable apps, automating business processes, and solving problems in a fast‑paced environment. Low Code Developer will be able to perform end‑to‑end solution delivery, including the creation, maintenance, and enhancement of Power Platform applications. This is not a power platform administration role. Candidates will require experience deploying solutions and working within Power Platform Environments." Then "Key Responsibilities:" list. Then "Required Skills:" list. Then "Preferred skills:" list. Then contact info line: "If you are interested, feel free to reach out to me directly at aksham.kumar@honorvet.com or call/text at (551) 220-9887." That's application instruction, should be removed per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we drop that line. Also note duplicated line: "Automated processes to meet business needs." appears twice; we need to preserve but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicated lines: we should keep only one instance? It says remove duplicated lines. So we should remove duplicate line. Now decide sections: We have Responsibilities (Key Responsibilities). We have Required Skills (Required Skills). We have Preferred skills (Preferred skills). Could combine Required and Preferred into Skills? But they said prefer a few substantive sections over many thin ones. Could have sections: Responsibilities, Requirements (maybe combine Required Skills), Skills (Preferred). Or we could have Requirements (Required Skills) and Skills (Preferred). Also maybe Qualifications? Not separate. We also could have About the role: maybe include the initial company description and job description? But About the role could be a short paragraph summarizing role. However we already have Job Description paragraph. Could treat that as About the role. But they gave example headings; we can use About the role for the descriptive paragraph about the role (the Job Description). Then Responsibilities for the list. Then Requirements for Required Skills. Then Skills for Preferred skills. We must not create empty sections. All have content. We need to output HTML fragment: use
for each section heading. Inside each, use
for prose,
- for lists.
We need to ensure we don't include any extra markup like or . Just the fragment.
Let's craft:
HonorVet Technologies is a Service-Disabled Veteran-Owned IT staffing firm, ISO 9001 and ISO 27001 certified, working with federal agencies, state governments, and Fortune 500 enterprise clients across the US. What makes us different isn't a tagline; it's the way we work. We don't forward resumes and hope for the best. We take the time to understand where a professional like you are headed and only reach out when we genuinely believe there's a fit worth exploring.
Job Title: Microsoft Power Platform Developer
Then
Location: Raleigh NC, 27610 (Hybrid)
Duration: 12 Months (Possible Extension)About the role
with the Job Description paragraph (maybe trimmed). Ensure we keep all substantive info. ThenResponsibilities
with- items from Key Responsibilities.
Then
Requirements
with Required Skills list. ThenSkills
with Preferred skills list. We need to ensure we don't include any boilerplate like "If you are interested...". Remove. Now extract responsibilities list exactly as given, but remove duplicate line. Key Responsibilities text: "Designing and developing Microsoft Power Platform solutions for the organization (Power Apps, Power Automate, Power BI, Dataverse).Your responsibilities will also include developing business requirements, preparing change management documentation, coordinating solution release schedules, and providing testing and training support. You will work closely with a technical lead and actively participate in discussions throughout the development lifecycle.Debugging, optimizing, and maintaining existing low‑code applications and workflows.Identifying and mitigating technical risks and issues within Power Platform solutions.Collaborating closely with project teams, analysts, and other developers.Providing technical support and guidance to stakeholders on Power Platform capabilities.Reporting on project statuses and solution progress to senior team members.Partnering with IT management and business users to translate requirements into user stories and solution designs.Working with clients to prototype, refine, test, and troubleshoot applications and automated processes to meet business needs. Automated processes to meet business needs.Analyzing, defining, and documenting requirements related to data models, workflows, system integration, andbusiness processes." We need to split into sensible bullet points. The original is a run-on sentence; we can break at periods. Let's extract each sentence: 1. Designing and developing Microsoft Power Platform solutions for the organization (Power Apps, Power Automate, Power BI, Dataverse). 2. Your responsibilities will also include developing business requirements, preparing change management documentation, coordinating solution release schedules, and providing testing and training support. 3. You will work closely with a technical lead and actively participate in discussions throughout the development lifecycle. 4. Debugging, optimizing, and maintaining existing low‑code applications and workflows. 5. Identifying and mitigating technical risks and issues within Power Platform solutions. 6. Collaborating closely with project teams, analysts, and other developers. 7. Providing technical support and guidance to stakeholders on Power Platform capabilities. 8. Reporting on project statuses and solution progress to senior team members. 9. Partnering with IT management and business users to translate requirements into user stories and solution designs. 10. Working with clients to prototype, refine, test, and troubleshoot applications and automated processes to meet business needs. 11. Automated processes to meet business needs. (duplicate of part of 10? Actually it's a fragment; we should remove duplicate line.) 12. Analyzing, defining, and documenting requirements related to data models, workflows, system integration, and business processes. We should remove duplicate line #11. Now Required Skills list: "5 years of Expert experience in the Microsoft Power Platform environment developing solutions, particularly migrating exiting apps/solutions to the Power Platform. 5 years of Experience in MS SQL Technologies writing TSQL queries (Select, Insert, Delete, etc.)" We can split into two bullet points. Preferred skills list: "1 years of Knowledgeable with Microsoft DevOps or another Agile tool for tracking work 1 years Planning skills, including scope and development timeline estimating Excellent interpersonal, writing, and communication skills.Ability to work independently and complete projects with minimal supervision." We need to parse: It seems missing punctuation. We'll make bullet points: - 1 year of experience with Microsoft DevOps or another Agile tool for tracking work - 1 year of planning skills, including scope and development timeline estimating - Excellent interpersonal, writing, and communication skills - Ability to work independently and complete projects with minimal supervision Now About the role paragraph: Use the Job Description paragraph (the block after "Job Description:"). Let's copy that paragraph exactly: "Client is seeking a Microsoft Power Platform Developer for the upgrade and development of an existing Geotechnical Application. In this role, you will be required to design, write, deploy and maintain a Low Code Web application and possible future and ongoing projects. You will also be required to contribute to design and planning sessions as well as formulate approaches for current coding tasks. Candidate must have strong application architecture, design, and development skills. To ensure success as a Microsoft Low Code, Developer should have a strong grasp of the Microsoft Power Platform (Power Apps, Power Automate, Power BI), Azure services, and related low‑code capabilities. You should be skilled in building scalable apps, automating business processes, and solving problems in a fast‑paced environment. Low Code Developer will be able to perform end‑to‑end solution delivery, including the creation, maintenance, and enhancement of Power Platform applications. This is not a power platform administration role. Candidates will require experience deploying solutions and working within Power Platform Environments." We need to ensure we keep all info. Now construct HTML. We'll start with afor company intro. Then a
for job metadata (maybe using labels). Could also be a
with line breaks using
- items from Key Responsibilities.
Then