Senior Database Administrator - Data Warehousing | ETL | Oracle or Teradata | SQL | Business Objects

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Only those lawfully authorized..." etc. Also remove "Please note that all Position start dates..." etc. Remove benefits link placeholder? Benefits: "For information and details on employment benefits offered with this position, please visit here." That's not specific content; it's a placeholder. So we should not create Benefits section unless posting actually states them. It says "Benefits For information and details on employment benefits offered with this position, please visit here." That's not substantive. So we should not include Benefits section. Pay: we have Min Hourly Rate $80.00 Max $85.00. That's specific. So include Pay section. Schedule: Work Model: Hybrid, 2 days remote, 3 days onsite, Shift: 8:00 AM to 5:00 PM. That's schedule info. So include Schedule section. About the role: maybe we can include a short paragraph summarizing role? The posting includes Job Description etc. We could put About the role as a prose paragraph summarizing the role (maybe from first lines). But we must not invent or summarize away detail. We can include a paragraph that is directly from posting: maybe the "Job Description" block? Actually there is a "Job Description Required Qualifications/Skills/Experience:" then a list. Could treat that as Requirements/Qualifications. The "Responsibilities" section is present with a block of responsibilities. So we can have Responsibilities section with

• . Also Requirements/Qualifications/Skills sections: we need to decide how to split. The posting has "Must Have Skills/Attributes:" list, then "Experience Desired:" list, then "Required Qualifications/Skills/Experience:" list (many repeated). Also "Preferred Qualifications". We need to preserve all substantive info, not invent. We can combine into Requirements (must have) and Qualifications (preferred) maybe. But we must not create thin sections with filler. We have substantive content for Requirements (must have skills), Qualifications (preferred), Skills (maybe we can separate skills list). However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But they ask to use headings for e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. Likely we will have About the role (maybe a brief paragraph from the job description?), Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. We need to avoid duplication. Let's extract substantive content: Job Title: Senior Database Administrator - Data Warehousing | ETL | Oracle or Teradata | SQL | Business Objects (but we don't repeat as heading). Location: Austin, TX, USA, 78751 Work Model: Hybrid Work Model Details: 2 days remote, 3 days onsite Shift: 8:00 AM to 5:00 PM Employment Type: Temporary FT/PT: Full-Time Estimated Duration (In months): 11 Min Hourly Rate($): 80.00 Max Hourly Rate($): 85.00 Must Have Skills/Attributes: Analytical Skills, Database, DataStage, ETL, Warehouse, WebSphere Experience Desired: Strong knowledge of database management systems, data warehouse management and decision support tool (5+ yrs); Extensive experience in the development, implementation and maintenance of data warehouses and data (5+ yrs); Experience in business objects and in building the data dictionary (5+ yrs); Strong familiarity with analysis, planning and management reporting functions (5+ yrs); Oracle Database and PowerBI report creation experience (5+ yrs) **C2C is not available** Job Description Required Qualifications/Skills/Experience: (list many items each with "5 Year Required"). Let's list them: - Strong knowledge of database management systems, as well as data warehouse management and decision support tools (actually "data warehouse management and decision support tools") - Extensive experience in the development, implementation and maintenance of data warehouses and data marts is desired - Experience in business objects and in building the data dictionary - Ability to use data base access tools for application delivery - Strong familiarity with analysis, planning and management reporting functions - Well-developed oral and written communications skills - Strong teamwork and interpersonal skills - Extremely high level of analytical ability where problems are very unusual and extremely difficult - Understanding of benchmarking processes and techniques - Very high level of interpersonal skills to work effectively with others, motivate employees, and elicit work output - Data Warehousing data population and data modeling techniques for target structures such as Star Schemas, Snowflake Schemas, and highly normalized data models - GUI based ETL tools such as Informatica, IBM WebSphere DataStage, or similar tools. - Implementation experience with enterprise class databases e.g. Teradata, Oracle, SQL Server, etc. or similar technologies. - Implementation experience with analytical and reporting tools e.g. Business Objects, Cognos, Hyperion, MicroStrategy or similar tools. - Experience with data warehouse implementation process, from business requirements through logical modeling, physical database design, data sourcing and data transformation, data loading, Structured Query Language (SQL), end-user tools, database and SQL pe (cut off) - Implementation experience with analytical and reporting tools e.g. Business Objects, Cognos, Hyperion, MicroStrategy or similar tools. (duplicate) - Excellent analytical; problem-solving; team playing; and oral and written communication skills. - Proven ability to work successfully with technical and non-technical groups and manage multiple responsibilities. Preferred Qualifications: - 5 Year Preferred Oracle Database experience - 5 Year Preferred PowerBI report creation Responsibilities: a long paragraph with many sentences. We need to turn into list items? The instruction: Use
  • for any list of duties/requirements/benefits. So responsibilities should be a list. We'll split each sentence into
  • . We must preserve all substantive info; not invent. We also need About the role: maybe we can take the first few sentences before responsibilities? The posting includes "Job Description Required Qualifications/Skills/Experience:" then list. There's no separate "About the role" paragraph. Could we create About the role from the job title and location? But we shouldn't invent. Perhaps we can omit About the role section if no specific content. The instruction: "include a section ONLY when the posting has real, specific content for it". So if there is no explicit "About the role" paragraph, we should not include that heading. However they gave examples of headings but we only include if content exists. So we may omit About the role. Thus sections: Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. But we also have "Must Have Skills/Attributes" and "Experience Desired". Those could go under Skills or Requirements. We need to decide mapping. We have Requirements (must have) and Qualifications (preferred). Skills could be a separate section for technical skills like Analytical Skills, Database, DataStage, ETL, Warehouse, WebSphere. But those are also must have. Might be redundant. Better to follow: Requirements = Must Have Skills/Attributes + Experience Desired (the 5+ years). Qualifications = Preferred Qualifications. Skills = maybe the list of technical skills from Must Have Skills/Attributes? But that duplicates. Given instruction to prefer few substantive sections, we could combine Must Have Skills/Attributes and Experience Desired into Requirements, and Preferred Qualifications into Qualifications, and maybe Skills not needed. But we need to include Skills section if there is specific content for skills beyond those already captured. The Must Have Skills/Attributes list is skills. So we could have Skills section for that list, and Requirements for the experience/qualifications (the 5 year required list). Qualifications for preferred. That seems reasonable. Thus: Skills:
    • Analytical Skills
    • Database
    • DataStage
    • ETL
    • Warehouse
    • WebSphere
    Requirements: list of the 5 Year Required items (the long list). We'll need to deduplicate duplicates (there are duplicates like Implementation experience with analytical and reporting tools appears twice). We should preserve all substantive info but not repeat duplicate lines? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicate lines are still substantive info but repeating them may be unnecessary. However they said remove duplicated lines. So we should remove duplicated lines. So we need to deduplicate. Let's extract unique items from the Required list: 1. Strong knowledge of database management systems, as well as data warehouse management and decision support tools 2. Extensive experience in the development, implementation and maintenance of data warehouses and data marts is desired 3. Experience in business objects and in building the data dictionary 4. Ability to use data base access tools for application delivery 5. Strong familiarity with analysis, planning and management reporting functions 6. Well-developed oral and written communications skills 7. Strong teamwork and interpersonal skills 8. Extremely high level of analytical ability where problems are very unusual and extremely difficult 9. Understanding of benchmarking processes and techniques 10. Very high level of interpersonal skills to work effectively with others, motivate employees, and elicit work output 11. Data Warehousing data population and data modeling techniques for target structures such as Star Schemas, Snowflake Schemas, and highly normalized data models 12. GUI based ETL tools such as Informatica, IBM WebSphere DataStage, or similar tools. 13. Implementation experience with enterprise class databases e.g. Teradata, Oracle, SQL Server, etc. or similar technologies. 14. Implementation experience with analytical and reporting tools e.g. Business Objects, Cognos, Hyperion, MicroStrategy or similar tools. 15. Experience with data warehouse implementation process, from business requirements through logical modeling, physical database design, data sourcing and data transformation, data loading, Structured Query Language (SQL), end-user tools, database and SQL pe (looks truncated; but we keep as is) 16. Excellent analytical; problem-solving; team playing; and oral and written communication skills. 17. Proven ability to work successfully with technical and non-technical groups and manage multiple responsibilities. Note item 14 duplicate of earlier? Actually we have item 14 as same as earlier "Implementation experience with analytical and reporting tools e.g. Business Objects, Cognos, Hyperion, MicroStrategy or similar tools." It appears twice in the list; we keep one. Now Qualifications (Preferred): - Oracle Database experience - PowerBI report creation Now Responsibilities: we need to split the paragraph into list items. Let's extract sentences from the responsibilities block: "Enters codes to create production data base" "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 data base management system" "Reviews and corrects programs" "Answers user questions" "Confers with coworkers to determine impact of data base changes on other systems and staff cost for making changes to data base" "Modifies data base programs to increase processing performance, referred to as performance tuning" "Workers typically specialize in one or more types of data base management systems" "Providing assistance in the planning, development, maintenance, and monitoring of integrated database systems, and ensuring that the conceptual and design phases of new applications are consistent with the 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