Data Platform Administrator

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. The posting includes Job Summary, Duties And Responsibilities, Education And Experience, Physical Demands/Requirements, Work Environment, Benefits. No explicit Pay or Schedule. So we should not create Pay or Schedule sections. We need to map content to appropriate headings: "About the role" could be Job Summary. "Responsibilities" could be Duties And Responsibilities. "Requirements" maybe Education And Experience? Or "Qualifications". The posting includes Education And Experience, Physical Demands/Requirements, Work Environment. We can combine Education And Experience as Qualifications or Requirements. Physical Demands/Requirements could be part of Requirements but maybe separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We have content for About the role (Job Summary). Responsibilities (Duties). Qualifications (Education And Experience). Possibly Skills (maybe from Education And Experience includes scripting, etc). Benefits (Benefits). Physical Demands/Requirements and Work Environment could be part of Requirements or maybe we can include as a separate section like "Working Conditions" but not in list; we should not create headings not in list unless we have content? The instruction says use those headings as examples, but we can use others? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings when appropriate. It doesn't forbid other headings, but better to stick to those. We have content that could map to Requirements (education/experience) and maybe Skills (specific technical skills). We could split Education And Experience into Qualifications and Skills. But we must not invent content. We can include both Qualifications and Skills headings if we have content for each. Let's extract: Education And Experience: - Bachelor’s degree in IT, CS, or equivalent experience. - Microsoft Certification in SQL systems administration (MCSA SQL Service) - Proven experience administering enterprise-scale databases (SQL Server preferred). - Experience with Microsoft Fabric. - Strong understanding of backup and recovery strategies, database security, performance tuning, and audit requirements. - Experience supporting mission-critical production systems. - Experience supporting ERP systems (e.g., JD Edwards or similar enterprise platforms). - Familiarity with high availability technologies and disaster recovery architectures. - Experience operating in a SOX-controlled or heavily audited environment. - Scripting or automation experience (PowerShell, T-SQL, or equivalent). Physical Demands/Requirements: - Constant operation of a computer and other office equipment... - Position is sedentary; must be able to remain in a stationary position... - Operates in an office environment and requires in-person presence (5 days/ week) - Ability to maintain, in your possession at all times, required medications... Work Environment: - Work is conducted in a professional office environment, with a collaborative and dynamic team setting and requires in-person presence. - BrightView Landscapes, LLC is an Equal Opportunity and E-Verify Employer. (EEO boilerplate to remove) - This job description is subject to change at any time. (boilerplate) - BrightView offers a suite or health, wellness, and financial benefits to full-time team members. Benefits offerings... (Benefits) - A detailed benefits package will be provided during the interview process. - It’s Not Just a Team. It’s One BrightView. (maybe tagline) We need to remove boilerplate: EEO, E-Verify, subject to change, etc. Also remove duplicated lines. Keep benefits content. Thus sections: About the role (Job Summary) Responsibilities (Duties And Responsibilities) Qualifications (Education And Experience) maybe also Skills (but we can include skills within Qualifications). Could also have Skills heading for specific technical skills like Microsoft Fabric, scripting, etc. But we already have them in Education And Experience. Might be redundant. Better to have Qualifications covering education/experience, and Skills covering technical skills. However the Education And Experience list includes both education and skills. We could split: Qualifications: Bachelor’s degree, Microsoft Certification, proven experience, experience with Fabric, etc. Skills: scripting, backup/recovery, performance tuning, etc. But we need to ensure we don't invent content; we can just put all under Qualifications and omit Skills heading if not needed. The instruction: Prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Qualifications, Benefits. Possibly also Working Conditions (Physical Demands/Requirements + Work Environment) but not in list; maybe we can incorporate into Qualifications? Not ideal. Could add a section "Working Conditions" but not in the example list; but instruction says use those headings (e.g...). It doesn't forbid others but better to stick to list. We could treat Physical Demands/Requirements and Work Environment as part of Qualifications? Not really. Maybe we can add a section "Requirements" for physical demands and work environment. The list includes Requirements as a possible heading. So we can have Requirements covering physical demands and work environment. That seems appropriate. Thus sections: - About the role (Job Summary) - Responsibilities (Duties And Responsibilities) - Requirements (Education And Experience + Physical Demands/Requirements + Work Environment) but we need to keep content separate? Could combine but risk mixing. Better to split: Qualifications for education/experience, Requirements for physical demands/work environment, Benefits for benefits. But we have both Qualifications and Requirements in list. Let's do: About the role Responsibilities Qualifications (Education And Experience) Requirements (Physical Demands/Requirements + Work Environment) Benefits We must not include Pay or Schedule as no content. Now we need to format:

About the role

then

Job Summary text

. Ensure we preserve all substantive information from Job Summary. Job Summary text: "The Enterprise Data Platform Administrator is responsible for the reliability, security, performance, and recoverability of BrightView’s production and non-production database environments. This role ensures that enterprise databases supporting core business platforms such as ERP, financial, operational, and reporting systems are properly maintained, secured, and compliant with internal controls and audit requirements. The Enterprise Data Platform Administrator operates as a control-bearing role with privileged access and is accountable for database availability, data integrity, backup and recovery, performance optimization, and adherence to change management and security standards." We need to keep that exactly. Responsibilities: The Duties And Responsibilities section includes many bullet-like paragraphs. We need to convert to

• . The text includes headings like Database Operations & Availability, Backup, Recovery & Disaster Recovery, etc. We should treat each bold heading as a subsection? But we only need list items for duties. Could keep each duty as a list item, preserving the content. The original text includes paragraphs under each heading. We could make each heading a
• with the paragraph inside. Or we could break into multiple list items for each duty. Simpler: treat each paragraph as a list item. Let's extract paragraphs: - Database Operations & Availability Administer, maintain, and support enterprise database platforms (primarily Microsoft SQL Server; additional platforms as applicable). Includes on-premise and Azure based.Ensure high availability and reliability of production databases through monitoring, maintenance, and proactive tuning.Perform routine health checks, patching, and upgrades in accordance with vendor guidance and internal change management procedures.Support database operations across production, test, development, and disaster recovery environments. - Backup, Recovery & Disaster Recovery Design, implement, and maintain database backup and recovery strategies aligned with business continuity requirements.Regularly test database restores and recovery procedures to validate data integrity and recovery objectives.Support disaster recovery planning and execution for database platforms, including failover testing and documentation. - Security, Access & Compliance Enforce least privilege access to database systems and data.Manage database authentication, authorization, and role assignments in accordance with access control policies.Support SOX, audit, and internal control requirements related to database access, change tracking, and logging.Participate in periodic privileged access reviews and provide audit evidence as required. - Performance & Optimization Monitor database performance and identify opportunities for optimization.Analyze query performance, indexing strategies, and resource utilization.Partner with application teams to resolve performance issues and improve scalability. - Change Management & Documentation Execute database changes through approved change management processes.Maintain accurate documentation including architecture diagrams, configuration standards, runbooks, and recovery procedures.Ensure database changes are traceable, auditable, and properly approved. - Application & Infrastructure Collaboration Work closely with application owners, systems engineers, cloud administrators, and vendors to support business systems.Partner with the data analytics team on design, implementation, and support of the Microsoft Fabric environment.Provide DBA expertise during application upgrades, migrations, and new system implementations.Support data integrations, reporting solutions, and downstream systems as required. - Key Controls & Accountability Custodian of production database platforms and data integrity.Control owner or key participant for database-related SOX and ITGC controls.Responsible for compliance with backup, recovery, access, and change management policies.Required participant in incident response involving data availability, corruption, or security events. We need to preserve all that. We'll output each as
• . Qualifications: Education And Experience list. We'll make each bullet as
• . The list includes many items separated by periods. We'll split by sentences? Better to keep each line as a bullet. The original text: "Bachelor’s degree in Information Technology, Computer Science, or equivalent experience.Microsoft Certification in SQL systems administration (MCSA SQL Service)Proven experience administering enterprise-scale databases (SQL Server preferred).Experience with Microsoft Fabric.Strong understanding of backup and recovery strategies, database security, performance tuning, and audit requirements.Experience supporting mission-critical production systems.Experience supporting ERP systems (e.g., JD Edwards or similar enterprise platforms).Familiarity with high availability technologies and disaster recovery architectures.Experience operating in a SOX-controlled or heavily audited environment.Scripting or automation experience (PowerShell, T-SQL, or equivalent)." We can split by period after each item (but some have internal periods like "e.g.,"). We'll approximate by splitting at each capital letter after a period? Simpler: treat each sentence as a bullet. We'll produce list items: - Bachelor’s degree in Information Technology, Computer Science, or equivalent experience. - Microsoft Certification in SQL systems administration (MCSA SQL Service) - Proven experience administering enterprise-scale databases (SQL Server preferred). - Experience with Microsoft Fabric. - Strong understanding of backup and recovery strategies, database security, performance tuning, and audit requirements. - Experience supporting mission-critical production systems. - Experience supporting ERP systems (e.g., JD Edwards or similar enterprise platforms). - Familiarity with high availability technologies and disaster recovery architectures. - Experience operating in a SOX-controlled or heavily audited environment. - Scripting or automation experience (PowerShell, T-SQL, or equivalent). That seems fine. Requirements: Physical Demands/Requirements + Work Environment (excluding EEO boilerplate). Let's extract: Physical Demands/Requirements: - Constant operation of a computer and other office equipment, such as a laptop, a cell phone, and printers/copiers - Position is sedentary; must be able to remain in a stationary position for the majority of time - Operates in an office environment and requires in-person presence (5 days/ week) - Ability to maintain, in your possession at all times, required medications to address any known allergic reactions should they occur Work Environment: - Work is conducted in a professional office environment, with a collaborative and dynamic team setting and requires in-person presence. - BrightView offers a suite or health, wellness, and financial benefits to full-time team members. Benefits offerings for full-time team members include medical, dental, and vision insurance, ancillary and voluntary products, a 401k savings plan with employer contributions, and 6 to 9 company paid holidays per year. Employees may also be eligible to