Senior Data Engineer

We need to produce HTML fragment with sections: About the role? The posting includes intro paragraphs about Sovos, then "The Work You'll Do", then "More Specifically, You Will", then "What We Need From You", then "Nice to Have", then "Due to client contractual obligations..." (background check) then "What Does Sovos Offer You?" then benefits list, then EEO boilerplate (remove), then Company Background (maybe we can include as About the role? but we should not repeat job title). We need to decide which sections to include based on actual content. We must not include Job ID/requisition numbers. No application instructions. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. So we should drop the EEO paragraph and maybe the Company Background? The instruction: "Prefer a few substantive sections over many thin ones." We can include sections: About the role (maybe combine intro and company background?), Responsibilities (the work you'll do + more specifically), Requirements (what we need from you), Nice to Have (nice to have), Benefits (what does Sovos offer you?). Pay and Schedule not present, so omit those sections. Also we should not include sections with filler like "commensurate with experience". Not present. We need to use

for section headings. Use

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

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep details like bullet points etc. We'll need to convert paragraphs into

  . For lists, we need to detect bullet points. Let's parse the posting. Intro: "Build your future with Sovos If you’re seeking a career where innovation meets impact, you’ve come to the right place. As a global leader, Sovos is transforming tax compliance from a business requirement to a force for growth while revolutionizing how businesses navigate the ever-changing regulatory landscape. At Sovos, we’re dedicated to more than just solving compliance challenges – we’re committed to making a positive and lasting difference in everything we do. Our teams operate on the modern edge of digital technology, working not only to solve complex business challenges but also to enrich our personal, professional, and local communities. Don’t worry if you don’t check all the boxes – apply anyway! We’re focused on hiring the right people, not just the “right” resume. It’s not about what you’ve done elsewhere; it’s all about what you’re capable of doing here." That's prose; we can put in

  . Then "The Work You’ll Do" heading (but we will not repeat job title). We'll make a section heading

  Responsibilities

  maybe. The content: "Sovos is building a world-class data platform, and the Senior Data Engineer is the foundation it runs on. You’ll own the full pipeline stack – from ingestion through transformation to the trusted, decision-ready outputs the business depends on. This is high-visibility, high-ownership engineering with a direct line to business impact. Today that means our US financial data chain, built on Snowflake and dbt. Tomorrow it may be a different domain and a different stack. We’re looking for someone who learns new business domains quickly, stays effective when the technology underneath changes, and takes ownership without waiting to be asked." Then "More Specifically, You Will" with bullet list: - Design and build the data models that power business-critical domains – today our financial data chain (Billing → ARR → Deferred Revenue → Rev Rec → Close Pack), tomorrow whatever the business needs most - Deliver ingestion and transformation models with full test coverage and documentation - Own reliability for vital pipelines – monitor, alert on, and recover from failures, and act as the escalation point when something breaks - Establish data quality standards, testing conventions, and governance patterns for the broader team - Treat documentation as a production deliverable – clear table descriptions, column definitions, and grain statements directly determine whether business users and AI consumers can trust the answer - Partner directly with business stakeholders to make sure technical outputs actually map to what they need - Pick up new domains and new tooling quickly, with minimal hand-holding – both the stack and the business context will evolve We need to preserve all details. Then "What We Need From You" heading. Content: bullet list of Must Have and Nice to Have? Actually they separate Must Have and Nice to Have later. Under "What We Need From You" they list Must Have items (Advanced SQL, communication skills, 5-8 years experience, modern cloud warehouse, data modeling framework, ownership of vital pipelines, data governance practices, cloud infrastructure CI/CD fundamentals, high adaptability). Then after that they have "Nice to Have" list. Thus we can make a section

  Requirements

  containing Must Have items as
  • . Then maybe a separate

    Nice to Have

    for those. But instruction: "Prefer a few substantive sections over many thin ones." Could combine Must Have and Nice to Have under Requirements? But they'd be separate lists; we could still have two subheadings? But we only allowed

    for section headings. Could we use

    Requirements

    and inside have two

    ? Not allowed? Only said use

    for section headings. It didn't forbid other headings, but to be safe we can just make two sections: Requirements and Nice to Have. That's okay. Then "What Does Sovos Offer You?" heading with benefits list: Flexible Time-Off, Comprehensive Health, Dental and Vision benefits, 401(k) with employee sponsored match, Bi-Weekly Meeting Free Days, Mentoring Programs, Globally recognized Training and Development programs, Tuition Reimbursement, Time off to Volunteer, Charitable Giving Match, and more! We'll put as

    • . We should drop the EEO paragraph and Company Background? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Company Background is not boilerplate; it's substantive about the company. Could be considered part of About the role. We could include an "About the company" section. But we already have intro about Sovos. Might be redundant. However we should preserve ALL substantive information; we cannot omit company background if it's substantive. The intro already covers some but not all details like founded 1979, owned by Hg and TA Associates, processes three billion transactions, etc. That's substantive. So we should include a section maybe "About Sovos" or keep as part of introductory paragraph. We could extend the introductory

      to include that info. Since we cannot invent or summarize away detail, we need to include that info. So we can add after the intro a paragraph with company background. Thus we could have sections: About the role (intro + company background), Responsibilities, Requirements, Nice to Have, Benefits. Let's craft. We need to ensure we don't repeat the job title as a heading. We'll not include any heading like "Senior Data Engineer". Good. Now produce HTML fragment. We'll start with

      for intro paragraph(s). Might need multiple

      for readability but okay. Let's draft:

      Build your future with Sovos. If you’re seeking a career where innovation meets impact, you’ve come to the right place. As a global leader, Sovos is transforming tax compliance from a business requirement to a force for growth while revolutionizing how businesses navigate the ever‑changing regulatory landscape. At Sovos, we’re dedicated to more than just solving compliance challenges – we’re committed to making a positive and lasting difference in everything we do. Our teams operate on the modern edge of digital technology, working not only to solve complex business challenges but also to enrich our personal, professional, and local communities. Don’t worry if you don’t check all the boxes – apply anyway! We’re focused on hiring the right people, not just the “right” resume. It’s not about what you’ve done elsewhere; it’s all about what you’re capable of doing here.

      Then company background paragraph:

      Sovos is a global provider of tax, compliance and trust solutions and services that enable businesses to navigate an increasingly regulated world with true confidence. Purpose‑built for always‑on compliance capabilities, our scalable IT‑driven solutions meet the demands of an evolving and complex global regulatory landscape. More than 100,000 customers in 100+ countries – including half the Fortune 500 – trust Sovos for their compliance needs. Sovos annually processes more than three billion transactions across 19,000 global tax jurisdictions. Founded in 1979, Sovos has operations across the Americas and Europe, and is owned by Hg and TA Associates.

      Now Responsibilities section:

      Responsibilities

      Sovos is building a world‑class data platform, and the Senior Data Engineer is the foundation it runs on. You’ll own the full pipeline stack – from ingestion through transformation to the trusted, decision‑ready outputs the business depends on. This is high‑visibility, high‑ownership engineering with a direct line to business impact. Today that means our US financial data chain, built on Snowflake and dbt. Tomorrow it may be a different domain and a different stack. We’re looking for someone who learns new business domains quickly, stays effective when the technology underneath changes, and takes ownership without waiting to be asked.

      More Specifically, You Will

      • Design and build the data models that power business‑critical domains – today our financial data chain (Billing → ARR → Deferred Revenue → Rev Rec → Close Pack), tomorrow whatever the business needs most
      • Deliver ingestion and transformation models with full test coverage and documentation
      • Own reliability for vital pipelines – monitor, alert on, and recover from failures, and act as the escalation point when something breaks
      • Establish data quality standards, testing conventions, and governance patterns for the broader team
      • Treat documentation as a production deliverable – clear table descriptions, column definitions, and grain statements directly determine whether business users and AI consumers can trust the answer
      • Partner directly with business stakeholders to make sure technical outputs actually map to what they need
      • Pick up new domains and new tooling quickly, with minimal hand‑holding – both the stack and the business context will evolve
      Now Requirements section:

      Requirements

      • Advanced SQL – CTEs, window functions, LATERAL joins, performance tuning, and complex multi‑source queries (non‑negotiable)
      • Very strong communication skills – you adapt how you explain things to your audience, whether that’s a finance analyst, an executive, or another engineer; you can describe a technical problem in plain language without jargon, walk a non‑technical stakeholder through what went wrong and what happens next, and write documentation a business user can actually use to validate their own numbers
      • 5–8 years in data engineering, with a track record of building and maintaining production pipelines and data models at scale
      • A modern cloud warehouse or lakehouse – Snowflake, Databricks, or equivalent; you’ve owned the environment (roles, compute, governance, access controls), not just queried it
      • A data modeling and transformation framework – dbt, Databricks/DLT, or equivalent; modular models, tests, and documentation as standard practice
      • Ownership of vital pipelines – keeping them running with no to very small downtime, and achieving high reliability through extensive testing and data baselines
      • Data governance practices – PII handling, access control, and GDPR basics
      • Cloud infrastructure and CI/CD fundamentals – Azure or AWS
      • High adaptability – you learn unfamiliar business domains and new tooling autonomously and get productive fast
      Now Nice to Have section:

      Nice to Have