OnBase Systems Administrator & Architect

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, navigation, etc. Also remove "Job Summary", "JOB DESCRIPTION" maybe not needed. The job title is already shown, so we don't repeat as heading. We need to parse the posting. Key sections: - Job Summary: "The OnBase Systems Administrator & Architect leads the design, administration, governance, optimization, and strategic evolution of enterprise Hyland OnBase environments supporting federal, state, and local government programs. This role combines enterprise architecture responsibilities with hands-on system administration and serves as the primary technical authority for the OnBase platform, ensuring security, scalability, performance, reliability, and alignment with business objectives. The position is remote and may require up to 10% travel." That could go under "About the role" (or maybe "Job Summary" but we only have allowed headings; "About the role" is allowed). So we put that as

About the role

then

with that text. - Responsibilities: The "Job Duties" section with sub-bullets: Platform Architecture & Strategy, System Administration, Solution Design & Development Support, Security, Compliance & Operational Leadership, Other duties as required, Supervisory Responsibilities N/A (we can ignore N/A). We need to output a list

• for duties. Should we keep subheadings? Probably not required; we can just list each duty as a bullet. But we need to preserve all substantive info. Could embed subheadings inside
• maybe as bold? But we cannot add extra tags not specified? The instruction only says use
  • for any list of duties/requirements/benefits, and

    for prose. It doesn't forbid other tags inside

  • . But to be safe, we can put the duty description as plain text inside
  • . We could include the subheading as part of the text. Thus

    Responsibilities

    then
    with each duty bullet. List items: - Defines and maintains enterprise-wide OnBase architecture standards and technical roadmaps; designs scalable content management, workflow, and case management solutions using OnBase; evaluates Hyland technologies and establishes governance standards for solution design, security, integrations, and deployments; provides technical leadership and architecture reviews for major OnBase initiatives. - Administers and maintains OnBase environments across Development, QA, UAT, and Production; configures and supports document types, keyword types, retention, forms, reports, dashboards, and WorkView applications; manages access, security groups, privileges, authentication integrations, upgrades, patches, migrations, and deployments; monitors system health, performance, storage, and availability; troubleshoot complex application, database, workflow, and integration issues. - Architects and oversees WorkView, Workflow, Unity Forms, Document Composition, Reporting Dashboards, and API-based solutions; partners with development teams on technical designs, coding standards, scalability, maintainability, and security compliance; supports integrations with Azure services, REST APIs, identity providers, ERP, GIS, CRM, and external government systems; assists with SQL design, reporting, and performance optimization. - Ensures alignment with government security requirements and organizational governance standards; supports audits, access reviews, disaster recovery testing, business continuity planning, and security incident resolution; maintains platform documentation, system diagrams, operational procedures, and configuration inventories; provides Tier III escalation support, lead root cause analysis, and mentor developers, administrators, and technical analysts; supports proposals, solution estimates, and technical discovery sessions for new programs. - Other duties as required. Supervisory Responsibilities N/A: we can ignore as it's N/A. - Requirements: The posting has "Education Qualifications, Knowledge, Skills and Abilities:" then bullet list of qualifications. Also there is "Experience" etc. We need to separate Requirements vs Qualifications vs Skills? The allowed headings include Requirements, Qualifications, Skills. We need to decide where to put each piece. The posting includes: Education Qualifications, Knowledge, Skills and Abilities: - Bachelor's degree in Computer Science, Information Systems, Engineering OR seven (7) or more years of experience in information technology or enterprise system administration, required Experience: - Seven (7) or more years of Hyland OnBase experience, required - Five (5) or more years of enterprise system administration experience, required - Experience administering multi-environment OnBase implementations and supporting large-scale production environments, required - Experience designing enterprise content management and workflow solutions, required - Experience with SQL Server administration, optimization, and reporting, required - Experience with change management, release processes, disaster recovery, and high availability architectures, preferred Certifications/Licensure: - One or more OnBase certifications, preferred: OCSA OCI OCWA OCWE WorkView API - Microsoft Azure certification, preferred - Agile development, DevOps, and CI/CD experience, preferred Software Proficiency: - Proficiency with OnBase Configuration, OnBase Studio, WorkView, Workflow, Unity Forms, Document Composition, Integration Services, and Reporting Dashboards, required - Proficiency with Microsoft SQL Server, REST APIs, API integrations, Azure-hosted environments, and authentication technologies including Active Directory, Azure AD, SSO, and MFA, required Other Knowledge, Skills, & Abilities: - Demonstrated understanding of enterprise architecture principles, platform governance, strategic planning, systems integration methodologies, and technical leadership practices within complex technology environments. - Strong skills in risk management, client communication, technical and business documentation, process improvement, problem-solving, mentoring, and cross-functional collaboration. - Ability to lead and influence technical and business stakeholders, manage competing priorities, and drive project deliverables in a fast-paced environment. - Proven ability to evaluate business and technical requirements, develop scalable solutions, and support organizational objectives through effective planning and execution. - Strong interpersonal and relationship management skills, with the ability to communicate complex technical concepts to both technical and non-technical audiences. - Ability to travel up to 10% as required We need to map these to sections. Potential approach: - Qualifications: Education and experience requirements (maybe combine Education and Experience). Could put under

    Qualifications

    with a list. - Skills: Software proficiency and other knowledge, skills, abilities (like communication, leadership). Could put under

    Skills

    . - Requirements: Could be certifications? Or maybe we treat "Requirements" as the mandatory items (required) and "Preferred" as optional? But the instruction says include a section only when posting has real specific content for it. We have content for Qualifications, Skills, maybe Requirements (like certifications?). However we already have Education and Experience under Qualifications. Certifications could be under Requirements or Skills. Let's decide: We could have:

    Qualifications

    (Education + Experience)

    Skills

    (Software proficiency + Other Knowledge, Skills, & Abilities)

    Requirements

    (Certifications/Licensure) maybe also include "One or more OnBase certifications, preferred" etc. But those are preferred not required. However they are still content. Could also put under Skills. But we need to avoid thin sections. Perhaps combine Certifications into Skills as well. Alternatively, we could have: - About the role - Responsibilities - Qualifications (Education + Experience) - Skills (Software proficiency + Other Knowledge, Skills, & Abilities + Certifications) That seems reasonable. No separate Requirements section unless we have specific mandatory requirements like "required" items beyond education/experience. But we already captured required items in Qualifications and Skills. The posting also mentions "Ability to travel up to 10% as required" which is in Other Knowledge, Skills, & Abilities; we can keep there. Pay and Schedule: Not mentioned besides remote and up to 10% travel. No explicit pay or schedule details. So we should NOT create Pay or Schedule sections because they are not stated. Benefits: The posting includes a section "About Us" and then mentions benefits: "BDO provides assurance, tax, and advisory services..." then later: "We are proud to be an ESOP company, offering participants a stake in the firm’s success through beneficial ownership and a unique opportunity to enhance their financial well-being. As a qualified retirement plan, the ESOP is a meaningful addition to our comprehensive compensation and Total Rewards benefits* offerings. It also reinforces an ownership mindset..." Also "Learn more about our benefits: BDO Total Rewards encompass more than traditional benefits. Click here to find out more ! Benefits may be subject to eligibility requirements." Thus there is some benefits info: ESOP, Total Rewards, etc. We should include a Benefits section with that content. However we must avoid boilerplate like "Click here to find out more !" maybe we can keep the substantive description: ESOP, stake in firm's success, qualified retirement plan, addition to compensation and Total Rewards benefits, ownership mindset. Also mention that benefits may be subject to eligibility requirements. We can include that. We should not include navigation/legal/EEO etc. So we strip the Equal Opportunity Employer lines. Thus final HTML:

    About the role

    The OnBase Systems Administrator & Architect leads the design, administration, governance, optimization, and strategic evolution of enterprise Hyland OnBase environments supporting federal, state, and local government programs. This role combines enterprise architecture responsibilities with hands-on system administration and serves as the primary technical authority for the OnBase platform, ensuring security, scalability, performance, reliability, and alignment with business objectives. The position is remote and may require up to 10% travel.

    Responsibilities

    • Defines and maintains enterprise-wide OnBase architecture standards and technical roadmaps; designs scalable content management, workflow, and case management solutions using OnBase; evaluates Hyland technologies and establishes governance standards for solution design, security, integrations, and deployments; provides technical leadership and architecture reviews for major OnBase initiatives.
    • Administers and maintains OnBase environments across Development, QA, UAT, and Production; configures and supports document types, keyword types, retention, forms, reports, dashboards, and WorkView applications; manages access, security groups, privileges, authentication integrations, upgrades, patches, migrations, and deployments; monitors system health, performance, storage, and availability; troubleshoot complex application, database, workflow, and integration issues.
    • Architects and oversees WorkView, Workflow, Unity Forms, Document Composition, Reporting Dashboards, and API-based solutions; partners with development teams on technical designs, coding standards, scalability, maintainability, and security compliance; supports integrations with Azure services, REST APIs, identity providers, ERP, GIS, CRM, and external government systems; assists with SQL design, reporting, and performance optimization.
    • Ensures alignment with government security requirements and organizational governance standards; supports audits, access reviews, disaster recovery testing, business continuity planning, and security incident resolution; maintains platform documentation, system diagrams, operational procedures, and configuration inventories; provides Tier III escalation support, lead root cause analysis, and mentor developers, administrators, and technical analysts; supports proposals, solution estimates, and technical discovery sessions for new programs.
    • Other duties as required.

    Qualifications

    • Bachelor's degree in Computer Science, Information Systems, Engineering OR seven (7) or more years of experience in information technology or enterprise system administration, required.
    • Seven (7) or more years of Hyland OnBase experience, required.
    • Five (5) or more years of enterprise system administration experience, required.
    • Experience administering multi-environment OnBase implementations and supporting large-scale production environments, required.
    • Experience designing enterprise content management and workflow solutions, required.
    • Experience with SQL Server administration, optimization, and reporting, required.
    • Experience with change management, release