Data Engineer I

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Larry H. Miller Company" and "Position Summary". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. We need to extract content. We have: - About The Larry H. Miller Company: description of company, mission, vision, values. That's about the company, not necessarily "About the role". But we 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 use those headings if content matches. For company description, maybe "About the role" is not appropriate. Could we create a section "About the company"? Not in list. Probably we should not create a heading not in list. But we could put that content under a

without heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests using those. Safer to stick to those headings only when we have content. We have Position Summary: could be under "About the role". That seems appropriate: summary of role. Then we have Primary Responsibilities (list of bullet points). That's responsibilities. Then Primary Duties (list of bullet points). That's also duties/responsibilities; could combine with responsibilities? Might be redundant. We could treat Primary Duties as responsibilities as well. But we need to preserve all substantive info. Could combine both lists under Responsibilities. Then Job Qualifications: includes Education and experience, Required knowledge and Required knowledge and skills and Preferred knowledge and skills. That's qualifications. Then Core Competencies: could be under Skills? Or maybe separate section "Skills". Core competencies are like skills/behaviors. Could put under Skills. Physical Requirements: maybe not a standard heading; could be omitted? It's substantive but not in list. Could we put under a generic

without heading? Probably better to include as a section? The instruction says prefer a few substantive sections over many thin ones. Could include Physical Requirements under a heading? Not in list. Might be better to omit? But we must preserve ALL substantive information. If we omit, we lose info. Could we include Physical Requirements under a

without heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. It doesn't forbid other headings, but says use

  for section headings (e.g. ...). It implies we should use those headings for sections, but we could also use other headings if needed? Safer to stick to those headings and put other content under appropriate heading or as prose without heading. Physical Requirements is a list of bullet? Actually it's a paragraph: "Work is performed primarily in an office setting. Regularly required to sit, stand, bend, reach, and move about facilities. May be required to perform other duties as assigned." That's prose, could be placed under a

  maybe under a heading like "Working Conditions"? Not in list. Could we put under "Requirements"? Not exactly. Could be part of "Qualifications"? Not really. Could be a separate section with heading "Physical Requirements" but not in list; risk of violating instruction. However instruction says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests examples, not exhaustive list. So we can use other headings as needed, but they gave examples. I'd say it's okay to use Physical Requirements as heading. Also there is a note about job description revision etc. That's boilerplate; we should remove. Also there is "Learn more about us..." and EEO etc. Remove. Thus sections: - About the role (Position Summary) - Responsibilities (combine Primary Responsibilities and Primary Duties) - Qualifications (Education and experience, Required knowledge and skills, Preferred knowledge and skills) - Skills (Core Competencies) - Physical Requirements (Physical Requirements) We should not include Benefits, Pay, Schedule as not present. We need to output only HTML fragment. We'll need to convert lists to

  • . For prose, use

    . We need to preserve all substantive info; not invent or summarize away detail. Let's extract content. About the role (Position Summary): "The Data Engineer I is an entry-level member of the Data & Analytics team who helps build and support reliable data pipelines and analytics-ready datasets. This position works with data from applications, databases, APIs, files, and third-party sources and helps transform that data into trusted, documented, and secure data products in Snowflake. The Data Engineer I works under the guidance of experienced data engineers and the Director of Data and Analytics. The position is responsible for learning and applying sound data-engineering practices, including SQL and Python development, data modeling, testing, monitoring, documentation, source-system integration, and production support. The successful candidate is curious, detail-oriented, comfortable learning new technologies, and able to explain technical issues clearly to both technical and business audiences. Reports to: Director of Data and Analytics" We should keep "Reports to: Director of Data and Analytics" as part of prose. Now Responsibilities: combine Primary Responsibilities and Primary Duties. Primary Responsibilities bullet list: - Protect the legal, financial, and moral well-being of LHM and its portfolio companies. - Support the reliability, accuracy, security, and usability of data used for reporting, analytics, applications, and business decision-making. - Learn from and contribute to the success of other members of the Data & Analytics team. - Seek opportunities to improve data processes, reduce manual work, and increase operational efficiency. - Follow LHM policies, data-security practices, coding standards, and change-management processes. Primary Duties bullet list (many items). We'll need to list each as

  • . Let's capture them: - Build, maintain, and support data ingestion and transformation pipelines using SQL, Python, and approved data-engineering tools. - Pull data from databases, APIs, cloud storage, flat files, and other approved sources into Snowflake or related data platforms. - Organize data into appropriate raw, staged, and curated layers using established team standards. - Develop reusable, parameterized, and maintainable pipeline components rather than one-time manual processes. - Create and maintain analytics-ready tables, views, data marts, and dimensional models for reporting and analysis. - Apply business rules, transformations, calculations, and standard definitions in partnership with analysts and business stakeholders. - Implement data-quality checks for completeness, accuracy, duplicates, nulls, referential integrity, valid values, and unexpected changes in record volumes. - Reconcile data between source systems and the data platform and investigate discrepancies. - Schedule, monitor, and troubleshoot data jobs, including reviewing logs, identifying root causes, documenting incidents, and escalating issues when appropriate. - Support pipeline alerts, retries, restart procedures, and other reliability practices. - Document data sources, refresh schedules, transformations, dependencies, ownership, and known limitations. - Create technical specifications, process diagrams, test plans, and deployment documentation. - Write and maintain unit, integration, regression, and data-validation tests and document test results. - Use Git, pull requests, code reviews, and established development, test, and production promotion practices. - Participate in technical design discussions and contribute to continuous improvement of the team’s data-engineering framework. - Assist with Snowflake performance and cost optimization by improving queries, models, workloads, and data structures. - Follow security and governance practices for sensitive financial, employee, customer, health, and other restricted data, including appropriate access controls and data handling. - Collaborate with data analysts, BI developers, application teams, finance, HR, and other business stakeholders to understand requirements and deliver reliable data. - Assist with production support and participate in on-call or after-hours support when required by team practices. - Stay current with modern data-engineering practices and learn new technologies as the LHM data platform evolves. - Perform other duties as assigned. Now Qualifications: Education and experience: "Bachelor’s degree in computer science, information systems, data engineering, data analytics, engineering, or a related field preferred; equivalent education, training, internship, project, or work experience may be considered. Zero to two years of experience in data engineering, software development, analytics engineering, database development, or a related field. Relevant academic, internship, or portfolio projects may qualify. Demonstrated experience completing a data, programming, database, or automation project from requirements through testing and documentation." Required knowledge and skills (list): - Strong foundation in SQL, including joins, common table expressions, aggregations, window functions, and basic query troubleshooting. - Working knowledge of Python or another modern programming language, with the ability and willingness to develop in Python. - Understanding of relational databases, data types, keys, normalization, and basic dimensional data-modeling concepts. - Understanding of ETL and ELT concepts, including ingestion, transformation, loading, incremental processing, and data validation. - Familiarity with REST APIs, JSON, CSV files, or other common data-integration formats. - Familiarity with Git, source control, testing, debugging, and code documentation. - Strong analytical and problem-solving skills, including the ability to investigate unexpected data results. - Strong attention to detail and commitment to data accuracy, security, and reliability. - Ability to communicate clearly in writing and verbally and adjust technical explanations for different audiences. - Ability to work collaboratively, accept feedback, manage priorities, and ask for help when appropriate. Preferred knowledge and skills (list): - Experience with Snowflake or another cloud data warehouse. - Experience with dbt, Control-M, Airflow, Prefect, or another workflow-orchestration tool. - Experience with AWS services such as S3, Lambda, Glue, Secrets Manager, or SNS. - Experience with Power BI or another business-intelligence platform, especially data models and semantic layers. - Familiarity with CI/CD, Docker, Linux, cloud security, data cataloging, metadata, lineage, or data-governance practices. - Familiarity with financial, ERP, HR, ticketing, sports, real estate, health-care, or other operational data. - Basic understanding of accounting concepts such as general ledger, debits and credits, trial balance, and financial statements. Core Competencies (list): - Cultivates Innovation and Strategy - Looks for practical ways to improve data processes, reliability, efficiency, and maintainability. - Learns new technologies and applies sound judgment when selecting tools and approaches. - Brings forward useful ideas and alternative ways to solve problems. - Communicates Effectively - Listens carefully and clarifies requirements before beginning work. - Adjusts communication style to fit technical, business, and executive audiences. - Provides timely updates about progress, risks, data issues, and dependencies. - Documents work so others can understand, support, and improve it. - Collaborates - Works cooperatively with data, IT, business, and vendor teams. - Builds trust through reliability, follow-through, and respect for others’ expertise. - Gives and receives feedback professionally. - Contributes to team standards and helps create a positive learning environment. - Operates with Integrity - Handles company and customer data responsibly and follows security and privacy requirements. - Demonstrates ethical behavior and professionalism consistent with LHM standards. - Follows policies, procedures, change controls, and approved development practices. - Takes ownership of mistakes, communicates issues promptly, and works toward resolution. Physical Requirements: "Work is performed primarily in an office setting. Regularly required to sit, stand, bend, reach, and move about facilities. May be required to perform other duties as assigned." Now we need to output HTML. We'll have: