Analyst, Data Engineering

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Content: - Intro about Bank OZK: "Why Bank OZK Founded on a legacy...". That's about the company, could be "About the role"? Actually "About the role" is about the job, but we have company description. Could treat as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" heading with content describing the role and company? The posting includes "Job Purpose & Scope" which describes the role. So we can put that under "About the role". Also we have "Essential Job Functions" which are responsibilities/duties. So "Responsibilities". Then "Knowledge, Skills & Abilities" could be Skills. Also "Basic Qualifications" could be Qualifications. Also "Job Expectations" maybe part of Requirements? Could be "Requirements". Also "Benefits" is mentioned: "We believe in providing our dedicated team members with the best resources to support their physical, mental and financial wellbeing, including generous PTO, 401(k) matching, health, dental, vision (and pet!) insurance as well as special perks and discounts." Also a link "Learn more about Bank OZK benefits". So we have benefits content. Pay and Schedule: Not mentioned. So we should NOT include Pay or Schedule sections. We must not repeat job title as heading. Job title is "Analyst, Data Engineering". Not to be used as heading. We must not include Job ID/requisition numbers. We must remove boilerplate: EEO statement, Member FDIC, note about not exhaustive list, etc. Also remove "Learn more about Bank OZK benefits ." maybe keep as part of benefits? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO statement is boilerplate, remove. Also "Member FDIC." remove. Also "Note: This description is not an exhaustive list..." remove. Also "Management reserves the right..." maybe remove as boilerplate? It's about job expectations; could be considered part of Requirements? But it's generic; maybe we can keep as part of Requirements? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The note about not exhaustive list is boilerplate; we should remove. The management reserves right also boilerplate; remove. Also "Job Expectations Operate customary equipment and technology used in a business environment, with or without accommodation." That's a requirement; keep maybe under Requirements. Now we need to structure. Sections: - About the role: content from "Job Purpose & Scope" plus maybe company intro? The company intro is about Bank OZK, not the role. Could be considered "About the role"? Might be better to include company intro under About the role? The instruction: About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put the description of the role and maybe company context. We'll include the "Job Purpose & Scope" paragraph(s). Also maybe the first paragraph about Bank OZK could be considered "About the role"? Not exactly, but we could include it as part of About the role to give context. However the instruction says "do NOT repeat the job title as a heading". It doesn't forbid including company description. I'd include a brief paragraph about Bank OZK under About the role as it's substantive. Thus About the role content: combine the intro paragraph(s) about Bank OZK and the Job Purpose & Scope. Let's extract: Intro: "Why Bank OZK Founded on a legacy of more than 120 years in banking, Bank OZK is much more than just a company. We’re nationally recognized as an industry leader in financial services. That means we combine exceptional service with innovative technologies to deliver smart solutions to our clients across the country. We’re investing in small businesses, fueling economies in local communities and changing skylines in the largest cities across America. Here, we're not simply filling roles. We're fostering even greater careers. The foundation for a great career starts with an exceptional team and a comprehensive benefits package. We believe in providing our dedicated team members with the best resources to support their physical, mental and financial wellbeing, including generous PTO, 401(k) matching, health, dental, vision (and pet!) insurance as well as special perks and discounts. Learn more about Bank OZK benefits ." But note that benefits part is duplicated later; we will move benefits to Benefits section. So we should not duplicate benefits in About the role. So we can keep the intro up to "Here, we're not simply filling roles. We're fostering even greater careers. The foundation for a great career starts with an exceptional team and a comprehensive benefits package." Then we can mention benefits generically but not list specifics; but we have a Benefits section later with specifics. To avoid duplication, we can keep a sentence about benefits but not list specifics. However the instruction says preserve ALL substantive information; we can keep the sentence about benefits but not list specifics; the specifics will be in Benefits section. That's okay. Thus About the role: combine the intro up to benefits mention, plus Job Purpose & Scope. Job Purpose & Scope: "As Analyst, Data Engineering, you will assist with developing, testing, and maintaining data solutions that support the Bank's Data Strategy. In this role, you will work under general direction to translate defined business and technical requirements into data models, ETL or ELT processes, reports, and other data solutions. As a member of the Data Engineering Team, you will complete assigned development and support activities while building knowledge of the Bank's data architecture, platforms, standards, and business processes. You will demonstrate effective customer service, problem-solving, planning, teamwork, communication, and organizational skills." We'll put that. Now Responsibilities: from "Essential Job Functions" list. We need to convert each bullet into

under

. The list includes many items. We'll preserve all. Let's extract the list items: - Assist with the development and maintenance of data models, data pipelines, reports, and other data solutions in accordance with established engineering standards. - Complete assigned data development tasks under the direction of more experienced Data Engineering team members or management. - Perform testing and validation of data solutions to verify that established business and technical requirements are met. - Identify, document, and assist with resolving data defects, processing errors, and other technical issues. - Escalate complex data or development issues to more experienced team members or management when appropriate. - Provide estimates for assigned work and communicate changes that may affect expected completion. - Follow established data development, documentation, testing, and deployment standards. - Work collaboratively with Data Engineering team members, management, business partners, and other technology teams. - Assist with the design, development, implementation, and production support of data applications and solutions. - Apply foundational knowledge of data modeling, ETL or ELT methodologies, database development, and reporting technologies to assigned work. - Develop an understanding of the Bank's enterprise data architecture, data platforms, data operations, and governance requirements. - Assist with preparing technical documentation and deployment materials for data solution releases. - Coordinate with the Data Assurance and Deployment team as directed to support smooth and properly documented releases. - Learn the business processes, data requirements, and operating environments of supported lines of business. - Follow established change control and version management processes. - Participate in training and professional development activities to expand technical and business knowledge. - Keep informed of developments in data engineering tools, platforms, and practices relevant to assigned responsibilities. - Enthusiastically embrace, support, and model the Bank's values and mission. - Ensure compliance with internal and external regulatory policies, procedures, and guidelines. Now Responsibilities section heading

Responsibilities

with
• ... etc. Now Requirements: Could include "Job Expectations" and maybe "Basic Qualifications"? Actually Basic Qualifications is separate. Requirements could be the "Job Expectations" plus maybe "Basic Qualifications"? But we have Qualifications section separate. The instruction list includes Requirements and Qualifications as separate headings. So we need to decide what goes where. Typically: Requirements = mandatory experience/skills; Qualifications = education/experience etc. But we have "Basic Qualifications" which includes degree, experience, SQL, etc. Also "Knowledge, Skills & Abilities" which is skills. So we can map: - Requirements: maybe the "Job Expectations" statement about operating equipment, plus maybe the "Basic Qualifications"? But we have Qualifications heading for basic qualifications. Let's follow the given headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Thus: - Requirements: could be the "Job Expectations" plus any other mandatory expectations like "Operate customary equipment and technology used in a business environment, with or without accommodation." Also maybe the note about not exhaustive list we removed. So we can put that under Requirements. - Qualifications: the "Basic Qualifications" bullet list: Bachelor's degree, at least 1 year experience, experience with SQL, etc. Also preferred qualifications? Those could go under Skills? Actually "Preferred" items could be under Skills. But we have Skills heading separate. So we can put preferred qualifications under Skills. - Skills: from "Knowledge, Skills & Abilities" list plus preferred experience items (experience with reporting tools, ETL tools, Jira, Azure DevOps, cloud platform, certifications). Also maybe the "Ability to ..." list. Thus we need to parse Knowledge, Skills & Abilities list. Let's extract that list: - Foundational knowledge of database development, data warehousing, data modeling, reporting, and data integration concepts. - Foundational knowledge of ETL or ELT processes and relational database concepts. - Ability to learn and apply established data development standards, procedures, and technical requirements. - Ability to analyze defined problems, identify potential causes, and assist with implementing appropriate solutions. - Ability to test and validate data for accuracy, completeness, and consistency. - Ability to organize work, manage assigned priorities, and meet established deadlines. - Ability to maintain focus for sustained periods while completing individual or multiple assigned tasks. - Ability to perform effectively in a challenging and changing work environment. - Ability to communicate effectively, both verbally and in writing, with employees at various levels of the organization. - Ability to document technical processes, testing results, issues, and resolutions clearly and accurately. - Ability to work independently on defined assignments under general supervision and collaboratively within a team environment. - Skill in using computers and Microsoft Office applications, including Word, Excel, and Outlook. Now preferred qualifications/experience: - Experience with a reporting or data visualization technology such as Power BI, SSRS, Tableau, Qlik, or a similar platform, preferred. - Experience with an ETL or ELT tool or data integration process, preferred. - Experience with Jira, Azure DevOps, or a similar development management environment, preferred. - Experience with a cloud-based data platform, such as Snowflake, preferred. - Data development or cloud platform certification, such as SnowPro or a Microsoft data certification, preferred. We can put these under Skills as well (maybe as bullet points). Or we could put them under Qualifications as "Preferred qualifications". But we have Skills heading; it's appropriate. Now Benefits: we have the benefits description: "We believe in providing our dedicated team members with the best resources to support their physical, mental and financial wellbeing, including generous PTO, 401(k) matching, health, dental, vision (and pet!) insurance as well as special perks and discounts." Also maybe the line "Learn more about Bank OZK benefits ." We can keep the benefits description; we can drop the "Learn more..." as it's a link/instruction. So Benefits section content: that sentence. Now we must not include Pay or Schedule sections. Now we need to output only HTML fragment, no <