Lead Infrastructure Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. The posting includes description of responsibilities, requirements, benefits. No explicit pay or schedule details (except work shift: 1st shift). That's schedule info: "Work Shift: 1st shift (United States of America)". That's schedule info. So we can include Schedule section with that. Benefits: there is a paragraph describing benefits. So include Benefits. About the role: maybe we can include a short prose summarizing the role? The posting includes "Please review the following job description:" then responsibilities. Could treat "About the role" as a brief description: maybe combine first sentences? But we must not invent content. We can use the initial sentences before responsibilities? The text: "Responsible for the installation, configuration and production turnover of Truist Database Services and servers Provide and assist with the creation of database(s), database schema and support for logical model with developments. Maintain documentation, backup and recovery procedure for the physical and logical databases. Includes developing, monitoring and maintaining backup and recovery solutions. Assist with application developers, business users and project managers in the development of user access requirements, logical and physical database design, and disaster recovery as needed. Assist with review of vendor configurations and patches adhering to best practices where allowed. Provide technical writings and detailed documentation on technology standards and procedures. Work with engineers groups on OS settings and recommendations. Work with disk storage management group to determine appropriate disk platform and disk allocation configuration to support desired physical design and performance. Provide performance measures of transactional databases, identifying bottlenecks, disk analysis and other metrics to provide tuning recommendations. Provide engineering support for industry best of breed applications for management of database systems and related security functions identifying risk. Ability to make decisions for implementation, build and configuration for RDBMS and integration into the environment. Provide both solution blocks low -level designs for database systems. Provide escalation support for the Change, Release, Incident, Request and Configuration Management processes for Truist Database Services technologies and services. Work closely with Production Engineering to maintain a product roadmap aligned with the business needs of Truist Data and Technology Services and appropriate team leads. Perform database reviews with Operations peer contacts for evergreen efforts and product changes or releases. Research and maintain a current understanding of available and evolving RDBMS and Database Service technology trends. Project Execution and Service Design. Tactical Operational Support & Technical Planning." That's essentially responsibilities. So we could put that under Responsibilities heading. For About the role, maybe we could include a short summary like "The position is responsible for installation, configuration, and production turnover of Truist Database Services and servers..." but that's basically same as responsibilities. Might be okay to omit About the role if no distinct content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not add About the role if we don't have distinct content. We could maybe use the first sentence as About the role? But that's still part of responsibilities. Safer to omit About the role. Qualifications: The posting includes "Must have Bachelor’s degree..." etc. That's qualifications. Also "Requirements" includes similar content. Actually they have "Requirements" heading in the posting. So we can map that to Requirements section. Qualifications maybe overlapping. Could combine? But we need to decide which sections to include. The posting has "Requirements" with bullet-like list. Also includes "Must have Bachelor’s degree..." and experience etc. That's qualifications. Could treat that as Requirements. Could also have Skills: they list technical skills: Microsoft Windows Server versions, SQL Server versions, RDBMS, etc. That's skills. So we can have Skills section. Thus sections: Responsibilities, Requirements, Skills, Benefits, Schedule. We must not repeat job title. No markdown. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information. So we need to capture all responsibilities as list items? The responsibilities are many sentences; we could break each sentence into

• . That would preserve detail. Similarly for requirements list. We need to extract benefits paragraph: "General Description of Available Benefits for Eligible Employees of Truist Financial Corporation: All regular teammates (not temporary or contingent workers) working 20 hours or more per week are eligible for benefits, though eligibility for specific benefits may be determined by the division of Truist offering the position. Truist offers medical, dental, vision, life insurance, disability, accidental death and dismemberment, tax-preferred savings accounts, and a 401k plan to teammates. Teammates also receive no less than 10 days of vacation (prorated based on date of hire and by full-time or part-time status) during their first year of employment, along with 10 sick days (also prorated), and paid holidays. For more details on Truist’s generous benefit plans, please visit our Benefits site. Depending on the position and division, this job may also be eligible for Truist’s defined benefit pension plan, restricted stock units, and/or a deferred compensation plan. As you advance through the hiring process, you will also learn more about the specific benefits available for any non-temporary position for which you apply, based on full-time or part-time status, position, and division of work." We need to keep all that. Could put as

  or

  • . Since it's prose, we can use

    . But we could also break into list items for each benefit. The instruction: Use

    • for any list of duties/requirements/benefits. So benefits list should be
      • . So we should extract each benefit item: medical, dental, vision, life insurance, disability, accidental death and dismemberment, tax-preferred savings accounts, 401k plan, vacation (10 days), sick days (10 days), paid holidays, defined benefit pension plan, restricted stock units, deferred compensation plan. Also mention eligibility conditions. Might be better to keep as prose? But instruction says use list for benefits. We'll create
        • for each benefit item. Also include eligibility statements maybe as separate

          . But we can incorporate eligibility as part of list? Might be okay to have a

          for eligibility description then

          for benefits. Schedule: "Work Shift: 1st shift (United States of America)". That's schedule info. Could be a

          . Now Responsibilities: we need to break each sentence into

          • . Let's list them: 1. Responsible for the installation, configuration and production turnover of Truist Database Services and servers 2. Provide and assist with the creation of database(s), database schema and support for logical model with developments. 3. Maintain documentation, backup and recovery procedure for the physical and logical databases. 4. Includes developing, monitoring and maintaining backup and recovery solutions. 5. Assist with application developers, business users and project managers in the development of user access requirements, logical and physical database design, and disaster recovery as needed. 6. Assist with review of vendor configurations and patches adhering to best practices where allowed. 7. Provide technical writings and detailed documentation on technology standards and procedures. 8. Work with engineers groups on OS settings and recommendations. 9. Work with disk storage management group to determine appropriate disk platform and disk allocation configuration to support desired physical design and performance. 10. Provide performance measures of transactional databases, identifying bottlenecks, disk analysis and other metrics to provide tuning recommendations. 11. Provide engineering support for industry best of breed applications for management of database systems and related security functions identifying risk. 12. Ability to make decisions for implementation, build and configuration for RDBMS and integration into the environment. 13. Provide both solution blocks low -level designs for database systems. 14. Provide escalation support for the Change, Release, Incident, Request and Configuration Management processes for Truist Database Services technologies and services. 15. Work closely with Production Engineering to maintain a product roadmap aligned with the business needs of Truist Data and Technology Services and appropriate team leads. 16. Perform database reviews with Operations peer contacts for evergreen efforts and product changes or releases. 17. Research and maintain a current understanding of available and evolving RDBMS and Database Service technology trends. 18. Project Execution and Service Design. 19. Tactical Operational Support & Technical Planning. Note some are fragments; but we keep as is. Now Requirements: The posting says: "Requirements Must have Bachelor’s degree in Computer Science, Computer Engineering, IT, IS, or related technical fieldMust have 5 years of progressive experience in development or application support positions performing/utilizing the following:In-depth knowledge of information systems and ability to identify, apply, and implement best practicesDemonstrated knowledge of business processes and competitive strategies related to the IT functionPlanning and managing projectsProviding direction and mentoring less experienced teammatesIdentifying risk and security gaps and concerns and developing remediation plans.Microsoft Windows Server 2008 R2 and 2012 R2, 2016, 2019Microsoft SQL Server 2008, 2008R2, 2012 and 2014, 2016, 2019RDBMS, platforms and VLDBs.Disaster Recovery and Replication with implementation skillsConfiguration and tuning capabilities, including RDBMS, IO and metric gatheringScripting capabilities within the OS to assist with automation and gathering metrics for analysisSecurity and Risk AwarenessReadying vendor security bulletins and correlating to enterprise environment" We need to parse into list items. Let's break: - Must have Bachelor’s degree in Computer Science, Computer Engineering, IT, IS, or related technical field - Must have 5 years of progressive experience in development or application support positions performing/utilizing the following: - In-depth knowledge of information systems and ability to identify, apply, and implement best practices - Demonstrated knowledge of business processes and competitive strategies related to the IT function - Planning and managing projects - Providing direction and mentoring less experienced teammates - Identifying risk and security gaps and concerns and developing remediation plans. - Microsoft Windows Server 2008 R2 and 2012 R2, 2016, 2019 - Microsoft SQL Server 2008, 2008R2, 2012 and 2014, 2016, 2019 - RDBMS, platforms and VLDBs. - Disaster Recovery and Replication with implementation skills - Configuration and tuning capabilities, including RDBMS, IO and metric gathering - Scripting capabilities within the OS to assist with automation and gathering metrics for analysis - Security and Risk Awareness - Readying vendor security bulletins and correlating to enterprise environment We could flatten. Now Skills: Could be overlapping with requirements technical skills. But we can separate: maybe list technical skills: Microsoft Windows Server versions, Microsoft SQL Server versions, RDBMS, platforms, VLDBs, Disaster Recovery and Replication, Configuration and tuning, Scripting capabilities, Security and Risk Awareness, Readying vendor security bulletins. But we already listed many as requirements. To avoid duplication, we could treat Requirements as the list of qualifications (degree, experience, etc.) and Skills as the technical competencies. However the posting lumps them together. But we can still create Skills section with the technical items. Let's define: Skills: - Microsoft Windows Server 2008 R2, 2012 R2, 2016, 2019 - Microsoft SQL Server 2008, 2008R2, 2012, 2014, 2016, 2019 - RDBMS, platforms and VLDBs - Disaster Recovery and Replication (implementation skills) - Configuration and tuning capabilities (including RDBMS, IO and metric gathering) - Scripting capabilities within the OS to assist with automation and