Senior Data Engineer

Benefits

• items. We must not include Pay or Schedule unless posting actually states them. There's no explicit pay or schedule beyond hybrid expectation (onsite four days). That is schedule info: "The current expectation is for employees to work onsite four days per week". That's schedule. So we can include Schedule section with that detail. However we must not create placeholder text like "varies". It's specific: four days per week onsite. So we can include Schedule. Pay: not mentioned, so omit. Now we need to decide sections: About the role (maybe include hybrid role location and expectation). Responsibilities (list of duties). Requirements (education + experience). Qualifications (technical skills). Benefits. Schedule. We could combine Requirements and Qualifications into one Requirements section, but guidelines: prefer few substantive sections over many thin ones. However we have enough content for separate sections. We must not repeat job title as heading. Use

  for section headings. We must use

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

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to drop lines like "This job description is not meant to be an all-inclusive list..." and EEO paragraphs, accommodation request, etc. We need to keep the hybrid role description, responsibilities list, requirements list, qualifications list, benefits list, schedule expectation. Let's extract responsibilities as bullet items: - designing and implementing Kimball-style dimensional models and analytical datasets - developing transformations with tests, documentation, and data contracts - building and maintaining ELT/ETL workflows into data warehouses/lakes, including orchestration, monitoring, and cost/performance tuning - developing governed BI semantic models and datasets for Power BI - enabling self-service while enforcing data quality, lineage, and security policies - evangelizing data and tools that increase organizational access to data and ad hoc capabilities to help stakeholders draw conclusions and drive data-informed decisions - continuously exploring internal and external data sources and working with BSAs and Data Engineering teams to ingest data into data lake/data bricks/synapse for analysis and development - eliciting and clarifying business requirements - documenting specs, KPIs, and acceptance tests - delivering demos, office hours, and enablement - implementing CI/CD (Git-based), unit/integration testing, and data observability SLAs/SLOs - profiling SQL and storage strategies, caching, and compute scaling - contributing to catalog/lineage, RBAC/ABAC, PII handling, and retention standards Now requirements (education + experience): - Bachelor’s degree in Computer Science, Information Technology, Electrical Engineering, or related field (foreign equivalent) - 36 months of experience in the job offered or related position, including experience with: - SQL development, including writing complex queries, stored procedures, views, joins, and performing performance tuning in SQL Server environments - ETL/ELT development using SSIS or equivalent tools, including data mapping, transformations, workflow scheduling, and job automation - Power BI development, including building semantic models, dashboards, and reports; creating DAX measures; performing Power Query (M) transformations; and publishing to Power BI Service - dimensional data modeling, including designing star and snowflake schemas using Kimball or equivalent methodologies - data validation and profiling, including dataset optimization, incremental refresh, and cross-system data reconciliation - working with databases and cloud platforms such as Azure SQL or Snowflake - JIRA for issue tracking and project management We could treat the bullet list under experience as part of Requirements. Qualifications: maybe we can separate technical skills as Qualifications, but they are already in requirements. To avoid duplication, we could have Requirements (education + experience) and Qualifications (technical skills). However the technical skills list is part of the experience requirement. Might be okay to keep as Requirements only. But guidelines: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those headings possibly. We can include Qualifications and Skills separate if we have content. We have technical skills list; we could put them under Qualifications or Skills. Let's decide: - About the role: hybrid role, location, onsite expectation. - Responsibilities: list of duties. - Requirements: education + experience (maybe just degree and years). - Qualifications: technical skills list (SQL, ETL/ELT, Power BI, dimensional modeling, data validation, cloud platforms, JIRA). - Skills: maybe we could also list soft skills? Not present. Could omit Skills section if no specific content. - Benefits: list. - Schedule: onsite four days per week. We must not create sections with filler. So if we have no content for Skills, we omit it. Now we need to ensure we don't repeat info. For example, the technical skills list appears also under Requirements experience. If we separate, we might duplicate. Better to keep Requirements include both education+experience and technical skills, and omit Qualifications/Skills. But the heading list includes Qualifications and Skills as examples; we can omit if not needed. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Check if we have any content for Pay: none, omit. Now craft HTML. We need to wrap each section:

    About the role

    then

    ...

    for prose. For lists:

    Responsibilities

    • ...
    . Make sure to preserve all substantive information: include location (headquarters near Portland, Oregon), hybrid role, onsite four days per week expectation. In About the role we can include: "This position is designated as a hybrid role based out of our headquarters near Portland, Oregon. The current expectation is for employees to work onsite four days per week, subject to change based on business needs. This in-office requirement may be adjusted at the discretion of the company. Columbia Sportswear Company is seeking a Senior Data Engineer in Portland, OR." That's prose. But note: we should not repeat the job title as a heading, but we can mention it in prose. That's fine. Now Responsibilities list as above. Requirements: education + experience. We'll need to include the degree requirement and 36 months experience, plus the list of experience areas. Could be a
    with sub-items? We can just list each requirement as
    • . For the experience with items, we can embed them as part of the
    • text. Simplify:
    • Bachelor’s degree in Computer Science, Information Technology, Electrical Engineering, or related field (foreign equivalent)
    • 36 months of experience in the job offered or related position, including experience with:
    Then a nested
    for the experience items. However guidelines: use
    • for any list of duties/requirements/benefits. Nested lists are okay but we need to ensure proper HTML. We'll do nested
      . Similarly for Benefits: list items. Schedule: we can have

      The current expectation is for employees to work onsite four days per week, subject to change based on business needs. This in-office requirement may be adjusted at the discretion of the company.

      but that's already in About the role. Actually we placed schedule expectation in About the role. To avoid duplication, we could move schedule to its own section and keep About the role more generic. Let's think. About the role: we could keep it short: "This position is designated as a hybrid role based out of our headquarters near Portland, Oregon. Columbia Sportswear Company is seeking a Senior Data Engineer in Portland, OR." Then Schedule section: "The current expectation is for employees to work on