Lead System Engineering - Database Architecture and Engineering
Responsibilities
. Also "What You'll Bring" is qualifications/requirements. Could map toRequirements
orQualifications
. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have "About The Team" which is like About the role/team. Could use About the Team
but they said e.g. About the role. We'll use About the Team as heading. Then Responsibilities for What You'll Do. Then Requirements or Qualifications for What You'll Bring. Since they list Required Qualifications, we can use Requirements
or Qualifications
. Probably Requirements is fine. We'll include - for lists.
We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title. Must not include boilerplate like office presence, relocation, sponsorship, etc? Actually those are substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The lines about office presence, relocation, sponsorship are not boilerplate? They are job specifics. Should we keep? They are not navigation/legal/EEO. They are job details: "This position requires office presence of a minimum of 5 days per week and is only located in the location(s) posted. No relocation is offered. AT&T will not hire any applicants for this position who require employer sponsorship now or in the future." That's substantive info about work location and sponsorship. Should we keep? Probably yes, as it's part of job description. Not boilerplate. So we should include that info somewhere. Where? Could be in a short
after heading maybe under About the role? There's no explicit heading for that. Could create a
after the heading About the Team? Or we could create a section like "Job Details" but not in allowed headings list. Better to embed as a paragraph after the heading About the Team before the list.
We must not include duplicated lines. Need to check for duplicates: The posting repeats some sentences? Might be okay.
We need to output only HTML fragment, no markdown fences.
Let's extract content:
First paragraph: "This position requires office presence of a minimum of 5 days per week and is only located in the location(s) posted. No relocation is offered. AT&T will not hire any applicants for this position who require employer sponsorship now or in the future. Join AT&T and reimagine the communications and technologies that connect the world. The Technology Services organization is responsible for advancing information technology performance and delivering solutions with a focus on maximizing ROI, increasing efficiency and enhancing the experience of end users. Guided by experienced leaders, Corporate Systems seamlessly integrate with advanced Technology and Operations to drive our enterprise forward. Our Systems Reliability and Software Delivery teams are unwavering in their commitment to excellence, ensuring every solution is robust and efficient. When you step into a career with AT&T, you won't just imagine the future, you'll create it."
Then heading: "About The Team" followed by description: "The DAE team designs, develops, and maintains standardized automation for enterprise database infrastructure. The team supports database platforms such as Oracle, PostgreSQL, MySQL, MongoDB, Cassandra, DB2, Informix, and SAP-related database environments across public cloud, private cloud, AWS Outposts, and hybrid platforms. The Team’s Work Includes Developing reusable Terraform modules and GitHub Actions workflows.Provisioning database-ready compute, storage, networking, identity, security, backup, and monitoring components.Creating standardized database deployment patterns and platform guardrails.Supporting cloud migrations, database onboarding, and modernization initiatives.Automating image creation, deployment validation, lifecycle management, and decommissioning.Integrating database infrastructure with enterprise identity, secrets management, certificate management, backup, observability, audit, and compliance services.Troubleshooting infrastructure and automation issues across multiple database technologies and cloud environments.Improving engineering practices through technical reviews, documentation, knowledge sharing, and reusable solutions."
Note there are missing spaces after periods before next sentences; but we keep as is.
Then "What You'll Do" heading and paragraphs.
Then "What You’ll Bring" heading with Required Qualifications list.
We need to convert lists to
- . The "What You'll Do" section contains bullet-like sentences separated by periods? Actually it's a paragraph with sentences separated by line breaks? The text: "The Lead Systems Engineer will provide hands-on technical leadership within the Database Architecture and Engineering team (DAE). The role is responsible for designing, developing, testing, and supporting reusable automation that provisions secure, standardized, and database-ready infrastructure across AWS, AWS Outposts, Azure, and hybrid environments. This is an individual-contributor role with responsibility for coordinating technical work, improving engineering deliverables, resolving complex cross-team issues, and coaching other engineers. The Lead Systems Engineer will work closely with database engineering, cloud platform, architecture, security, migration, backup, monitoring, and operational support teams to deliver resilient and supportable database platform capabilities. Infrastructure as Code and Automation Design, develop, test, and maintain reusable Terraform modules for database-ready infrastructure.Build and support GitHub Actions workflows that automate infrastructure provisioning, configuration, validation, and teardown.Develop automation for EC2 instances, virtual machines, storage, encryption, networking, security groups, IAM roles, identity integration, and supporting database services.Create modules that support multiple database products while allowing product-specific compute, storage, filesystem, networking, and operating-system requirements.Maintain common automation components that can be reused across Oracle, PostgreSQL, MySQL, and other supported database platforms.Improve module reliability through input validation, dependency management, error handling, logging, testing, and rerun-safe deployment behavior.Support migration from legacy pipelines and locally managed scripts to standardized GitHub- and Terraform-based workflows.Participate in code reviews, pull-request validation, release planning, and version management for shared modules and deployment workflows. Cloud and Systems Engineering Engineer database-ready infrastructure across AWS, AWS Outposts, Azure, and hybrid environments.Configure compute, storage, filesystems, networking, encryption, operating-system settings, and supporting agents according to database platform requirements.Apply Linux engineering practices related to system configuration, package management, storage management, performance tuning, service management, and troubleshooting.Support image creation and lifecycle processes, including validation, regional distribution, ownership, versioning, patching, and retirement.Develop and maintain patterns for account, subscription, region, availability zone, subnet, routing, security group, and tagging requirements.Support secure administrative access through enterprise identity services, role-based access controls, session management, and least-privilege design.Integrate infrastructure with certificate, secrets, monitoring, logging, backup, recovery, service-management, and compliance capabilities.Evaluate technical dependencies and identify reusable solutions that reduce platform-specific customization. Database Platform Enablement Translate database product requirements into standardized infrastructure modules and deployment configurations.Work with database subject-matter experts to define processor, memory, disk, filesystem, network, operating-system, backup, monitoring, and high-availability requirements.Support infrastructure patterns for single-node, clustered, replicated, and disaster-recovery configurations where required.Ensure modules produce infrastructure that is ready for database software installation, configuration, validation, and operational handoff.Assist with the development of onboarding patterns for new database technologies and versions.Participate in database migration readiness activities by identifying infrastructure prerequisites, technical constraints, and deployment dependencies.Help define consistent handoff criteria between infrastructure provisioning, database installation, migration execution, and ongoing operational support. Security, Compliance, and Operational Readiness Incorporate security and compliance controls into infrastructure automation from the beginning of the design process.Implement encryption, key management, secrets handling, identity controls, network segmentation, logging, and audit requirements in reusable modules.Work with security and compliance teams to evaluate requirements for regulated and restricted database workloads.Help ensure that infrastructure patterns support least privilege, separation of duties, traceability, standardized lifecycle management, and auditable access.Integrate automated deployments with enterprise backup, monitoring, vulnerability management, logging, and service-management processes.Develop validation checks that confirm infrastructure meets defined technical and operational requirements before handoff.Identify operational gaps and work across teams to establish ownership, escalation paths, support procedures, and remediation approaches.Support vulnerability remediation, patching readiness, platform lifecycle management, and retirement of obsolete components. Troubleshooting and Operational Support Serve as a senior technical resource for complex infrastructure, automation, pipeline, access, networking, storage, and deployment issues.Analyze failed Terraform plans and applies, GitHub workflow failures, cloud service errors, and operating-system configuration problems.Diagnose issues involving IAM, identity federation, OIDC, security groups, routing, DNS, KMS, EBS, SSM, certificates, secrets, and service integrations.Develop durable fixes rather than relying on repeated manual workarounds.Improve troubleshooting information through meaningful logs, validation messages, runbooks, and support documentation.Coordinate resolution of issues that cross database, infrastructure, cloud platform, security, and operations teams.Participate in recurring engineering standups, backlog reviews, technical working sessions, and incident discussions.Track assigned work through completion and clearly communicate status, risks, dependencies, and blockers. Technical Leadership and Continuous Improvement Provide technical leadership within the team without requiring direct people-management responsibility.Coordinate a small team or focused engineering workstream when needed.Help break complex platform objectives into implementable technical stories, tasks, dependencies, and acceptance criteria.Identify opportunities to improve engineering quality, delivery efficiency, reliability, maintainability, and operational resilience.Recommend new techniques and tools when they provide measurable improvements over existing practices.Establish and promote standards for Terraform development, source control, pipeline design, module structure, testing, documentation, and release management.Balance immediate delivery needs with long-term maintainability and platform strategy.Remain current on cloud infrastructure, Infrastructure as Code, database platforms, automation, security, and observability trends.Deliver complex assignments reliably while maintaining high-quality and resilient outputs. Collaboration, Communication, and Coaching Foster collaboration beyond the immediate team by building productive working relationships across engineering and support organizations.Resolve cross-team technical issues involving unclear ownership, competing requirements, integration dependencies, and operational handoffs.Communicate technical designs, risks, constraints, and recommendations clearly to both technical and nontechnical stakeholders.Provide constructive feedback through design reviews, code reviews, working sessions, and implementation discussions.Coach less-experienced engineers on Infrastructure as Code, cloud services, automation, Linux, troubleshooting, and database infrastructure practices.Share technical knowledge through demonstrations, documentation, examples, reusable code, and recorded working sessions.Contribute to a team culture that values transparency, practical problem-solving, engineering discipline, and shared ownership.Maintain clear documentation in shared repositories and collaboration platforms so that processes do not depend on individual knowledge."
That's a massive paragraph with many sentences but no explicit bullet list. We could keep as
paragraphs splitting by double newline? The original had line breaks after each major subsection? Actually the text shows headings like "Infrastructure as Code and Automation", "Cloud and Systems Engineering", etc. Those are likely subsection headings but not marked. We could treat each sentence as separate
but that would be many. Better to keep as one
for the whole "What You'll Do" section, preserving all info. That's acceptable.
Similarly "What You'll Bring" includes a list of qualifications each starting with a bold? Actually the text: "Required Qualifications 5+ years experience delivering Infrastructure-as-Code solutions using Terraform and automated deployment pipelines in a production environment.Demonstrated experience providing technical leadership within an engineering team or coordinating a focused technical workstream.Strong hands-on experience developing and maintaining Terraform modules.5+ years experience building or supporting
after heading maybe under About the role? There's no explicit heading for that. Could create a
after the heading About the Team? Or we could create a section like "Job Details" but not in allowed headings list. Better to embed as a paragraph after the heading About the Team before the list. We must not include duplicated lines. Need to check for duplicates: The posting repeats some sentences? Might be okay. We need to output only HTML fragment, no markdown fences. Let's extract content: First paragraph: "This position requires office presence of a minimum of 5 days per week and is only located in the location(s) posted. No relocation is offered. AT&T will not hire any applicants for this position who require employer sponsorship now or in the future. Join AT&T and reimagine the communications and technologies that connect the world. The Technology Services organization is responsible for advancing information technology performance and delivering solutions with a focus on maximizing ROI, increasing efficiency and enhancing the experience of end users. Guided by experienced leaders, Corporate Systems seamlessly integrate with advanced Technology and Operations to drive our enterprise forward. Our Systems Reliability and Software Delivery teams are unwavering in their commitment to excellence, ensuring every solution is robust and efficient. When you step into a career with AT&T, you won't just imagine the future, you'll create it." Then heading: "About The Team" followed by description: "The DAE team designs, develops, and maintains standardized automation for enterprise database infrastructure. The team supports database platforms such as Oracle, PostgreSQL, MySQL, MongoDB, Cassandra, DB2, Informix, and SAP-related database environments across public cloud, private cloud, AWS Outposts, and hybrid platforms. The Team’s Work Includes Developing reusable Terraform modules and GitHub Actions workflows.Provisioning database-ready compute, storage, networking, identity, security, backup, and monitoring components.Creating standardized database deployment patterns and platform guardrails.Supporting cloud migrations, database onboarding, and modernization initiatives.Automating image creation, deployment validation, lifecycle management, and decommissioning.Integrating database infrastructure with enterprise identity, secrets management, certificate management, backup, observability, audit, and compliance services.Troubleshooting infrastructure and automation issues across multiple database technologies and cloud environments.Improving engineering practices through technical reviews, documentation, knowledge sharing, and reusable solutions." Note there are missing spaces after periods before next sentences; but we keep as is. Then "What You'll Do" heading and paragraphs. Then "What You’ll Bring" heading with Required Qualifications list. We need to convert lists to
- . The "What You'll Do" section contains bullet-like sentences separated by periods? Actually it's a paragraph with sentences separated by line breaks? The text: "The Lead Systems Engineer will provide hands-on technical leadership within the Database Architecture and Engineering team (DAE). The role is responsible for designing, developing, testing, and supporting reusable automation that provisions secure, standardized, and database-ready infrastructure across AWS, AWS Outposts, Azure, and hybrid environments. This is an individual-contributor role with responsibility for coordinating technical work, improving engineering deliverables, resolving complex cross-team issues, and coaching other engineers. The Lead Systems Engineer will work closely with database engineering, cloud platform, architecture, security, migration, backup, monitoring, and operational support teams to deliver resilient and supportable database platform capabilities. Infrastructure as Code and Automation Design, develop, test, and maintain reusable Terraform modules for database-ready infrastructure.Build and support GitHub Actions workflows that automate infrastructure provisioning, configuration, validation, and teardown.Develop automation for EC2 instances, virtual machines, storage, encryption, networking, security groups, IAM roles, identity integration, and supporting database services.Create modules that support multiple database products while allowing product-specific compute, storage, filesystem, networking, and operating-system requirements.Maintain common automation components that can be reused across Oracle, PostgreSQL, MySQL, and other supported database platforms.Improve module reliability through input validation, dependency management, error handling, logging, testing, and rerun-safe deployment behavior.Support migration from legacy pipelines and locally managed scripts to standardized GitHub- and Terraform-based workflows.Participate in code reviews, pull-request validation, release planning, and version management for shared modules and deployment workflows. Cloud and Systems Engineering Engineer database-ready infrastructure across AWS, AWS Outposts, Azure, and hybrid environments.Configure compute, storage, filesystems, networking, encryption, operating-system settings, and supporting agents according to database platform requirements.Apply Linux engineering practices related to system configuration, package management, storage management, performance tuning, service management, and troubleshooting.Support image creation and lifecycle processes, including validation, regional distribution, ownership, versioning, patching, and retirement.Develop and maintain patterns for account, subscription, region, availability zone, subnet, routing, security group, and tagging requirements.Support secure administrative access through enterprise identity services, role-based access controls, session management, and least-privilege design.Integrate infrastructure with certificate, secrets, monitoring, logging, backup, recovery, service-management, and compliance capabilities.Evaluate technical dependencies and identify reusable solutions that reduce platform-specific customization. Database Platform Enablement Translate database product requirements into standardized infrastructure modules and deployment configurations.Work with database subject-matter experts to define processor, memory, disk, filesystem, network, operating-system, backup, monitoring, and high-availability requirements.Support infrastructure patterns for single-node, clustered, replicated, and disaster-recovery configurations where required.Ensure modules produce infrastructure that is ready for database software installation, configuration, validation, and operational handoff.Assist with the development of onboarding patterns for new database technologies and versions.Participate in database migration readiness activities by identifying infrastructure prerequisites, technical constraints, and deployment dependencies.Help define consistent handoff criteria between infrastructure provisioning, database installation, migration execution, and ongoing operational support. Security, Compliance, and Operational Readiness Incorporate security and compliance controls into infrastructure automation from the beginning of the design process.Implement encryption, key management, secrets handling, identity controls, network segmentation, logging, and audit requirements in reusable modules.Work with security and compliance teams to evaluate requirements for regulated and restricted database workloads.Help ensure that infrastructure patterns support least privilege, separation of duties, traceability, standardized lifecycle management, and auditable access.Integrate automated deployments with enterprise backup, monitoring, vulnerability management, logging, and service-management processes.Develop validation checks that confirm infrastructure meets defined technical and operational requirements before handoff.Identify operational gaps and work across teams to establish ownership, escalation paths, support procedures, and remediation approaches.Support vulnerability remediation, patching readiness, platform lifecycle management, and retirement of obsolete components. Troubleshooting and Operational Support Serve as a senior technical resource for complex infrastructure, automation, pipeline, access, networking, storage, and deployment issues.Analyze failed Terraform plans and applies, GitHub workflow failures, cloud service errors, and operating-system configuration problems.Diagnose issues involving IAM, identity federation, OIDC, security groups, routing, DNS, KMS, EBS, SSM, certificates, secrets, and service integrations.Develop durable fixes rather than relying on repeated manual workarounds.Improve troubleshooting information through meaningful logs, validation messages, runbooks, and support documentation.Coordinate resolution of issues that cross database, infrastructure, cloud platform, security, and operations teams.Participate in recurring engineering standups, backlog reviews, technical working sessions, and incident discussions.Track assigned work through completion and clearly communicate status, risks, dependencies, and blockers. Technical Leadership and Continuous Improvement Provide technical leadership within the team without requiring direct people-management responsibility.Coordinate a small team or focused engineering workstream when needed.Help break complex platform objectives into implementable technical stories, tasks, dependencies, and acceptance criteria.Identify opportunities to improve engineering quality, delivery efficiency, reliability, maintainability, and operational resilience.Recommend new techniques and tools when they provide measurable improvements over existing practices.Establish and promote standards for Terraform development, source control, pipeline design, module structure, testing, documentation, and release management.Balance immediate delivery needs with long-term maintainability and platform strategy.Remain current on cloud infrastructure, Infrastructure as Code, database platforms, automation, security, and observability trends.Deliver complex assignments reliably while maintaining high-quality and resilient outputs. Collaboration, Communication, and Coaching Foster collaboration beyond the immediate team by building productive working relationships across engineering and support organizations.Resolve cross-team technical issues involving unclear ownership, competing requirements, integration dependencies, and operational handoffs.Communicate technical designs, risks, constraints, and recommendations clearly to both technical and nontechnical stakeholders.Provide constructive feedback through design reviews, code reviews, working sessions, and implementation discussions.Coach less-experienced engineers on Infrastructure as Code, cloud services, automation, Linux, troubleshooting, and database infrastructure practices.Share technical knowledge through demonstrations, documentation, examples, reusable code, and recorded working sessions.Contribute to a team culture that values transparency, practical problem-solving, engineering discipline, and shared ownership.Maintain clear documentation in shared repositories and collaboration platforms so that processes do not depend on individual knowledge."
That's a massive paragraph with many sentences but no explicit bullet list. We could keep as
paragraphs splitting by double newline? The original had line breaks after each major subsection? Actually the text shows headings like "Infrastructure as Code and Automation", "Cloud and Systems Engineering", etc. Those are likely subsection headings but not marked. We could treat each sentence as separate
but that would be many. Better to keep as one
for the whole "What You'll Do" section, preserving all info. That's acceptable. Similarly "What You'll Bring" includes a list of qualifications each starting with a bold? Actually the text: "Required Qualifications 5+ years experience delivering Infrastructure-as-Code solutions using Terraform and automated deployment pipelines in a production environment.Demonstrated experience providing technical leadership within an engineering team or coordinating a focused technical workstream.Strong hands-on experience developing and maintaining Terraform modules.5+ years experience building or supporting