Database Administrator
for each heading only if there is real content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Must not create sections with placeholder like "commensurate with experience". Pay and Benefits: we have pay range $10.00 - $12.00/hr and benefits list. So we need Pay and Benefits sections? The instruction: "Prefer a few substantive sections over many thin ones." Also "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Pay And Benefits and includes pay range and benefits list. So we could combine Pay and Benefits into one section? But they said use headings for each: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They want separate headings if content exists. We have Pay content (pay range) and Benefits content (list). So we should have both Pay
and Benefits
. Schedule: not mentioned; no schedule info. So omit Schedule section.
We need About the role: likely the introductory paragraph after title: "TEKsystems DB2 DBA Opening !!! Administers, secures, and tunes the company's IBM Db2 for z/OS databases supporting core policy, claims, and financial processing. Owns physical database design review, performance management, backup and recovery, and disaster recovery readiness for the Db2 subsystems. Provides secondary administration for Microsoft SQL Server and Azure SQL Managed Instance and supports the data pipelines that move mainframe data to the enterprise data warehouse. Treats documentation, cross-training, and knowledge transfer as core deliverables of the role." That's about the role. We'll put that in
. Responsibilities: The "Essential Functions" list with bullet points. We'll extract each bullet as
- . We'll preserve details.
Requirements: Not explicitly listed; maybe "Additional Skills & Qualifications" and "Skills" etc. But we have "Skills" section later. Requirements could be things like "IBM Certified Database Administrator, Db2 for z/OS", "Microsoft SQL Server administration; Azure SQL Managed Instance", etc. Also "Experience Level Entry Level". We'll treat those as Requirements.
Qualifications: Could be similar to Requirements? Might be overlapping. But we need to decide. The posting has "Skills" list: "Database administrator, Db2, Sql, z/OS, database design, performance management, backups, table creation, stored procedures, Azure, Cloud, AI, Cobol". Also "Top Skills Details" and "Additional Skills & Qualifications". We'll treat Skills as a section with list.
Qualifications maybe include certifications and experience: "IBM Certified Database Administrator, Db2 for z/OS", "Microsoft SQL Server administration; Azure SQL Managed Instance", "COBOL, REXX, Python", "Advanced Db2: Data sharing and Parallel Sysplex; Db2 Connect and DDF tuning; Db2 stored procedures", "Enterprise job scheduling (e.g., Stonebranch); Db2 performance monitoring tools", "ITIL Foundation; Agile delivery experience". Also "Experience Level Entry Level". We'll put those in Qualifications.
We need to ensure we don't repeat content. We'll parse.
Let's extract sections:
About the role: first paragraph(s) before "Essential Functions". That's:
"TEKsystems DB2 DBA Opening !!! Administers, secures, and tunes the company's IBM Db2 for z/OS databases supporting core policy, claims, and financial processing. Owns physical database design review, performance management, backup and recovery, and disaster recovery readiness for the Db2 subsystems. Provides secondary administration for Microsoft SQL Server and Azure SQL Managed Instance and supports the data pipelines that move mainframe data to the enterprise data warehouse. Treats documentation, cross-training, and knowledge transfer as core deliverables of the role."
We'll keep that as
- with its subpoints as nested
- .
Requirements: Might be "Experience Level Entry Level" and maybe "Job Type & Location This is a Contract to Hire position based out of Omaha, NE." Also "Workplace Type This is a fully onsite position in Omaha,NE." Also "Application Deadline This position is anticipated to close on Oct 2, 2026." But those are metadata; we should not include Job ID etc but location and job type maybe considered requirements? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
- Database design and change management
- Reviews and approves physical database designs (tablespaces, partitioning, indexing, referential integrity, compression) for new and changed applications.
- Implements DDL and configuration changes through the ITIL change management process; maintains DDL, object inventory, and standards under version control.
- Manages subsystem parameters (ZPARM), buffer pool configuration, and storage allocation.
... etc for each main heading.
- IBM Certified Database Administrator, Db2 for z/OS
- Microsoft SQL Server administration; Azure SQL Managed Instance
- COBOL, REXX, Python
- Advanced Db2: Data sharing and Parallel Sysplex; Db2 Connect and DDF tuning; Db2 stored procedures
- Enterprise job scheduling (e.g., Stonebranch); Db2 performance monitoring tools
- ITIL Foundation; Agile delivery experience
- Database administrator
- Db2
- Sql
- z/OS
- database design
- performance management
- backups
- table creation
- stored procedures
- Azure
- Cloud
- AI
- Cobol
- Medical, dental & vision
- Critical Illness, Accident, and Hospital
- 401(k) Retirement Plan
- Pre-tax and Roth post-tax contributions available
- Life Insurance (Voluntary Life & AD&D for the employee and dependents)
- Short and long-term disability
- Health Spending Account (HSA)
- Transportation benefits
- Employee Assistance Program
- Time Off/Leave (PTO, Vacation or Sick Leave)
or drop it." So we can include location and job type in a short
maybe under About the role? But we already have About the role. Could add a
after About the role for metadata: "Contract to Hire position based out of Omaha, NE. Fully onsite. Anticipated to close Oct 2, 2026." That seems okay. But Requirements section: maybe we should include "Experience Level Entry Level" and any explicit requirements like certifications? However those are more qualifications. We'll treat Requirements as maybe empty? Better to omit if no specific requirements beyond what's in Qualifications. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. If we don't have clear requirements separate from qualifications, we could omit Requirements. However we have "Experience Level Entry Level" which is a requirement. Also "Job Type & Location" maybe not a requirement but metadata. We'll include Requirements with entry level and maybe location? But location is not a requirement per se. Let's include Requirements: "Entry level position." We'll put as
. Qualifications: We'll list certifications, skills, experience. Skills: We'll list the skills list. Benefits: list of benefits. Pay: pay range. We must not include boilerplate like EEO, legal, etc. Also remove duplicated lines like "About TEKsystems" repeated. We'll ignore those. Now craft HTML. Structure:
About the role
...
Responsibilities
Requirements
Entry level position.
Qualifications
Skills
Benefits
Pay
The pay range for this position is $10.00 - $12.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.
We should also maybe include a short metadata paragraph after About the role? But we already have About the role. Could - Database design and change management
. Responsibilities: Under "Essential Functions" we have headings: - Database design and change management - Reviews and approves physical database designs (tablespaces, partitioning, indexing, referential integrity, compression) for new and changed applications. - Implements DDL and configuration changes through the ITIL change management process; maintains DDL, object inventory, and standards under version control. - Manages subsystem parameters (ZPARM), buffer pool configuration, and storage allocation. - Performance management - Monitors subsystem, thread, and application performance; establishes and tracks baselines. - Analyzes access paths using EXPLAIN and related tooling; identifies and remediates inefficient SQL in partnership with application and data engineering teams. - Schedules and tunes Db2 utilities (REORG, RUNSTATS, COPY, MODIFY, RECOVER) and maintains the utility calendar. - Backup, recovery, and availability - Owns the image copy strategy, active and archive log management, and point-in-time recovery procedures. - Executes and documents recovery tests on a defined cadence (HR/manager: state cadence, e.g., annually). - Participates in disaster recovery exercises and maintains the Db2 recovery runbooks. - Security and confidentiality - Administers Db2 authorization (GRANT/REVOKE, roles, RACF integration) under least-privilege principles. - Supports internal and external audit and regulatory data requests. - Handles confidential and regulated policyholder and financial data in accordance with company information security policies. - Integration and data movement - Supports the nightly Db2-to-SQL Server extract pipelines (unload utilities, SFTP, enterprise scheduler) in partnership with EDM Data Engineering. - Administers DDF/DRDA connectivity and distributed access for downstream consumers. - Advises on Db2 data structures consumed by warehouse, finance, and analytics teams. - Platform currency - Plans and executes Db2 version and function-level upgrades and PTF maintenance with Systems Programming. - Evaluates and recommends Db2 features and tooling that improve performance, availability, or operational efficiency. - Documentation, knowledge transfer, and mentoring - Maintains runbooks, standards, and architecture documentation for all administered subsystems. - Cross-trains at least one designated backup administrator on every critical procedure. - Mentors mainframe developers and data engineers on Db2 design and SQL efficiency. - Secondary platform support - Provides backup administration for Microsoft SQL Server and Azure SQL Managed Instance as assigned by the DBA team lead. - Operations - Participates in the DBA on-call rotation and scheduled off-hours maintenance windows. - Follows ITIL incident, problem, and change management practices. We'll turn each main heading into a