Database Administrator / Data Warehouse Specialist
Technix LLC · Austin, TX · 1 mo ago
Information TechnologyFull-time
We need to produce 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. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info.
We need to parse the posting.
Position: Database Administrator / Data Warehouse Specialist Duration: 10 months with extension Possible Location: Austin, TX Job ID: 529701778 Agency: HHSC Work Mode: Hybrid work- Locals only Anticipated start date: 11/02/2026 SPECIAL REQUIREMENTS ... etc.
We need to extract sections.
Let's identify content:
- About the role: maybe description of services? Could be "DESCRIPTION OF SERVICES". That is a long paragraph describing duties. So we can put that under
About the role
withcontaining the description. - Responsibilities: maybe list of duties? The description includes many responsibilities. Could also separate responsibilities list. But we can put them under Responsibilities as
- . However we need to avoid duplication. The instruction: Use
- for any list of duties/requirements/benefits. So we should extract bullet list of duties from description. The description is a paragraph with many sentences; we could split into bullet points each responsibility. But we must preserve all substantive information; we can convert sentences into list items. That seems acceptable.
- Requirements: maybe "SPECIAL REQUIREMENTS" and "OTHER SPECIAL REQUIREMENTS". Those are constraints: location, hybrid, remote days, local only, etc. Also "Required Skills" list. Those are requirements. So we can have a Requirements section with bullet list.
- Qualifications: maybe "Required Skills" and "Preferred Skills"? Actually qualifications could be experience years etc. But we have "Required Skills" and "Preferred Skills". Could treat them as Skills section. Qualifications maybe education? Not present. So we may skip Qualifications if no content.
- Skills: list of required and preferred skills. We'll put under Skills.
- Benefits, Pay, Schedule: Not mentioned. So we should not include those sections.
We must not include headings with filler. So only include sections with real content.
Thus we will output:
About the role
... description ...
Responsibilities
- ... each responsibility ... ...
Requirements
- ... special requirements ... ...
Skills
- ... required skills ...
- ... preferred skills ... ...
About the role
... (the description paragraph) ...
Responsibilities
- Enters codes to create production database.
- Selects and enters codes of utility program to monitor database performance, such as distribution of records and amount of available memory.
- Directs programmers and analysts to make changes to database management system.
- Reviews and corrects programs.
- Answers user questions.
- Confers with coworkers to determine impact of database changes on other systems and staff cost for making changes to database.
- Modifies database programs to increase processing performance (performance tuning).
- Workers typically specialize in one or more types of database management systems.
- Provides assistance in the planning, development, maintenance, and monitoring of integrated database systems, ensuring that conceptual and design phases of new applications are consistent with structural parameters within the database environment.
- Evaluates users' requests for new data elements and systems, incorporates them into the existing shared data environment, and provides technical assistance.
- Coordinates the use of data to ensure data integrity and control redundancy, loads databases, and reorganizes as needed.
- Performs data modeling and prototyping.
- Performs logical and physical data modeling, designs relational database models, and creates physical data models from logical data models.
- Performs security recovery procedures.
- Determines and implements database search strategies and storage requirements.
- Maintains data dictionary ensuring uniformity of definitions and sets standards for use of data dictionary.
- Monitors database performance and recommends efficiency improvements.
- Creates test database environment for applications section, including creation of necessary libraries and procedures.
- Executes procedures necessary to save, retrieve, and recover databases from hardware and software failures within
- for any list of duties/requirements/benefits. So we should extract bullet list of duties from description. The description is a paragraph with many sentences; we could split into bullet points each responsibility. But we must preserve all substantive information; we can convert sentences into list items. That seems acceptable.
- Requirements: maybe "SPECIAL REQUIREMENTS" and "OTHER SPECIAL REQUIREMENTS". Those are constraints: location, hybrid, remote days, local only, etc. Also "Required Skills" list. Those are requirements. So we can have a Requirements section with bullet list.
- Qualifications: maybe "Required Skills" and "Preferred Skills"? Actually qualifications could be experience years etc. But we have "Required Skills" and "Preferred Skills". Could treat them as Skills section. Qualifications maybe education? Not present. So we may skip Qualifications if no content.
- Skills: list of required and preferred skills. We'll put under Skills.
- Benefits, Pay, Schedule: Not mentioned. So we should not include those sections.
We must not include headings with filler. So only include sections with real content.
Thus we will output: