Senior Database Migration Engineer (Secret Clearance)

We need to output HTML fragment with sections: About the role? The description includes key responsibilities, required qualifications, education, preferred qualifications, work location, salary description. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly. We must not repeat job title. No Job ID. Remove boilerplate. We need to preserve all substantive info. We need sections only when posting has real specific content. We have responsibilities (Key Responsibilities). We have required qualifications (Required Qualifications). We have education (Education / Workforce Qualification). We have preferred qualifications (Preferred Qualifications). We have work location (Hybrid...). We have salary description ($130k - $145k). There's no explicit Benefits or Schedule beyond work location maybe schedule not given. No benefits listed. So we should not create Benefits or Schedule sections unless content present. Pay section we have salary description, so we can include Pay. Schedule? Not given, so omit. We need to decide headings: About the role maybe a brief summary? The description starts with "Description Key Responsibilities". Could treat that as About the role? But we have a Responsibilities section already. Could put About the role as a short paragraph summarizing role (maybe from first sentence). But we must not invent content. We could use the first sentence as About the role: "Migration Assessment, Planning & Execution Lead end-to-end database migration activities..." That's actually part of responsibilities. Might be better to treat that as Responsibilities. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We have responsibilities content, required qualifications content, education content, preferred qualifications content, work location (maybe under About the role or Schedule? Not exactly). Pay content. We could map: - About the role: maybe a brief overview from first sentence? But that is part of responsibilities. However we could still include About the role as a short paragraph summarizing the role: "Lead end-to-end database migration activities including discovery, assessment, planning, schema conversion, data movement, validation, cutover, rollback planning, and post-migration stabilization." That's from responsibilities. It's okay to reuse content? The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we put that sentence in About the role, we still preserve it, but we also have Responsibilities section with more detail. That would duplicate content. Duplication might be okay? But they said remove duplicated lines. So we should avoid duplicating same content. Better to not have About the role if we already have Responsibilities covering it. But we need to follow instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It's examples, not mandatory to include all. So we can omit About the role if no distinct content. Thus sections: Responsibilities, Requirements (maybe Required Qualifications), Qualifications (maybe Education/Workforce Qualification?), Skills (maybe Preferred Qualifications?), Pay. But we need to map content to headings appropriately. Let's define: - Responsibilities: the Key Responsibilities block. - Requirements: Required Qualifications block (experience, etc.) - Qualifications: Education / Workforce Qualification block (degree or certifications) - Skills: Preferred Qualifications block (preferred experience) - Pay: Salary Description. We should not include Benefits or Schedule. We need to output only HTML fragment, no markdown fences. We'll wrap each section in

heading then content: for lists use

• . For prose use

  . We need to preserve all substantive info: include all bullet points from responsibilities? The responsibilities block is prose sentences, not bullet list. We can keep as

  paragraphs. Similarly required qualifications is a list of bullet-like sentences but not formatted as list. We could convert each sentence to

• in a
  . That would be okay as it's a list of requirements. The instruction: Use
  • for any list of duties/requirements/benefits. So we should convert those to list. Similarly education block: could be list. Preferred qualifications: list. Pay: just a

    with salary. Let's extract responsibilities sentences: "Migration Assessment, Planning & Execution Lead end-to-end database migration activities including discovery, assessment, planning, schema conversion, data movement, validation, cutover, rollback planning, and post-migration stabilization. Assess legacy database platforms, schemas, data volumes, stored procedures, functions, triggers, indexes, interfaces, application dependencies, security controls, and performance requirements. Develop migration strategies, technical plans, schedules, risk assessments, source-to-target mappings, validation criteria, cutover procedures, rollback procedures, and operational runbooks. Lead migration of legacy relational databases to approved AWS managed database platforms, including Amazon Aurora PostgreSQL or Aurora MySQL where implemented. Use AWS Database Migration Service, AWS Schema Conversion Tool, native database utilities, and custom scripts, or comparable approved tools, to support full-load, incremental, change-data-capture, and low-downtime migration approaches. Database Conversion, Compatibility & Performance Convert and remediate database schemas, data types, stored procedures, functions, triggers, sequences, indexes, queries, and proprietary database features for target-platform compatibility. Analyze and remediate application, ETL, BI, API, and interface dependencies affected by database-platform changes, coordinating required code and query changes with the applicable development teams. Develop and optimize SQL queries, views, functions, stored procedures, indexes, and other database objects supporting application and reporting requirements. Analyze execution plans, workloads, locks, connections, database metrics, and resource utilization to resolve performance and scalability issues. Define database-layer requirements for availability, resiliency, replication, backup, recovery, failover, and performance within the approved IGC cloud architecture. Validation, Automation & Secure Delivery Develop and execute migration-validation and reconciliation procedures to verify record counts, data relationships, business rules, transformations, calculations, referential integrity, completeness, accuracy, and functional equivalence between source and target platforms. Identify data-quality issues and coordinate cleansing, correction, exception handling, and remediation activities with the appropriate data owners and technical teams. Develop database and migration automation using SQL, Python, Bash, PowerShell, Liquibase, Flyway, or comparable technologies. Integrate database changes, migration scripts, validation routines, and deployment controls into established GitLab CI/CD and configuration-management processes. Implement database-specific security controls including least privilege, encryption, secrets management, logging, auditing, secure configuration, vulnerability remediation, and applicable STIG/RMF evidence. Documentation & Technical Leadership Prepare and maintain database architecture diagrams, data models, data dictionaries, source-to-target mappings, configuration documentation, migration reports, cutover documentation, and operational procedures. Provide technical leadership and mentoring to database administrators, developers, cloud engineers, and migration team members. Collaborate with application developers, ETL/data engineers, BI developers, cloud/DevSecOps engineers, cybersecurity personnel, testers, functional analysts, operations staff, and Government stakeholders." We can split into list items each sentence (or each bullet heading). We'll create

    • for each distinct responsibility sentence. Now Required Qualifications block: "Eight (8+) or more years of experience in database engineering, database administration, database development, data architecture, or database migration. Demonstrated experience leading complex enterprise database migrations from assessment through production cutover and stabilization. Hands-on experience with Amazon Aurora PostgreSQL, Aurora MySQL, Amazon RDS, or comparable managed relational database services. Experience migrating Oracle, PostgreSQL, MySQL, SQL Server, or comparable enterprise relational databases to cloud-managed database platforms. Experience with AWS Database Migration Service, AWS Schema Conversion Tool, native database utilities, or comparable migration technologies. Advanced SQL and database-development skills including schemas, stored procedures, functions, triggers, views, indexing, and query optimization. Experience converting schemas and remediating incompatible data types, queries, procedural code, and application dependencies. Experience developing migration validation, reconciliation, and data-quality controls. Experience with database performance tuning, backup, recovery, replication, high availability, and production stabilization. Experience scripting database and migration activities using SQL, Python, Bash, PowerShell, or a comparable language. Experience using Git and automated database deployment or CI/CD processes. Knowledge of database security, access control, encryption, auditing, secure configuration, and vulnerability remediation. Strong technical leadership, troubleshooting, documentation, and stakeholder-communication skills. Active Secret security clearance or the ability to obtain and maintain one, as required by assigned duties and contract requirements." We'll make each as
    • . Education / Workforce Qualification: "A bachelor’s degree in Computer Science, Cybersecurity, Data Science, Software Engineering, Information Technology, Information Systems, or a related software-engineering discipline; or One of the following current certifications: Certified Cloud Security Professional (CCSP), CyberSec First Responder (CFR), Federal IT Security Professional–Manager (FITSP-M), GIAC Security Essentials Certification (GSEC), CompTIA Security+, or Systems Security Certified Practitioner (SSCP)." We can make two
    • items. Preferred Qualifications: "Experience supporting USTRANSCOM, Department of Defense logistics, or another mission-critical federal system. Experience migrating large or highly available databases with minimal downtime using change-data capture, replication, blue-green, or phased migration techniques. Experience with Oracle and PostgreSQL/Aurora modernization; familiarity with Teradata or other large-scale enterprise data-warehouse platforms is beneficial where applicable. Experience supporting analytics or BI platforms, including Apache Superset, using migrated relational data sources. Familiarity with containerized application environments and infrastructure-as-code processes used by cloud/DevSecOps teams. AWS, PostgreSQL, Oracle, Microsoft, Security+, or related database/cloud certifications." Make each
    • . Work Location: "Hybrid. Remote work may be authorized consistent with program requirements. Personnel must be available for required on-site migration planning, testing, cutover, classified-system access, technical reviews, or meetings at Scott AFB, Illinois." We could put this under About the role? Or maybe under Schedule? Not exactly. Could be a separate section like "Work Location" but not in allowed headings. Could incorporate into About the role or Schedule? Since Schedule not given, we could treat Work Location as part of About the role? But we don't have About the role section. Perhaps we can add a

      after Responsibilities before Requirements? But we need to follow headings only for those categories. The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. It might be okay to add a heading like "Work Location" but not in the list. Safer to avoid extra headings. We could incorporate work location into a

      under Responsibilities? Not ideal. Maybe we can put it under "About the role" as a brief summary: include work location there. Since we don't have About the role section, we could create it and put work location plus a brief role summary. But we must not invent content; we can include work location as content. That's fine. Thus we can have About the role section containing a short paragraph summarizing role and work location. But we already have responsibilities detailed; we could still have About the role with a high-level summary (maybe first sentence). That would duplicate some content but not exact same sentences. Might be okay. However they said remove duplicated lines. Duplication of same sentence is not allowed. Summarized version is not duplicate. So we can create About the role with a brief overview: "Lead end-to-end database migration activities including discovery, assessment, planning, schema conversion, data movement, validation, cutover, rollback planning, and post-migration stabilization. Hybrid work arrangement with possible remote work; on-site presence required at Scott AFB, Illinois for planning, testing, cutover, and reviews." That's derived from content but not verbatim duplicate. It's okay. Then Respons