Business Applications Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. The posting includes Overview (description), Essential Functions broken down with percentages, Education And Experience, Skills/Abilities, Work Environment, Physical Demands. We need to map to sections: About the role (overview), Responsibilities (essential functions), Requirements (maybe education and experience?), Qualifications (maybe certifications?), Skills (skills/abilities), Benefits (none mentioned), Pay (none), Schedule (none). So we should include About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly also Work Environment? Not in list of allowed headings; only those given. So we cannot add Work Environment heading. We could incorporate work environment details into About the role or Responsibilities? But we must not invent sections. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are allowed headings. We should only use those headings if content exists. So we can include About the role, Responsibilities, Requirements, Qualifications, Skills. No Benefits, Pay, Schedule. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID etc. We need to format lists with

• for any list of duties/requirements/benefits. Use

  for prose. We need to extract content. About the role: Overview paragraph(s). The overview: "The Business Applications Engineer administers and supports Alterman's enterprise business applications, covering the construction, financial, human resources, project management, and business productivity platforms the company runs on. This role owns the day to day administration, configuration, and support of an assigned set of applications, and works directly with the departments that use them to translate business process into system configuration. This role participates in the full application lifecycle, including evaluation, implementation, integration, upgrade, and retirement, and supports the licensing, renewal, and software asset records that go with it. Complex configuration decisions, integration design, and commercial terms are escalated to the senior level of the function. Thorough documentation of application configurations, integrations, and operational activity is a core responsibility of this role." We can put that in a

  . Responsibilities: Essential Functions broken down with percentages and bullet-like sentences. We need to create a list. The essential functions have sections: Enterprise Application Administration (40%), Implementation, Integration & Projects (20%), License Administration & Software Asset Records (15%), Software Evaluation Support (10%), Documentation, Training & Compliance (10%), plus 5% other duties. We should capture each bullet as list items. Could combine percentages into description. Must preserve all detail. So each bullet could be a

• containing the description. We need to avoid repeating headings inside list? It's fine. Requirements: Education And Experience section. Contains: Bachelor's degree in Computer Science, Information Technology, Information Systems, Business Administration, or related field preferred; equivalent combination of education and experience will be considered. Minimum of 3-5 years of experience administering enterprise business applications required; OR minimum of 5 years of progressive technology experience. Experience with Microsoft 365 administration required. Experience administering a construction ERP, or HRIS platform preferred. Experience with scripting and automation tools such as PowerShell preferred. One Microsoft Associate-level certification required, held at placement or obtained within twelve months; Microsoft Expert-level certification preferred. Additional certifications preferred (e.g., Procore Certified Administrator, UKG Pro certification, ITIL 4 Foundation). We can put that as a

  or list? It's prose; could be

  . But we could also break into list items for each requirement. The instruction: use

  • for any list of duties/requirements/benefits. So we should treat requirements as a list. So each distinct requirement could be a
  • . However we need to preserve all detail; we can split into items. Qualifications: Might be overlapping with Requirements? The posting doesn't have a separate Qualifications section besides Education And Experience and Skills/Abilities. But we could treat Certifications as Qualifications? However the heading "Qualifications" is allowed; we need to see if there is specific content for it. The posting includes certifications under Education And Experience (Microsoft Associate-level certification required, Expert-level preferred, Additional certifications preferred). Also Skills/Abilities includes skills. So we could put certifications under Qualifications. But we must not invent content; we need to see if there is a distinct "Qualifications" block. Not explicitly labeled. However we could treat the certification requirements as Qualifications. But we must not create a heading if the posting doesn't have real specific content for it. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Does the posting have specific content for Qualifications? It mentions certifications, but not under a heading "Qualifications". However we could still create a Qualifications section containing the certification details, as that is substantive content. The heading is allowed; we just need to ensure we have content. I think it's acceptable to create Qualifications section for certifications. Skills: Skills/Abilities section. We must not include Benefits, Pay, Schedule. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

    About the role

    ...overview...

    Responsibilities

    • Enterprise Application Administration (40%): Administers, configures, and supports an assigned set of enterprise business applications, including construction management, ERP, HRIS, CRM, project portfolio, and business productivity platforms. Manages user accounts, roles, permissions, and workflow configuration within assigned applications. Provides technical support and troubleshooting for business application issues and escalates complex configuration and integration problems to the senior level of the function. Administers Microsoft 365 services as they support the business application portfolio, including groups, permissions, and collaboration settings. Monitors application health and performance, and reports issues and improvement opportunities. Works directly with department users to understand business process and configure the system to match it.
    • Implementation, Integration & Projects (20%): Executes application rollouts, upgrades, migrations, and configuration changes under the direction of the senior level of the function. Builds and maintains integrations between business applications and enterprise platforms, including single sign-on, identity provisioning, and data feeds. Performs testing and validation of application changes before release, and coordinates user communication. Assists with data conversion, cleanup, and reconciliation during application migrations.
    • License Administration & Software Asset Records (15%): Maintains accurate license assignment and entitlement records across assigned applications. Runs recurring license and access reviews, identifies unused assignments, and reclaims them. Maintains the software asset inventory, including owner, renewal date, entitlement count, and contract reference. Supports provisioning and deprovisioning accuracy for joiner, mover, and leaver events across business applications.
    • Software Evaluation Support (10%): Supports the evaluation of new business application requests, including functional testing, integration review, and licensing model comparison. Coordinates vendor demonstrations and proof of concept exercises, and gathers stakeholder feedback. Gathers renewal and pricing information for contract review, and tracks renewal dates ahead of expiration. Documents evaluation findings and recommendations for review at the senior level.
    • Documentation, Training & Compliance (10%): Creates and maintains documentation for application configurations, integrations, processes, and procedures. Develops knowledge base articles and delivers end user and Service Desk training on business applications. Provides audit evidence for compliance activities, including NIST CSF 2.0, CMMC, and SOC 2, for applications in scope. Documents incidents affecting business applications, including root cause and corrective action.
    • Other duties (5%): Performs other duties as assigned.

    Requirements

    • Bachelor's degree in Computer Science, Information Technology, Information Systems, Business Administration, or related field preferred; equivalent combination of education and experience will be considered.
    • Minimum of 3-5 years of experience administering enterprise business applications required; OR minimum of 5 years of progressive technology experience.
    • Experience with Microsoft 365 administration required.
    • Experience administering a construction ERP, or HRIS platform preferred.
    • Experience with scripting and automation tools such as PowerShell preferred.
    • One Microsoft Associate-level certification required, held at placement or obtained within twelve months; Microsoft Expert-level certification preferred.
    • Additional certifications preferred (e.g., Procore Certified Administrator, UKG Pro certification, ITIL 4 Foundation).

    Qualifications

    • Microsoft Associate-level certification required (or obtained within 12 months); Microsoft Expert-level certification preferred.
    • Additional certifications such as Procore Certified Administrator, UKG Pro certification, ITIL 4 Foundation are preferred.
    But note we already listed certifications in Requirements; duplicating may be redundant. Perhaps better to not duplicate; we could put certifications under Qualifications and keep Requirements focused on education/experience. However the instruction says preserve ALL substantive information; we must not lose any. So we need to include certification info somewhere. We could split: Requirements includes education/experience; Qualifications includes certifications. That way we preserve all. Thus Requirements list: education, years experience, Microsoft 365 admin, construction ERP/HRIS experience, PowerShell scripting. Qualifications list: Microsoft Associate-level certification required (or within 12 months), Expert-level preferred, Additional certifications preferred (Procore Certified Administrator, UKG Pro certification, ITIL 4 Foundation). Now Skills section: Skills/Abilities bullet list. We need to capture each skill as list item. Skills/Abilities list: - Strong communication and interpersonal skills, with the ability to explain application behavior to non-technical business users. - Ability to translate a described business process into system configuration, and to document the result. - Solid knowledge of enterprise application administration, including role-based access, workflow configuration, and reporting. - Working understanding of identity and access management, single sign-on, and Microsoft Entra ID. - Ability to build and maintain integrations using APIs, connectors, and integration platforms. - PowerShell scripting proficiency for administration and licensing at scale. - Strong documentation skills, including configuration records, runbooks, and knowledge base articles. - Excellent troubleshooting and problem-solving skills, with the ability to trace an issue across integrated systems. - Able to manage multiple assigned applications and project tasks against committed dates. - Able to work independently and as part of a team, and to provide after-hours support as needed. We'll put each as
  • . Now ensure we didn't miss any substantive info: Work Environment and Physical Demands are not included because no allowed heading. Could we incorporate them into About the role or Responsibilities? The instruction says we must preserve ALL substantive information. If we omit them, we lose info. But we cannot create new headings not allowed. However we could add them as paragraphs under About the role or Responsibilities? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g., those). It might be okay to use other headings, but they gave examples. Safer to stick to those headings only. However we must preserve all substantive info; we could embed Work Environment and Physical Demands into About the role as additional paragraphs. That would preserve them without new headings. Let's do that: after overview paragraph, add another paragraph for Work Environment and Physical Demands. Thus About the role will have two

    elements: overview, then work environment/physical demands.