Low-Code Application Developer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the job posting. Key info: - Title: Full Time - Low-Code Application Developer (Mid level) (but we do not repeat as heading). - About the role: The first paragraph: "IEM is looking for a Full Time - Low-Code Application Developer (Mid level) to design, build, and maintain client facing business applications. The ideal candidate has hands-on experience delivering solutions on an enterprise low-code/no-code platform (such as Microsoft Power Platform, Appian, ServiceNow, Salesforce, or OutSystems), building forms, workflows, data models, and dashboards, and working in an agile team that ships on a regular release cadence." - Primary Location: Live anywhere that meets personal office /at home work requirements in the United States including Puerto Rico. Travel Requirements: occasional travel to client's office at DC. - Essential Functions: list of duties. - Minimum Qualifications: education, experience, etc. - Preferred Qualifications: list. - Additional Information: Office Locations, Personal Office requirements (internet speed). This could be part of Requirements or maybe separate but we can incorporate. - Benefits And More: Salary range $90,000 - $110,000/year, 10 paid Holidays, Vacation Pay, Sick Pay, 401(K) plan with matching, Company paid STD and LTD. - Also EEO etc, but we remove boilerplate. We need to produce sections: About the role (maybe a paragraph), Responsibilities (list of essential functions), Requirements (maybe combine Minimum Qualifications and Preferred Qualifications? Could separate into Qualifications and Skills). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. We need to decide what goes where. We have: - About the role: description. - Responsibilities: essential functions list. - Requirements: maybe Minimum Qualifications (education, experience, citizenship, etc.) - Qualifications: maybe Preferred Qualifications. - Skills: maybe specific skills like analytical, problem-solving, communication, etc. Could be derived from Minimum Qualifications: Strong analytical and problem-solving skills, ability to translate business requirements, strong written and verbal communication skills, self-directed, collaborative mindset, commitment to quality. - Benefits: list of benefits. - Pay: salary range. - Schedule: maybe not specified; we have no explicit schedule info (full-time). The posting says Full Time. Could we include Schedule? It says Full Time. That's schedule info. Should we include a Schedule section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Full Time (implies schedule). It also says "Full Time - Low-Code Application Developer". So we can include Schedule with "Full-time". However, we need to check if they explicitly state schedule: "Full Time - Low-Code Application Developer (Mid level)". That indicates full-time. So we can include Schedule section with "Full-time". But we need to avoid filler like "not specified". It's specified. Thus we will include Schedule. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

IEM is looking for a Full Time - Low-Code Application Developer (Mid level) to design, build, and maintain client facing business applications. The ideal candidate has hands-on experience delivering solutions on an enterprise low-code/no-code platform (such as Microsoft Power Platform, Appian, ServiceNow, Salesforce, or OutSystems), building forms, workflows, data models, and dashboards, and working in an agile team that ships on a regular release cadence.

Responsibilities

• Design, configure, build, test, and deploy applications on an enterprise low-code platform, including forms, custom modules, portals, and interactive dashboards.
• Develop automated workflows, approval routing, notifications, and integrations with enterprise data sources and APIs.
• Model and maintain relational data structures supporting application and reporting needs.
• Participate in agile ceremonies (sprint planning, daily stand-ups, sprint reviews, retrospectives) and deliver working increments in two-week sprints.
• Support release activities, including regression testing, deployment, and post-release troubleshooting.
• Produce and maintain technical documentation, and support end-user documentation and training as needed.
• Follow security, accessibility, and configuration-management standards for an enterprise IT environment.

Requirements

• Bachelor’s degree in Computer Science, Information Systems, Engineering, or a related field.
• Five (5) + years of software development.
• Two - Three (2 - 3)+ years hands‑on experience in a low‑code platform.
• Hands‑on experience building applications on an enterprise low‑code/no‑code platform, including forms, workflow automation, and data modeling.
• Experience developing dashboards or reports using a business intelligence tool (e.g., Power BI, Tableau, or equivalent).
• Experience working in agile/scrum delivery teams.
• Strong written and verbal communication skills, with the ability to gather requirements directly from business stakeholders.
• U.S. citizenship and the ability to obtain and maintain a federal Public Trust suitability determination.
• Self‑directed and productive in a remote, distributed team environment.
• Collaborative mindset and comfort working directly with non‑technical stakeholders.
• Commitment to quality, documentation, and continuous improvement.

Qualifications

• Platform certifications (e.g., Microsoft PL‑series, Appian, ServiceNow, or Salesforce developer certifications).
• Experience integrating low‑code applications with collaboration platforms such as SharePoint or Teams.
• Experience supporting federal or public sector clients, including familiarity with IT security and compliance requirements (e.g., FISMA, FedRAMP, Section 508).
• Exposure to scripting or data tooling such as SQL, Python, or JavaScript.
• Experience with application lifecycle management across development, test, and production environments.

Skills

• Strong analytical and problem‑solving skills with attention to detail.
• Ability to translate business requirements into working, maintainable solutions.
• Strong written and verbal communication skills.
• Self‑directed and productive in a remote, distributed team environment.
• Collaborative mindset and comfort working with non‑technical stakeholders.
• Commitment to quality, documentation, and continuous improvement.

Benefits

• 10 paid holidays
• Vacation pay
• Sick pay
• 401(K) plan with matching
• Company paid STD and LTD

Pay

Salary will be based on experience and location: $90,000 - $110,000 per year.

Schedule

Full‑time position.

We need to ensure we didn't include boilerplate like EEO, reasonable accommodation, office locations, personal office internet requirements. Those are additional info but maybe we could include them under Requirements? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Office Locations and Personal Office requirements might be considered not boilerplate but maybe considered additional info. However they are not explicitly listed as headings we must include; we could incorporate them into Requirements or maybe a separate section like "Work Environment". But the allowed headings list does not include Work Environment. We could put them under Requirements as extra bullets. However the instruction: "Prefer a few substantive sections over many thin ones." So we could merge those into Requirements or maybe a separate "Additional Information" but not in allowed headings. Safer to incorporate into Requirements. We have already a long Requirements list; we could add bullets for office location flexibility and internet requirements. But we need to check if they are substantive: "Primary Location: Live anywhere that meets personal office /at home work requirements in the United States including Puerto Rico. Travel Requirements This position may require occasional travel to client's office at DC to complete work assignments or attend meetings." and "Personal Office: All personal office work environments require the ability to maintain minimum Internet speeds of 25 Mbps upload and 3 Mbps download, as well as a ping rate of 100 ms or less during working hours, regardless of the type and number of devices using your Internet connection. You must also have account privileges and access to your Internet service provider account during working hours for the purposes of maintaining the Internet connection, if needed." These are substantive. We could add them under Requirements or maybe a separate "Work Location" but not allowed. Let's add them under Requirements as additional bullets. Thus Requirements bullets will include education, experience, citizenship, etc., plus location flexibility, travel, internet requirements. We need to avoid duplication: we already have some similar points like self-directed, collaborative mindset etc. Those are in Skills; we could keep them there. Now check for any duplicated lines: we have "Strong written and verbal communication skills" appears both in Requirements and Skills. Might be okay but could be considered duplicate. We could remove from Requirements to avoid duplication. The instruction: remove duplicated lines. So we should ensure not to repeat same exact line. Let's adjust. In Requirements we have "Strong written and verbal communication skills, with the ability to gather requirements directly from business stakeholders." In Skills we have "Strong written and verbal communication skills." That's similar but not identical; still could be considered duplicate. To be safe, we could remove the communication skill from Requirements and keep it in Skills, or keep both but maybe it's okay. I'd rather remove from Requirements to avoid duplication. Similarly "Self‑directed and productive in a remote, distributed team environment." appears in Requirements and Skills. Remove from Requirements. "Collaborative mindset and comfort working directly with non‑technical stakeholders." appears in Requirements and Skills. Remove from Requirements. "Commitment to quality, documentation, and continuous improvement." appears in Requirements and Skills. Remove from Requirements. Thus Requirements will focus on education, experience, technical qualifications, citizenship, location, travel, internet. Now we need to ensure we didn't miss any substantive info: The "Essential Functions" list we used for Responsibilities. Good. Now we need to check for any other sections like "About the role" we already have. Now check for any mention of "Pay" we have salary range. Now "Schedule": we have full-time. Now "Benefits": we have list. Now ensure we didn't include any boilerplate like EEO, reasonable accommodation, office locations (we incorporated location flexibility and travel). We also incorporated personal office internet requirements. Now we need to output only HTML fragment. Let's craft final HTML. We'll need to escape any special characters? Not needed. We'll produce:

About the role

...

Responsibilities

...

Requirements

...

Qualifications

...

Skills

...

Benefits

...

Pay