Jira Administrator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real, specific content for it—never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Key content: - Who We Are: description of Point32Health. This could be "About the role"? Actually "Who We Are" is about organization. Could be considered "About the role"? But we have a section "About the role" maybe we can use that for description of role? The posting includes "Job Summary" and "Job Description". So we can have sections: About the role (maybe from Who We Are? but that's about company). Could treat "Who We Are" as "About the role"? Not exactly. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which sections to include based on content. We have: - Job Summary: description of Jira Administrator role. - Job Description: Key Responsibilities/Duties (top five) but actually they list many responsibilities (more than five). We'll treat as Responsibilities. - Qualifications – What You Need To Perform The Job: includes Certification and Licensure, Education Required, Experience Required, Skill Requirements (Communication Skills, Leadership Skills, Additional Characteristics And Skills, Technical Skills And Knowledge). Also Working Conditions and Additional Requirements. - Salary Range: $82,902.50 - $124,353.74 - Compensation & Total Rewards Overview: description of benefits (medical, dental, vision, retirement plans, paid time off, employer-paid life and disability insurance, tuition program, well-being benefits, full suite of benefits). This is Benefits. - Also there is "Working Conditions and Additional Requirements" which could be part of Requirements or Qualifications. We need to avoid boilerplate: disclaimer, scam alert, EEO statement, etc. We need to preserve all substantive info: So we need to include the Who We Are description? It's about the organization, not the role. Might be considered "About the role"? The instruction says we can use About the role heading for section headings. It might be appropriate to include the Who We Are content under About the role (or maybe About the company). Since they said "About the role" as example, but we can still use it for organization description. It's substantive. We need to avoid repeating job title as heading (the page already shows it). So we won't add a heading for Jira Administrator. We need to not put Job ID/requisition numbers as headings (none present). We need to remove duplicated lines: there may be duplicate skill lists (Technical Skills And Knowledge repeats earlier). We'll consolidate. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for section headings. Use

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

    for prose. We need to decide sections: Potential sections: - About the role (or About the company): includes Who We Are paragraph(s) and Job Summary. - Responsibilities: list of duties from Key Responsibilities/Duties. - Qualifications: includes Education Required, Experience Required, Skill Requirements (Communication Skills, Leadership Skills, Additional Characteristics And Skills, Technical Skills And Knowledge). Could be split into Requirements and Skills? But we have separate headings for Requirements, Qualifications, Skills. The instruction says we can use those headings. We need to decide which to use to avoid thin sections. Prefer few substantive sections over many thin ones. So maybe combine Education, Experience, Skills into a single "Qualifications" section, with sub-lists? But we need to use

    • for any list. Could have nested lists? Probably okay to have multiple
      inside section. We could have sections: - About the role (includes Who We Are and Job Summary) - Responsibilities (list of duties) - Qualifications (Education, Experience, Skills) - Benefits (from Compensation & Total Rewards Overview) - Pay (Salary Range) - Working Conditions (maybe part of Qualifications? Could be separate but might be thin. Could include under Qualifications as additional info.) We need to avoid filler like "commensurate with experience". Not present. We need to ensure we don't create sections with only placeholder text. Let's extract substantive content. Who We Are: "Point32Health is a leading not-for-profit health and well-being organization dedicated to delivering high-quality, affordable healthcare. Serving nearly 2 million members, Point32Health builds on the legacy of Harvard Pilgrim Health Care and Tufts Health Plan to provide access to care and empower healthier lives for everyone. Our culture revolves around being a community of care and having shared values that guide our behaviors and decisions. We’ve had a long-standing commitment to inclusion and equal healthcare access and outcomes, regardless of background; it’s at the core of who we are. We value the rich mix of backgrounds, perspectives, and experiences of all of our colleagues, which helps us to provide service with empathy and better understand and meet the needs of the communities where we serve, live, and work. We enjoy the important work we do every day in service to our members, partners, colleagues and communities. Learn more about who we are at Point32Health." We can keep that as prose. Job Summary: "The Jira Administrator supports the administration, configuration, and maintenance of the Atlassian Jira platform. This role works closely with business stakeholders, project teams, Scrum teams, and IT personnel to ensure Jira is operating effectively and meeting organizational needs. The ideal candidate has a foundational understanding of Agile methodologies, issue tracking, workflow management, and user support. This position is well suited for an individual early in their Atlassian administration career who is looking to expand their expertise in Jira configuration, automation, reporting, and platform governance." We can combine with Who We Are under About the role. Responsibilities: The list under "Key Responsibilities/Duties – what you will be doing (top five):" then a bunch of bullet-like sentences separated by periods. We need to turn each duty into
      • . Let's extract each duty sentence: - Acts as primary point of contact between the Application Management Services (AMS) and Systems Engineering Services (SES) departments. - Works with Infrastructure Services to coordinate the management of middleware with operating system and hardware requirements. - Coordinates maintenance of business applications across platforms. - Defines system topology for enterprise business services and middleware services. - Monitors, reports, and analyzes metrics to meet or exceed the business’ expectations for availability and performance of critical enterprise services. - Works with System Engineering Services and Network Engineering to create high availability, redundant service deployments. - Maintains documentation that defines and describes the service environment. - Troubleshoots and provides production support for applications across platforms. - Provides input to plan, develop and document enterprise recovery plans and disaster recovery guidelines. - Engages in monitoring and environmental tuning to identify areas where optimization is necessary. - Defines system requirements for applications. - Monitors performance tests, approach to performance tests and defines the correct tests to be used. - Responsible for planning and requirement gathering for corporate and IT only projects. - Participate on multiple cross-departmental committees. - Perform root cause analysis on high severity issues. - Other duties and projects as assigned. We need to keep all. Qualifications: Education Required (minimum): Bachelor’s degree in Computer Science or equivalent Preferred: Master’s degree Experience Required (minimum): 3-5 years related experience Java Virtual Machine performance tuning Experience with 1 or more of the following operating systems: Windows, Linux Experience with 2 or more of the following host platforms: WebSphere Application Server, WebSphere Portal, Apache Tomcat, Apache HTTP Server, JBoss Application Server Preferred: 3-5 years of experience in computer science Skill Requirements: Communication Skills: - Listens well and clearly expresses questions to elicit understanding. - Actively listens to colleagues and applies information gathered to work assignments. - Proactively and regularly interacting with others, via written and verbal communications. - Demonstrates positive, respectful, and professional communications style in written communications, group meetings, and individual meetings. - Communicates and escalates issues to peers, team leader/manager, and others, as appropriate - Ability to effectively communicate technical information to the business. Leadership Skills: - Demonstrates leadership through individual contributions: - Positive and professional attitude and interactions - Taking initiative to collaborate with and assist team members - Demonstrates self-motivation and persistency in successful completion of assignments Additional Characteristics And Skills: - Tasks are performed across multiple platforms - Must understand dependencies among systems and across departments in IS - Broad experience rather than depth in one specialized area of expertise - Maintain expert level of industry and technical knowledge base Technical Skills And Knowledge: - Java Virtual Machine performance tuning. - Experience with 1 or more of the following operating systems: Windows, Linux - Experience with 2 or more of the following host platforms: WebSphere Application Server, WebSphere Portal, Apache Tomcat, Apache HTTP Server, JBoss Application Server Note: Some duplication with Experience Required. We'll keep but maybe combine. Working Conditions and Additional Requirements: - 24 hour on-call responsibilities - Weekend and after-hour work as needed - Must be able to work under normal office conditions and work from home as required. - Work may require simultaneous use of a telephone/headset and PC/keyboard and sitting for extended durations. - May be required to work additional hours beyond standard work schedule. CONFIDENTIAL DATA: ... This is boilerplate? It's about confidentiality, maybe we should keep? It's substantive but maybe considered boilerplate? It's a policy statement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Confidential data statement might be considered legal boilerplate. Safer to remove. Disclaimer: remove. Salary Range: $82,902.50 - $124,353.74 Compensation & Total Rewards Overview: description of benefits. We need to produce Benefits section with list: Medical, dental and vision coverage, Retirement plans, Paid time off, Employer-paid life and disability insurance with additional buy-up coverage options, Tuition program, Well-being benefits, Full suite of benefits to support career development, individual & family health, and financial health. We can turn each into
      • . Pay section: just the salary range as prose. Schedule: Not explicitly given; we have working conditions includes on-call, weekend, after-hour, etc. Could be considered Schedule. But we have Working Conditions section maybe. The instruction says include a section ONLY when posting has real, specific content for it. We have specific content about working conditions (24 hour on-call, weekend, after-hour, etc.). So we could make a Schedule section with those details. However we also have Working Conditions and Additional Requirements which includes those plus other conditions (office conditions, work from home, telephone/headset, sitting, additional hours). Could be considered Schedule? Might be better to have a "Working Conditions" section (not in the list of examples but we can still use heading? The examples list includes Benefits, Pay, Schedule. They didn't list Working Conditions but we could still use Schedule for shift/hours info. The other conditions like office conditions, work from home, telephone/headset, sitting, additional hours could be considered part of Schedule or maybe we can incorporate into Qualifications? But we already have many sections. We need to avoid many thin sections. Perhaps combine Working Conditions into Schedule section (since it's about hours and conditions