IS Data Warehouse Architect III
CareOregon · Portland, OR · 1 mo ago
Information Technology$127k–$155k/yrFull-time
We need to output HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. Must not include boilerplate like EEO, equal opportunity, etc. Must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove "Current CareOregon Employees: Please use the internal Workday site to submit an application for this job." That's application instruction. Also remove "Please contact your recruiter for more information." Also remove "We are an equal opportunity employer ..." etc.
We need to preserve all substantive information: description, essential responsibilities, required experience, preferred experience, knowledge, skills and abilities, working conditions, benefits description, pay range, bonus target, etc.
We need to decide sections: About the role (maybe a summary paragraph), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule? Schedule not given. So we omit Schedule. Pay: we have Estimated Hiring Range $126,720.00 - $154,880.00 Bonus Target Bonus - SIP Target, 5% Annual. So we can include Pay section with that info. Benefits: we have description of benefits. So Benefits section.
We also have Working Conditions details; could be part of Responsibilities? Might be separate section like Working Conditions. But instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings but suggests those are typical. We could include Working Conditions as a heading if content present, but not in list. Might be okay but better to stick to given headings. However we have substantive info about Working Conditions; we could incorporate into Responsibilities or a separate section like "Working Conditions". The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could combine Working Conditions into Responsibilities or About the role. Probably better to have About the role (summary), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay.
We have Required Experience and/or Education (that's qualifications). Also Preferred Experience in health care or managed care (could be part of Qualifications). Knowledge, Skills And Abilities (that's Skills). So we can have sections: About the role (intro paragraph), Responsibilities, Qualifications, Skills, Benefits, Pay.
We must not repeat job title. Must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content:
Intro: "This position performs data warehouse architecture or enterprise data architecture at a senior level. Essential responsibilities are focused on design and development of data models and ETL specifications, data analysis, system design and architecture, standards and policy administration, and vendor coordination and relations."
That's About the role.
Responsibilities: list under Essential Responsibilities with subheadings: Data Modeling and ETL Specifications, Data Analysis, System Design and Architecture, Standards and Policy Administration, Vendor Coordination and Relations. Each has bullet points.
We need to output
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. implies those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could combine Working Conditions into Responsibilities or About the role. Probably better to have About the role (summary), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay.
We have Required Experience and/or Education (that's qualifications). Also Preferred Experience in health care or managed care (could be part of Qualifications). Knowledge, Skills And Abilities (that's Skills). So we can have sections: About the role (intro paragraph), Responsibilities, Qualifications, Skills, Benefits, Pay.
We must not repeat job title. Must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content:
Intro: "This position performs data warehouse architecture or enterprise data architecture at a senior level. Essential responsibilities are focused on design and development of data models and ETL specifications, data analysis, system design and architecture, standards and policy administration, and vendor coordination and relations."
That's About the role.
Responsibilities: list under Essential Responsibilities with subheadings: Data Modeling and ETL Specifications, Data Analysis, System Design and Architecture, Standards and Policy Administration, Vendor Coordination and Relations. Each has bullet points.
We need to output - for any list of duties/requirements/benefits. So we can have a
with - items for each responsibility group, maybe each group as a
- containing its details (maybe nested?). Simpler: each bullet as
- with the description.
We must preserve all details. Let's list each responsibility bullet:
- Data Modeling and ETL Specifications:
* Create data models for advanced to complex subjects and provide guidance to junior architects.
* Create advanced ETL specifications to meet business data needs.
* Develop and maintain appropriate documentation, including current design and operation.
- Data Analysis:
* Analyze data sources; partner with leaders across the organization to effectively research and recommend solutions which balance business need and risk mitigation.
- System Design and Architecture:
* Recommend long-term data architecture goals and planning for IS and business.
* Lead and provide direction in creating and managing advanced to complex data warehouse and analytics architectures for use as reference and as input to solution development process.
- Standards and Policy Administration:
* Author and serve as subject matter expert to define requirements, standards and best practices for data modeling, ETL specifications, and data warehouse development.
* Monitor and continually review existing systems to ensure they are designed to comply with established standards and to empower business operations.
- Vendor Coordination and Relations:
* Conduct product and vendor research, and present recommendations to the lead developer and/or management.
* Establish and manage effective relations with vendors and related equipment suppliers, including installation and repair of services.
Now Qualifications (Required Experience and/or Education plus Preferred Experience):
Required:
- Minimum 5 years of data warehouse architecture experience.
- Experience should include most or all of the following:
* Dimensional modeling experience
* Metadata management
* Data quality assessment
* Performance tuning and optimization
* ETL/ELT design
* Cloud warehousing solutions
* Proficiency with SQL
* Health insurance
* Systems analysis and design
* Agile/Scrum methodology
Preferred:
- Experience in health care or managed care
Knowledge, Skills And Abilities:
Required Knowledge:
- Advanced knowledge of cloud data warehousing tools such as Snowflake or Redshift
- Advanced troubleshooting of system performance issues and root cause
Skills And Abilities:
- Advanced knowledge/skills of Microsoft SQL Server
- Advanced knowledge/skills of ETL tools, such as SSIS or Azure Data Factory
- Advanced knowledge/skills of unit and integration testing
- Strong communication skills, including listening, verbal, written, customer service, meeting facilitation, and presentations
- Ability to clearly articulate policies, instructions, goals, and objectives
- Ability to convey appropriate level of detail effectively to all levels of the organization including non-technical staff
- Ability to author policies, document risks, and propose solutions to information technology management and senior leadership
- Possess a high degree of initiative and motivation
- Ability to effectively collaborate with coworkers, staff, leaders, and executives across all departments
- Ability to work effectively with diverse individuals and groups
- Ability to learn, focus, understand, and evaluate information and determine appropriate actions
- Ability to accept direction and feedback, as well as tolerate and manage stress
- Ability to see, read, and perform repetitive finger and wrist movement for at least 6 hours/day
- Ability to hear and speak clearly for at least 3-6 hours/day
Working Conditions: we could incorporate into About the role or a separate section but maybe we can add a short paragraph under About the role? But we have to preserve it. Could add a section "Working Conditions" but not in the list of headings; but it's okay. However instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to include only those headings. We could fold Working Conditions into About the role or Responsibilities. Probably About the role can include a sentence about work environment: indoor/office, no patient facing, hazards, equipment, travel, work location (work from home). Let's incorporate.
Benefits: description of benefits package.
Pay: Estimated Hiring Range $126,720.00 - $154,880.00 Bonus Target Bonus - SIP Target, 5% Annual.
We must not include boilerplate like "Current CareOregon Employees: Please use the internal Workday site to submit an application for this job." etc. Also remove EEO statements.
Now produce HTML fragment:
About the role
This position performs data warehouse architecture or enterprise data architecture at a senior level. Essential responsibilities are focused on design and development of data models and ETL specifications, data analysis, system design and architecture, standards and policy administration, and vendor coordination and relations. Work environment is indoor/office with no patient-facing duties; may involve occasional travel; work location is remote (work from home).
Responsibilities
- Data Modeling and ETL Specifications
- Create data models for advanced to complex subjects and provide guidance to junior architects.
- Create advanced ETL specifications to meet business data needs.
- Develop and maintain appropriate documentation, including current design and operation.
- Data Analysis
- Analyze data sources; partner with leaders across the organization to effectively research and recommend solutions which balance business need and risk mitigation.
- System Design and Architecture
- Recommend long-term data architecture goals and planning for IS and business.
- Lead and provide direction in creating and managing advanced to complex data warehouse and analytics architectures for use as reference and as input to solution development process.
- Standards and Policy Administration
- Author and serve as subject matter expert to define requirements, standards and best practices for data modeling, ETL specifications, and data warehouse development.
- Monitor and continually review existing systems to ensure they are designed to comply with established standards and to empower business operations.
- Vendor Coordination and Relations
- Conduct product and vendor research, and present recommendations to the lead developer and/or management.
- Establish and manage effective relations with vendors and related equipment suppliers, including installation and repair of services.
But nested lists may be okay. However instruction: "Use - for any list of duties/requirements/benefits". It didn't forbid nested lists. Could flatten: each responsibility as a
- with the description including sub-bullets as separate
- maybe. Simpler: just list each bullet as a
- without grouping headings. But we need to preserve headings? Might be okay to keep headings inside
- as plain text.
Let's flatten: each responsibility bullet as a
- with the description.
Thus:
- Data Modeling and ETL Specifications: Create data models for advanced to complex subjects and provide guidance to junior architects; create advanced ETL specifications to meet business data needs; develop and maintain appropriate documentation, including current design and operation.
- Data Analysis: Analyze data sources; partner with leaders across the organization to effectively research and recommend solutions which balance business need and risk mitigation.
- System Design and Architecture: Recommend long-term data architecture goals and planning for IS and business; lead and provide direction in creating and managing advanced to complex data warehouse and analytics architectures for use as reference and as input to solution development process.
- Standards and Policy Administration: Author and serve as subject matter expert to define requirements, standards and best practices for data modeling, ETL specifications, and data warehouse development; monitor and continually review existing systems to ensure they are designed to comply with established standards and to empower business operations.
- Vendor Coordination and Relations: Conduct product and vendor research, and present recommendations to the lead developer and/or management; establish and manage effective relations with vendors and related equipment suppliers, including installation and repair of services.
That preserves all details.
Now Qualifications section:
Qualifications
- Minimum 5 years of data warehouse architecture experience.
- Experience should include most or all of the following:
- Dimensional modeling experience
- Metadata management
- Data quality assessment
- Performance tuning and optimization
- ETL/ELT design
- Cloud warehousing solutions
- Proficiency with SQL
- Health
- with
- items for each responsibility group, maybe each group as a
- containing its details (maybe nested?). Simpler: each bullet as
- with the description.
We must preserve all details. Let's list each responsibility bullet:
- Data Modeling and ETL Specifications:
* Create data models for advanced to complex subjects and provide guidance to junior architects.
* Create advanced ETL specifications to meet business data needs.
* Develop and maintain appropriate documentation, including current design and operation.
- Data Analysis:
* Analyze data sources; partner with leaders across the organization to effectively research and recommend solutions which balance business need and risk mitigation.
- System Design and Architecture:
* Recommend long-term data architecture goals and planning for IS and business.
* Lead and provide direction in creating and managing advanced to complex data warehouse and analytics architectures for use as reference and as input to solution development process.
- Standards and Policy Administration:
* Author and serve as subject matter expert to define requirements, standards and best practices for data modeling, ETL specifications, and data warehouse development.
* Monitor and continually review existing systems to ensure they are designed to comply with established standards and to empower business operations.
- Vendor Coordination and Relations:
* Conduct product and vendor research, and present recommendations to the lead developer and/or management.
* Establish and manage effective relations with vendors and related equipment suppliers, including installation and repair of services.
Now Qualifications (Required Experience and/or Education plus Preferred Experience):
Required:
- Minimum 5 years of data warehouse architecture experience.
- Experience should include most or all of the following:
* Dimensional modeling experience
* Metadata management
* Data quality assessment
* Performance tuning and optimization
* ETL/ELT design
* Cloud warehousing solutions
* Proficiency with SQL
* Health insurance
* Systems analysis and design
* Agile/Scrum methodology
Preferred:
- Experience in health care or managed care
Knowledge, Skills And Abilities:
Required Knowledge:
- Advanced knowledge of cloud data warehousing tools such as Snowflake or Redshift
- Advanced troubleshooting of system performance issues and root cause
Skills And Abilities:
- Advanced knowledge/skills of Microsoft SQL Server
- Advanced knowledge/skills of ETL tools, such as SSIS or Azure Data Factory
- Advanced knowledge/skills of unit and integration testing
- Strong communication skills, including listening, verbal, written, customer service, meeting facilitation, and presentations
- Ability to clearly articulate policies, instructions, goals, and objectives
- Ability to convey appropriate level of detail effectively to all levels of the organization including non-technical staff
- Ability to author policies, document risks, and propose solutions to information technology management and senior leadership
- Possess a high degree of initiative and motivation
- Ability to effectively collaborate with coworkers, staff, leaders, and executives across all departments
- Ability to work effectively with diverse individuals and groups
- Ability to learn, focus, understand, and evaluate information and determine appropriate actions
- Ability to accept direction and feedback, as well as tolerate and manage stress
- Ability to see, read, and perform repetitive finger and wrist movement for at least 6 hours/day
- Ability to hear and speak clearly for at least 3-6 hours/day
Working Conditions: we could incorporate into About the role or a separate section but maybe we can add a short paragraph under About the role? But we have to preserve it. Could add a section "Working Conditions" but not in the list of headings; but it's okay. However instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. Safer to include only those headings. We could fold Working Conditions into About the role or Responsibilities. Probably About the role can include a sentence about work environment: indoor/office, no patient facing, hazards, equipment, travel, work location (work from home). Let's incorporate. Benefits: description of benefits package. Pay: Estimated Hiring Range $126,720.00 - $154,880.00 Bonus Target Bonus - SIP Target, 5% Annual. We must not include boilerplate like "Current CareOregon Employees: Please use the internal Workday site to submit an application for this job." etc. Also remove EEO statements. Now produce HTML fragment:
About the role
This position performs data warehouse architecture or enterprise data architecture at a senior level. Essential responsibilities are focused on design and development of data models and ETL specifications, data analysis, system design and architecture, standards and policy administration, and vendor coordination and relations. Work environment is indoor/office with no patient-facing duties; may involve occasional travel; work location is remote (work from home).
Responsibilities
- Data Modeling and ETL Specifications
- Create data models for advanced to complex subjects and provide guidance to junior architects.
- Create advanced ETL specifications to meet business data needs.
- Develop and maintain appropriate documentation, including current design and operation.
- Data Analysis
- Analyze data sources; partner with leaders across the organization to effectively research and recommend solutions which balance business need and risk mitigation.
- System Design and Architecture
- Recommend long-term data architecture goals and planning for IS and business.
- Lead and provide direction in creating and managing advanced to complex data warehouse and analytics architectures for use as reference and as input to solution development process.
- Standards and Policy Administration
- Author and serve as subject matter expert to define requirements, standards and best practices for data modeling, ETL specifications, and data warehouse development.
- Monitor and continually review existing systems to ensure they are designed to comply with established standards and to empower business operations.
- Vendor Coordination and Relations
- Conduct product and vendor research, and present recommendations to the lead developer and/or management.
- Establish and manage effective relations with vendors and related equipment suppliers, including installation and repair of services.
- for any list of duties/requirements/benefits". It didn't forbid nested lists. Could flatten: each responsibility as a
- with the description including sub-bullets as separate
- maybe. Simpler: just list each bullet as a
- without grouping headings. But we need to preserve headings? Might be okay to keep headings inside
- as plain text. Let's flatten: each responsibility bullet as a
- with the description.
Thus:
- Data Modeling and ETL Specifications: Create data models for advanced to complex subjects and provide guidance to junior architects; create advanced ETL specifications to meet business data needs; develop and maintain appropriate documentation, including current design and operation.
- Data Analysis: Analyze data sources; partner with leaders across the organization to effectively research and recommend solutions which balance business need and risk mitigation.
- System Design and Architecture: Recommend long-term data architecture goals and planning for IS and business; lead and provide direction in creating and managing advanced to complex data warehouse and analytics architectures for use as reference and as input to solution development process.
- Standards and Policy Administration: Author and serve as subject matter expert to define requirements, standards and best practices for data modeling, ETL specifications, and data warehouse development; monitor and continually review existing systems to ensure they are designed to comply with established standards and to empower business operations.
- Vendor Coordination and Relations: Conduct product and vendor research, and present recommendations to the lead developer and/or management; establish and manage effective relations with vendors and related equipment suppliers, including installation and repair of services.
Qualifications
- Minimum 5 years of data warehouse architecture experience.
- Experience should include most or all of the following:
- Dimensional modeling experience
- Metadata management
- Data quality assessment
- Performance tuning and optimization
- ETL/ELT design
- Cloud warehousing solutions
- Proficiency with SQL
- Health
- Data Modeling and ETL Specifications