Principal Database Administrator

We need to output HTML fragment with sections: About the role? Actually the posting includes "Your journey as a Principal Database Administrator starts here!" then description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to extract content. Let's parse: - About the role: The first paragraph: "Your journey as a Principal Database Administrator starts here! This role is essential to maintaining the stability, security, and availability of GovCloud database environments that support Epicor customers. The Principal Database Administrator design, implement, and support databases to meet business requirements, develop database strategies, and ensure robust system monitoring. You will play a key role in advising management, mentoring team members, and driving best practices for database management. We are seeking applicants with strong leadership, analytical thinking, and creative problem-solving skills." That's about the role. - Responsibilities: The "What You Will Be Doing" bullet list (actually sentences). We need to list each duty as

. The text includes multiple sentences separated by periods. We'll break them into list items. List: - Advise management on database concepts and functional capabilities, translating data models or user specifications into designs that comply with standards, guidelines, procedures, and processes. - Install, configure, and maintain database management system product software on database and application servers. - Design, implement, and maintain complex databases, including access methods, access time, device allocation, validation checks, organization, protection, and security. - Apply telemetry and observability practices to interpret database metrics, and other operational signals using Datadog or comparable monitoring tools; identify patterns, anomalies, and potential root causes to improve database reliability and performance. - Deliver formal and informal training, mentorship, and support to other Database Admins. - Recommend and implement best practices, keeping up with external trends to incorporate into products and processes. - Lead and manage database projects, ensuring deadlines are met and schedules are maintained. - Requirements: The "What You Will Likely Bring" list. List: - 8+ years’ applicable experience and demonstrated success/knowledge, including 3+ years of specialized or industry experience. - Bachelor of Science degree in Information Technology, Computer Science, or a related field, or equivalent practical experience. - Ability to propose and implement new ideas, lead a team to meet deadlines, and manage schedules effectively. - Excellent written and oral communication skills, with the ability to mentor others. - Analytical thinking and creative problem-solving skills. - Recognized as a thought leader and change agent. - Expertise in running Microsoft Access queries and updates, with broad database management experience. - Qualifications: Might be similar to Requirements? The posting includes "Sponsorship", "Export Control" sections. Those are not typical headings but could be considered Qualifications? However we only output sections if they have real content. The "Sponsorship" and "Export Control" are specific content but not in the allowed headings list. The allowed headings are limited to About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could map Sponsorship and Export Control into Qualifications or Requirements? Probably they are part of Requirements (eligibility). But we have to preserve all substantive information. We could include them under Requirements as additional items. - Skills: Not explicitly listed but we could infer from responsibilities: maybe "Skills" section could be omitted if no explicit skills list. The instruction: include a section ONLY when the posting has real, specific content for it. There's no explicit "Skills" heading. So we should not create Skills section. - Benefits: The posting includes "Competitive Pay & Benefits" with bullet list of benefits. So we need Benefits section. - Pay: The posting mentions "Competitive Pay & Benefits" but does not give specific pay amount. It says "Competitive Pay & Benefits" but no actual pay figure. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states "Competitive Pay & Benefits" but not actual pay. Is that considered stating them? It says "Competitive Pay & Benefits" as a heading, but no specific pay. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Since they didn't give a specific pay figure, we should not create a Pay section. However we could include the phrase "Competitive Pay & Benefits" as part of Benefits? But Benefits section already includes benefits list. The phrase "Competitive Pay & Benefits" is a heading; we could treat it as part of Benefits section description. But we should not create a Pay section. - Schedule: Not mentioned. So no Schedule section. - Qualifications: Could be separate from Requirements. The posting includes "Sponsorship" and "Export Control" which are qualifications/eligibility. Could also include "Bachelor of Science degree" etc. But we already put those under Requirements. Might be better to split: Requirements = experience, education, abilities; Qualifications = sponsorship, export control, thought leader etc. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine them into Requirements. But we need to preserve all info. Let's keep Requirements as the list of experience/education/abilities, and Qualifications as sponsorship and export control and thought leader etc. However "Recognized as a thought leader and change agent" is more like a skill/quality. Could go under Qualifications. But we need to decide. Let's extract sections: About the role: as above. Responsibilities: list. Requirements: list of experience, education, ability to propose ideas, communication skills, analytical thinking, problem-solving. Qualifications: list of thought leader, expertise in Microsoft Access queries, sponsorship, export control. Skills: maybe not needed. Benefits: list. We must not include Pay or Schedule. Now format HTML. We'll output:

About the role

Your journey as a Principal Database Administrator starts here! This role is essential to maintaining the stability, security, and availability of GovCloud database environments that support Epicor customers. The Principal Database Administrator design, implement, and support databases to meet business requirements, develop database strategies, and ensure robust system monitoring. You will play a key role in advising management, mentoring team members, and driving best practices for database management. We are seeking applicants with strong leadership, analytical thinking, and creative problem-solving skills.

Responsibilities

• Advise management on database concepts and functional capabilities, translating data models or user specifications into designs that comply with standards, guidelines, procedures, and processes.
• Install, configure, and maintain database management system product software on database and application servers.
• Design, implement, and maintain complex databases, including access methods, access time, device allocation, validation checks, organization, protection, and security.
• Apply telemetry and observability practices to interpret database metrics, and other operational signals using Datadog or comparable monitoring tools; identify patterns, anomalies, and potential root causes to improve database reliability and performance.
• Deliver formal and informal training, mentorship, and support to other Database Admins.
• Recommend and implement best practices, keeping up with external trends to incorporate into products and processes.
• Lead and manage database projects, ensuring deadlines are met and schedules are maintained.

Requirements

• 8+ years’ applicable experience and demonstrated success/knowledge, including 3+ years of specialized or industry experience.
• Bachelor of Science degree in Information Technology, Computer Science, or a related field, or equivalent practical experience.
• Ability to propose and implement new ideas, lead a team to meet deadlines, and manage schedules effectively.
• Excellent written and oral communication skills, with the ability to mentor others.
• Analytical thinking and creative problem-solving skills.

Qualifications

• Recognized as a thought leader and change agent.
• Expertise in running Microsoft Access queries and updates, with broad database management experience.
• Sponsorship: This position is not eligible for employment-based immigration sponsorship now or in the future. Applicants must be authorized to work in the United States without Epicor sponsorship.
• Export Control: This position requires access to customer information subject to U.S. export-control laws, including the International Traffic in Arms Regulations (ITAR). Candidates must be U.S. persons as defined by applicable law or otherwise eligible to obtain any required U.S. government authorization to access such information. Any offer of employment is contingent upon Epicor’s determination that the candidate can lawfully be provided the access required for the position. For these purposes, a U.S. person generally includes a U.S. citizen or national, lawful permanent resident, refugee, or asylee.

Benefits

• Health and Wellness: Comprehensive health and wellness benefits designed to support your overall well-being.
• Internal Mobility: Opportunities for mentorship, continuing education, and focused career goal setting, with 25% of positions filled internally.
• Career Development: Free LinkedIn Learning licenses for everyone, along with our Mentoring Program to boost your personal development.
• Education Support: Geographically specific programs to balance the cost of education with the benefits of continued learning and personal development.
• Inclusive Workplace: Collaborate with a diverse team in an inclusive, global workplace that fosters innovation and celebrates partnership.
• Work-Life Balance: Policies built on mutual trust and support, encouraging time off to rest, recharge, and reconnect.
• Global Mobility: Comprehensive support for international relocations and permanent residency processes.

We must not include any extra text. Ensure no markdown fences. Just HTML. Check for any boilerplate: we removed Equal Opportunities and Accommodations Statement, Recruiter Mouy Bun, etc. Also removed "Competitive Pay & Benefits" heading as we didn't create Pay section. But we kept benefits list. The phrase "Competitive Pay & Benefits" is not included; we could optionally include a sentence before benefits list but not required. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The phrase "Competitive Pay & Benefits" is substantive? It's a heading that indicates benefits exist. Since we are already listing benefits, we could include a short paragraph before the list:

Competitive Pay & Benefits

. But that would be a heading-like text but not a heading tag. It's okay to include as a paragraph. However the rule: Use

for prose. So we could add a

Competitive Pay & Benefits

before the

. That preserves the phrase. Let's do that. Thus Benefits section:

Benefits

Competitive Pay & Benefits

...
Check if any other substantive info: "We’re Proactive, Proud, Partners." etc. That's boilerplate? It's part of About Epicor section which we omitted because we didn't have About Epicor as a section. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The About Epicor paragraph is descriptive of company; could be considered "About the role"? Actually we already have About the role. The Epicor description is more about company, not role. Should we include it? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The About Epicor paragraph is substantive. But we have no section for company description. Could we add it under About the role as additional paragraph? The About the role section currently includes the initial description. We could append