LMS Administrator

We need to output HTML fragment with sections: About the role (maybe "About The Role" heading), Responsibilities (What You’ll Do), Requirements (Who You Are), Qualifications (Required Education & Experience). Also maybe Benefits? The posting includes "More Information Please visit ... Click here to view a listing of employee benefits". That's a link to benefits but not actual benefits list. According to rules: do NOT create Benefits section unless posting actually states them. It only mentions a link to view benefits, not actual benefits. So we should not include Benefits. Pay? It says "Pay Basis Salary". That's a mention of pay basis but not actual salary amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It states "Pay Basis Salary". That's a statement about pay basis, but not actual pay. Is that enough? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay Basis Salary, which is a statement about pay. However they also say "Prefer a few substantive sections over many thin ones." Might be better to include a Pay section with that info? But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay Basis Salary, so we could include a Pay section with that line. However they also say "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "Pay Basis Salary" is not filler; it's a specific statement. So we could include a Pay section with that sentence. Schedule? Not mentioned. So no Schedule. We need headings:

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include those with real content. We have content for About the role (the paragraph "About The Role"). Responsibilities (What You’ll Do). Requirements (Who You Are). Qualifications (Required Education & Experience). Skills? The "Who You Are" includes domain expertise, LMS proficiency, virtual tools, software suite, core competencies. That could be considered Skills. But we already have Requirements section; maybe we split into Requirements and Skills? The instruction: use headings for those categories if content exists. We could put "Who You Are" under Requirements (domain expertise, etc.) and then Qualifications for education. Or we could have Requirements (domain expertise, LMS proficiency, virtual tools, software suite) and Skills (core competencies). But the posting lumps them together. To avoid thin sections, better to combine into one Requirements section that includes both domain expertise and core competencies. Then Qualifications for education. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Check if we need to include "Location Pittsburgh, PA" and "Job Function Systems Administration and Support Position Type Staff – Regular Full time/Part time Full time". That's metadata; we can fold into a short

maybe under About the role or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a

after the heading for location, job function, position type. Or we can include in About the role section as a paragraph. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting. Let's extract content: Who We Are paragraph: "The SEI helps advance software engineering principles and practices and serves as a national resource in software engineering, computer security, and process improvement. The SEI works closely with defense and government organizations, industry, and academia to continually improve software-intensive systems. Its core purpose is to help organizations improve software engineering capabilities and develop or acquire the right software, defect-free, within budget and on time, every time." That's about the organization; could be included as an introductory paragraph before sections. Not a heading. We'll keep as a

. About The Role: "Primary technical support for both asynchronous eLearning and Live-Online learning sessions. Ensure that learners and instructors have the uninterrupted, high-quality digital environment they need to succeed." What You’ll Do: list items: - LMS Administration - System Administration: Build, configure, and deploy training content within the LMS as directed by the LMS Lead. - Data Integrity: Manage student enrollments for live-online sessions and ensure all student records are accurately updated upon course completion. - Reporting: Generate and distribute weekly reports regarding client training status and learner progress. - Documentation: Maintain meticulous documentation of system settings, workflows, and standard operating procedures to ensure continuity. - Virtual Learning & Support - Live-Online Moderation: Act as the technical moderator for virtual classroom sessions, supporting instructors to ensure smooth delivery of content. - Technical Readiness: Audit and ensure all technical requirements (audio, video, connectivity) are optimized for online deliveries. - Help-Desk Support: Serve as the first point of contact for troubleshooting technical issues related to SEI eLearning and SEI Live-Online Learning platforms. We need to output as

• for any list of duties/requirements/benefits. So we need to structure lists. Could have top-level items for LMS Administration and Virtual Learning & Support, each with sublist? The instruction: use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll do nested
    . Who You Are: Domain Expertise: Proven experience in Educational Technology or a closely related field. LMS Proficiency: Hands-on experience managing Learning Management Systems (experience with Docebo is highly preferred). Virtual Tools: Strong technical command of video-conferencing platforms (specifically Zoom) and collaborative digital environments. Software Suite: Proficiency in Microsoft Office products and modern collaborative tools used for training content development. Core Competencies: Communication: Excellent verbal and written communication skills for interacting with both technical teams and non-technical learners. Time Management: A demonstrated ability to juggle multiple tasks, manage competing priorities, and meet deadlines in a fast-paced environment. Problem-Solving: A proactive approach to troubleshooting technical hurdles in real-time. We can make a list. Required Education & Experience: Education: Bachelor’s Degree Location Pittsburgh, PA Job Function Systems Administration and Support Position Type Staff – Regular Full time/Part time Full time Pay Basis Salary We need to include Pay section with "Pay Basis Salary". Could be a

    . We must not include boilerplate like "More Information Please visit ... Click here to view a listing of employee benefits Carnegie Mellon University is an Equal Opportunity Employer/Disability/Veteran. Statement of Assurance". Remove that. Now construct HTML. Start with

    for Who We Are. Then

    About the role

    Primary technical support for both asynchronous eLearning and Live-Online learning sessions. Ensure that learners and instructors have the uninterrupted, high-quality digital environment they need to succeed.

    Then maybe a

    for location/job function/position type/pay basis? Could be separate

    after About the role. But we also have Pay section later. Let's decide: After About the role, we can have a

    containing: Location: Pittsburgh, PA. Job Function: Systems Administration and Support. Position Type: Staff – Regular Full time. (Note: Full time/Part time Full time seems redundant; we keep as given). Pay Basis: Salary. Then

    Responsibilities

    then nested lists. Then

    Requirements

    then list. Then

    Qualifications

    then

    Education: Bachelor’s Degree

    We could also include Pay section:

    Pay

    Pay Basis: Salary

    but we already included Pay Basis in metadata paragraph. To avoid duplication, maybe better to have Pay section separate and not duplicate. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we put Pay Basis in metadata paragraph, we still preserve it. Having a separate Pay section would duplicate. Better to keep it in metadata paragraph and not have a Pay section. However the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay Basis Salary, but we are not creating a Pay section; we are including that info in a paragraph. That's fine. Thus we will not have a Pay heading. Now ensure we don't repeat job title as heading. Not needed. Now output only HTML fragment. Let's craft:

    The SEI helps advance software engineering principles and practices and serves as a national resource in software engineering, computer security, and process improvement. The SEI works closely with defense and government organizations, industry, and academia to continually improve software-intensive systems. Its core purpose is to help organizations improve software engineering capabilities and develop or acquire the right software, defect-free, within budget and on time, every time.

    About the role

    Primary technical support for both asynchronous eLearning and Live-Online learning sessions. Ensure that learners and instructors have the uninterrupted, high-quality digital environment they need to succeed.

    Location: Pittsburgh, PA. Job Function: Systems Administration and Support. Position Type: Staff – Regular Full time. Pay Basis: Salary.

    Responsibilities

    • LMS Administration
      • System Administration: Build, configure, and deploy training content within the LMS as directed by the LMS Lead.
      • Data Integrity: Manage student enrollments for live-online sessions and ensure all student records are accurately updated upon course completion.
      • Reporting: Generate and distribute weekly reports regarding client training status and learner progress.
      • Documentation: Maintain meticulous documentation of system settings, workflows, and standard operating procedures to ensure continuity.
    • Virtual Learning & Support
      • Live-Online Moderation: Act as the technical moderator for virtual classroom sessions, supporting instructors to ensure smooth delivery of content.
      • Technical Readiness: Audit and ensure all technical requirements (audio, video, connectivity) are optimized for online deliveries.
      • Help-Desk Support: Serve as the first point of contact for troubleshooting technical issues related to SEI eLearning and SEI Live-Online Learning platforms.

    Requirements

    • Domain Expertise: Proven experience in Educational Technology or a closely related field.
    • LMS Proficiency: Hands-on experience managing Learning Management Systems (experience with Docebo is highly preferred).
    • Virtual Tools: Strong technical command of video-conferencing platforms (specifically Zoom) and collaborative digital environments.
    • Software Suite: Proficiency in Microsoft Office products and modern collaborative tools used for training content development.
    • Core Competencies
      • Communication: Excellent verbal and written communication skills for interacting with both technical teams and non-technical learners.
      • Time Management: A demonstrated ability to juggle multiple tasks, manage competing priorities, and meet deadlines in a fast-paced environment.
      • Problem-Solving: A proactive approach to troubleshooting technical hurdles in real-time.

    Qualifications

    Education: Bachelor’s Degree

    Check for any missing info: The posting also had "Who We Are" paragraph we included. Good. We removed boilerplate. Check for any duplicate lines: none. Check for any placeholder text: none. All good. Now output only HTML fragment.