Technical Support Engineer - Power App

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to parse the posting. Content: Role Description: "We are seeking an experienced Power Platform professional with strong functional and technical capabilities across Microsoft Power Platform products The role requires hands-on expertise in application support low code solution development automation troubleshooting and customer facing collaboration The ideal candidate should be comfortable working in fast paced support or engineering environments and be able to contribute across Power Apps Power Automate desktop automation and AI enabled experiences" That's description; could be "About the role". We'll put that in

. Minimum Qualifications: list of items. We'll put under Requirements or Qualifications? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where each piece fits. We have Minimum Qualifications (list). Also Good to Have Skills (list). Also PODSpecific Skills (list broken into subcategories). Also Other Details (compensation, benefits). Also Benefits/perks listed. We need to extract substantive info. Let's extract: - About the role: description paragraph. - Responsibilities: Not explicitly listed; maybe implied: "hands-on expertise in application support low code solution development automation troubleshooting and customer facing collaboration", "contribute across Power Apps Power Automate desktop automation and AI enabled experiences". Could treat as responsibilities. We'll create Responsibilities section with bullet list. - Requirements: Minimum Qualifications list. - Qualifications: maybe same as Requirements? But we can combine? The instruction says prefer few substantive sections over many thin ones. We could have Requirements covering minimum qualifications, and Skills covering good to have and PODSpecific skills. - Skills: Good to Have Skills + PODSpecific Skills (maybe combine). Could separate into Skills (technical) and maybe "Preferred Skills". But we have only one Skills heading allowed. We'll put all skill-related items under Skills. - Benefits: Benefits/perks listed. - Pay: compensation range info: "Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity." Also "The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations." etc. That's pay info. We'll include Pay section with that paragraph. - Schedule: mention flexibility to work in different shifts outside local business hours and when required cover a weekend day based on business needs. That's schedule. We must not include boilerplate like EEO etc. Remove that. Now format. We need

headings, then content: either

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. Let's extract each bullet. Minimum Qualifications list (as sentences separated by line breaks? In text they are separated by spaces but we can parse): - Good hands on experience with CRM or enterprise application platforms such as Dynamics 365 SAP Salesforce PeopleSoft or related technologies - Experience in SaaS product support web frontend development or quality assurance - Working knowledge of programming languages such as C and Python - Good understanding of database technologies such as SQL Server or Oracle - Strong communication skills including verbal written and active listening abilities - Experience in a customer facing service or support role - Strong interpersonal and collaboration skills demonstrated through work experience - Passion for continuous learning and professional development - Strong research problem solving and troubleshooting skills with the ability to use available tools and resources effectively - Flexibility to work in different shifts outside local business hours and when required cover a weekend day based on business needs Note: The last one about flexibility is also schedule; but it's in Minimum Qualifications. We'll keep it there maybe but also schedule section. Might duplicate; but we should not duplicate content? The instruction: preserve ALL substantive information; do not invent or summarize away detail. If it's in Minimum Qualifications, we should keep it there. However schedule section also needed if posting actually states schedule. The posting does state flexibility to work in different shifts etc. So we could include that in Schedule section, but we must not omit it from Minimum Qualifications if we keep it there. Could we move it to Schedule and remove from Minimum Qualifications? That would be removing detail, not allowed. So we need to keep it in Minimum Qualifications as well. It's okay to have overlapping info; but we should not duplicate exactly same sentence? Might be okay but could be considered duplication. However instruction says preserve ALL substantive information; doesn't forbid duplication. But better to avoid duplication by moving it to Schedule and removing from Minimum Qualifications? That would be removing detail from Minimum Qualifications (the flexibility sentence). That would be losing info. So we keep it in both places? Might be okay but could be considered redundant. However we could rephrase? Not allowed to invent or summarize away detail; but we could keep the sentence as is in Minimum Qualifications and also include in Schedule (same sentence). That's preserving detail, not losing. It's duplication but not losing info. Acceptable. Now Good to Have Skills list: - Experience integrating Power Platform with external systems using connectors APIs and data gateways - Knowledge of extending Power Platform capabilities using custom connectors plugins JavaScript or Azure Functions - Understanding of security user roles permissions and compliance controls within Power Platform environments - Exposure to Microsoft Dataverse bot frameworks and building copilots or agents using generative AI capabilities Now PODSpecific Skills: It's a big list with headings inside like Power Apps, Copilot Studio, Microsoft Dataverse, Customization and Configuration, Integration Services, Custom Development, Security and Compliance, Environment and Release Management, Power Automate, Power Automate for Desktop. We need to preserve all. We'll treat each bullet under Skills maybe with subheadings? But we cannot add extra headings beyond the allowed ones? The instruction only says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? It says use

  for section headings (list). Likely they expect only those headings. So we should not add other headings like

  . We'll just list items under Skills as a flat list, preserving each item. Thus Skills section will contain a long list combining Good to Have Skills and PODSpecific Skills items. We need to ensure we don't lose any detail. Let's extract PODSpecific Skills items: Under "Power Apps Power Apps Strong capability in building custom business applications using canvas apps model driven apps and portals with low code or no code approaches" - Strong capability in building custom business applications using canvas apps, model driven apps and portals with low code or no code approaches "Copilot Studio Knowledge of building conversational agents and AI driven support experiences with the ability to integrate with Dynamics 365 CE Microsoft Teams and third party applications Understanding of single sign on SSO is preferred" - Knowledge of building conversational agents and AI driven support experiences with the ability to integrate with Dynamics 365 CE, Microsoft Teams and third party applications - Understanding of single sign on (SSO) is preferred "Microsoft Dataverse Understanding of Dataverse data modelling including tables relationships and its use as a core data source for Power Platform applications" - Understanding of Dataverse data modelling including tables, relationships and its use as a core data source for Power Platform applications "Customization and Configuration Ability to customize user interfaces business rules forms and views to meet business requirements" - Ability to customize user interfaces, business rules, forms and views to meet business requirements "Integration Services Proficiency in integrating Power Platform with external systems using connectors APIs and data gateways" - Proficiency in integrating Power Platform with external systems using connectors, APIs and data gateways "Custom Development Knowledge of extending Power Platform using plugins custom connectors JavaScript and Azure Functions" - Knowledge of extending Power Platform using plugins, custom connectors, JavaScript and Azure Functions "Security and Compliance Ability to implement role based security permissions and compliance controls within the Power Platform ecosystem" - Ability to implement role based security permissions and compliance controls within the Power Platform ecosystem "Environment and Release Management Experience managing environments solution lifecycle management version control and change deployment using DevOps and ALM practices" - Experience managing environments, solution lifecycle management, version control and change deployment using DevOps and ALM practices "Power Automate Power Automate Proficiency in building cloud flows and business process automation across services and applicationsAdvanced Automation Components Handson experience with custom connectors on-premises data gateways and dataflowsCopilot and Governance Understanding of Copilot capabilities within Power Automate and awareness of data loss prevention DLP policies governance and administrative controlsCopilot Studio Administration Exposure to publishing administration and integration of agents created using Copilot StudioPower Automate for Desktop PAD Proficiency in building desktop automation workflows along with experience in machine setup installation and configuration" We need to split that into sensible bullets: - Proficiency in building cloud flows and business process automation across services and applications - Hands-on experience with custom connectors, on-premises data gateways and dataflows - Understanding of Copilot capabilities within Power Automate and awareness of data loss prevention (DLP) policies, governance and administrative controls - Exposure to publishing, administration and integration of agents created using Copilot Studio - Proficiency in building desktop automation workflows (Power Automate for Desktop) along with experience in machine setup, installation and configuration Now Benefits list: - Comprehensive Medical Plan Covering Medical, Dental, Vision - Short Term and Long-Term Disability Coverage - 401(k) Plan with Company match - Life Insurance - Vacation Time, Sick Leave, Paid Holidays - Paid Paternity and Maternity Leave Pay section: we have paragraphs: "Actual compensation within the range will be dependent upon the individual's skills, experience, performance and internal equity." "The range displayed on each job posting reflects the minimum and maximum salary target for the position across all US locations. Within the range, individual pay is determined by work location and job level and additional factors including job-related skills, experience, and relevant education or training. Depending on the position offered, other forms of compensation may be provided as part of overall compensation like an annual performance-based bonus, sales incentive pay and other forms of bonus or variable compensation." "Disclaimer: The compensation and benefits information provided herein is accurate as of the date of this posting." We should keep that disclaimer? It's about compensation and benefits info; it's substantive. We'll include in Pay section maybe as a note. Schedule section: we have flexibility to work in different shifts outside local business hours and when required cover a weekend day based on business needs. Also maybe other schedule info? Not else. Now About the role: we have the initial paragraph. Responsibilities: we can derive from description: "hands-on expertise in application support low code solution development automation troubleshooting and customer facing collaboration", "contribute across Power Apps Power Automate desktop automation and AI enabled experiences". Also maybe "working in fast paced support or engineering environments". We'll create bullet list. Now we need to ensure we don't include boilerplate like EEO etc. Remove that. Now produce HTML. Structure:

  About the role

  We are seeking an experienced Power Platform professional with strong functional and technical capabilities across Microsoft Power Platform products. The role requires hands-on expertise in application support, low-code solution development, automation, troubleshooting and customer-facing collaboration. The ideal candidate should be comfortable working in fast-paced support or engineering environments and be able to contribute across Power Apps, Power Automate, desktop automation and AI-enabled experiences.

  Responsibilities

  • Provide hands-on expertise in application support
  • Develop low-code solutions
  • Implement automation and troubleshooting
  • Engage in customer-facing collaboration
  • Contribute across Power Apps, Power Automate, desktop automation and AI-enabled experiences
  • Work in fast-paced support or engineering environments

  Requirements

  • Good hands-on experience with CRM or enterprise application