Database Engineer

We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. No job title heading. No Job ID etc. Remove boilerplate. Include sections only if real specific content. Must preserve all substantive info. We need to parse job description. Key parts: - Intro paragraph about AgCountry etc. That's prose. - Job Summary: "Incumbent must work three days each week in the Omaha, NE office". Also "We are seeking a Database Engineer to join our team." Then description of responsibilities. We need sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we only include sections with real content. We have content about responsibilities (Essential Duties & Responsibilities). That's a list of duties. We have Minimum Qualifications, Preferred Qualifications, Education Requirements, Years of Experience, Certification and Technical Requirements. Those can be grouped under "Requirements" or "Qualifications". We need to decide. We have Benefits described under "Why Us:" with bullet list. We have Schedule? The job summary says incumbent must work three days each week in the Omaha, NE office. That's schedule info (hybrid). So we can include a Schedule section. Pay: Not mentioned. So we should not include Pay section. We need to avoid filler like "commensurate with experience". Not present. We need to preserve all substantive info. We need to format using

  for each section heading. We need to use

  • for any list of duties/requirements/benefits. We need to use

    for prose. We need to output only HTML fragment, no /, no markdown fences. Let's craft sections: - About the role (maybe summarizing job summary). Could include the introductory paragraph and job summary. But we need to avoid duplication. Let's think. We could have:

    About the role

    AgCountry Farm Credit Services (AgCountry), Farm Credit Services of America (FCSAmerica) and Frontier Farm Credit are financial cooperatives that operate under shared management across eight states. While each association is owned by its local farmers and ranchers, they collaborate by pooling resources, expertise, and talent to provide affordable credit, crop insurance, and financial services. Our associations are united by a common mission and commitment to serving rural America and supporting each other, which drives the success of the farmers, ranchers, and agribusiness we serve. We take pride in being a great place to work, and this enthusiasm is reflected in the relationships our team members foster with one another and with our customers.

    Job Summary: Incumbent must work three days each week in the Omaha, NE office. We are seeking a Database Engineer to join our team. This role will be responsible for the installation, configuration, administration, monitoring, security, maintenance, and support of enterprise database systems including tool sets. This includes database performance tuning, capacity planning, backup and recovery, security and access controls, patch management, test data management, data refreshes, and operational support. The role also participates in a 24x7 on-call rotation, supports testing and deployments, and assists with SQL reporting and related database processes. Our Database Engineers are responsible for the database infrastructure of both SQL, Oracle, and cloud databases. We also focus on the performance of both the database and application code. Monitoring and process automation/improvement are key factors in the success of our team, FCSAmerica and ultimately our customers.

    But we need to avoid using maybe not needed; we can just keep as prose. We could incorporate the job summary into About the role. Then Responsibilities: list of duties from Essential Duties & Responsibilities. We need to split into two subcategories: Customer Service and Operational Response, Database Administration and Engineering. Could keep as one list or separate subheadings? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings but we should stick to those headings. Could embed subheadings as

    maybe but better to keep as

    • with description. We'll create a Responsibilities section with
      • items covering each bullet. We need to preserve all details. Let's extract duties: Customer Service and Operational Response: - Deliver timely, accurate, and high-quality support. - Respond to database-related incidents, service requests, and operational issues in a professional and efficient manner. - Participate in a 24x7 on-call rotation to provide after-hours support for critical database systems. - Diagnose database issues, troubleshoot root causes, and implement effective resolutions. - Document incidents, resolutions, procedures, and technical knowledge in the appropriate tracking and support systems. - Collaborate with technical teams and business partners to ensure service expectations are met or exceeded. Database Administration and Engineering: - Administer and maintain database environments to ensure confidentiality, integrity, availability, and performance. - Install, configure, patch, upgrade, and maintain database software and related components, and tools. - Perform routine database administration activities including provisioning, configuration tuning, backup validation, recovery support, replication support, and system optimization. - Develop, maintain, and enhance automation for routine database administration tasks, including monitoring, maintenance, deployments, backups, data refresh support, and operational reporting - Manage database recoverability through the implementation and support of backup, restore, and disaster recovery processes. - Monitor database performance and resolve issues related to capacity, availability, security, and operational efficiency. - Analyze database growth and usage trends to support capacity planning and long-term data storage strategies. - Establish, maintain, and enforce standards, policies, and procedures for database administration, security, maintenance, and utilization. - Manage database access and permissions in accordance with data security standards and business requirements. - Support database migrations, environment refreshes, and operational improvements. - Support database-related utilities and processes that assist with replication, validation, and operational documentation. We'll put each as
      • . Now Requirements/Qualifications: We have Minimum Qualifications, Preferred Qualifications, Education Requirements, Years of Experience, Certification and Technical Requirements. We could combine into a Requirements section with sublists? But we must use
        • for any list. Could have multiple
          inside section. We'll create a Requirements section with

          Requirements

          and then maybe separate

          headings inside? But we cannot use other headings besides

          . Could use

          with bold text? Not prohibited. We'll just list items. Let's extract: Minimum Qualifications: - High proficiency with database analysis, development, administration, stored procedures, (PL/SQL & T-SQL), SQL query analysis and optimization, SQL Server Integrations Services (SSIS), Data Transformation Services (DTS), Materialized Views, partitioning, multi-tenant, Active Data Guard (ADG), and triggers. - Proficient with Microsoft and Oracle database tools and technologies - Experience with cloud database management on Azure or AWS - Demonstrated ability to effectively architect complex databases to meet the needs of the rapidly changing business environment. - Proficient Microsoft SQL and Oracle Server, Microsoft Visual Studio, Oracle SQL Developer, Oracle Data Integrator (ODI), and third-party database optimization and monitoring tools. - 4-6 years of database management and development experience Preferred Qualifications: - Microsoft MCDBA, MCITP, or MCSE (Data Platform) certification - Additionally, Oracle Database Administrator Certified Associate, Master, or Professional is a plus. Education Requirements: - Bachelor’s or Graduate degree in Computer Science or MIS preferred. - Master's degree or other advanced degree preferred Years of Experience: - 4 + years of experience in Database management and development, experience with data warehouse, architecture and decision support tools in a Microsoft SQL and Oracle Server environment. - Cloud database management. Certification and Technical Requirements: - Microsoft Certified Azure Database Administrator Associate certification preferred. - Oracle Database Administrator certification (Associate, Professional, or Master) is a plus. - Demonstrated expertise in database analysis, development, and administration, including T-SQL, PL/SQL, SQL query analysis and optimization, SQL Server Integration Services (SSIS), Always On Availability Groups, and Active Data Guard (ADG). - Strong understanding of industry standards, best practices, and methodologies for Microsoft and Oracle database development and administration. - Proficiency with Microsoft and/or Oracle database tools, platforms, and technologies. - Hands-on experience with SolarWinds SentryOne & DPA and Redgate database tools preferred. - Experience scripting and automation using PowerShell and Python preferred. - Proficient with current and recent versions of Microsoft SQL Server or Oracle Database, Microsoft Visual Studio, and/or Oracle SQL Developer. - Experience with the Snowflake cloud data platform and Qlik Replicate is a plus. - Strong working knowledge of current and recent Microsoft operating systems and Microsoft Office products. We'll put these as list items. Now Benefits: from "Why Us:" section. - Health Benefits: Comprehensive medical, dental, and vision insurance - Retirement Plans: 401(k) - Paid Time Off: Vacation, sick leave, paid holidays, and parental leave - Additional Benefits: Life and disability insurance, Employee Assistance Program (EAP), wellness programs, tuition assistance, and short-term incentive pay - For a comprehensive overview of our total reward offerings, click here. (We may drop the link as boilerplate? It's not boilerplate but it's a link; we could keep as prose but it's not a list item. Might be okay as a

          .) We'll create Benefits section with

          • for each benefit. Schedule: from Job Summary: "Incumbent must work three days each week in the Omaha, NE office". That's schedule info. We'll create Schedule section with

            stating that. Now we need to ensure we don't repeat job title as heading. We'll not. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement; we should drop that. Also "About Us:" section includes details about offices etc. That's substantive? It describes the company. Could be considered "About the role" or maybe we could include as part of About the role. It's not duplicated. We'll keep it in About the role maybe as a separate paragraph. We have "About Us:" after Benefits. That's substantive: description of offices, employee count, etc. We'll include that in About the role section as prose. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now produce HTML. Structure:

            About the role

            ... intro paragraph ...

            ... job summary ...

            ... About Us paragraph ...

            Responsibilities

            • ...
            ...

            Requirements

            • ...
            ...

            Benefits

            • ...
            ...

            Schedule

            Incumbent must work three days each week in the Omaha, NE office.

            We need to ensure we didn't miss any substantive info like "We also focus on the performance of both the database and application code." That's in job summary; we included. Also "Monitoring and process automation/improvement are key factors in the success of our team, FCSAmerica and ultimately our customers." included. Now we need to check for duplication: The "About Us" paragraph may duplicate some of intro but it's okay. Let's craft the About the role paragraph: First paragraph: "AgCountry Farm Credit Services (AgCountry), Farm Credit Services of America (FCSAmerica) and Frontier Farm Credit are financial cooperatives that operate under shared management across eight states. While each association is owned by its local farmers and ranchers, they collaborate by pooling resources, expertise, and talent to provide affordable credit, crop insurance,