Senior Data Engineer
or drop it. This is not Job ID but a requirement; maybe keep as part of Requirements. We need sections: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content for it. So we need to decide which sections to include.
We have content: "The Work You'll Do" -> Responsibilities. "More Specifically, You Will" could be part of Responsibilities as well. Could combine.
"What We Need From You" -> Requirements/Qualifications/Skills. Could split: Must Have as Requirements, Nice to Have as Skills or Qualifications.
"What Does Sovos Offer You?" -> Benefits.
We have no explicit Pay or Schedule info, so we should NOT create those sections.
We also have intro paragraph about company mission; could be "About the role" or maybe "About Sovos". But rule: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The intro could be "About the role". However they said do NOT repeat the job title as a heading (the page already shows it). The intro is not job title; it's company description. Could be "About the role" or maybe we omit About the role if not needed. But we have substantive content: "Build your future with Sovos..." That's more about company; could be placed under About the role.
We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all bullet points etc.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus we will parse the posting and create sections.
Let's extract content:
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; could be under About the role.
Next: "The Work You’ll Do 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."
That's responsibilities prose.
Then "More Specifically, You Will" 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
These are duties; we can put under Responsibilities as a list.
Next: "What We Need From You" with Must Have bullet list:
- Advanced SQL – CTEs, window functions, LATERAL joins, performance tuning, and complex multi-source queries. This is the one 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
These are requirements/qualifications/skills. Could separate: Requirements (years, experience), Qualifications (education? none), Skills (SQL, communication, etc). But we can combine into Requirements section with list.
Next: "Nice to Have" bullet list:
- Fluency in the revenue data chain: Billing → ARR → Deferred Revenue → Rev Rec → Close Pack
- B2B SaaS metrics: ARR, GRR, NRR, churn, and deferred revenue
- CRM/ERP integration (NetSuite, Salesforce, or similar): ELT patterns, API pagination, incremental loads
- Python for pipeline scripting and orchestration
- Model Context Protocol (MCP) or similar frameworks for connecting AI agents to structured data
- RAG architecture, hybrid retrieval strategies, or prompt engineering
- Domain knowledge in compliance, tax technology, or e-invoicing
These could be Skills or Qualifications.
Next: "Due to client contractual obligations, the successful candidate will be asked to clear a background check and drug test upon hire." This is a requirement; could be included in Requirements as a note.
Next: "What Does Sovos Offer You?" bullet list:
- The tools to enhance your life – because we want you to enjoy your life outside of work and inside!
- 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!
These are Benefits.
After that there is EEO boilerplate etc which we need to remove.
Also there is "Company Background" section describing Sovos; that's also substantive but maybe could be part of About the role or separate About the company. However rule: we should include sections only when posting has real, specific content for it. The company background is substantive; we could include an "About the company" but not in the list of allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we could fold company background into About the role or maybe omit it? But we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. The allowed headings are examples; we can use other headings? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use other headings if needed? However they say "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". They didn't restrict to only those headings, but they gave examples. Safer to stick to those headings; we can put company background under About the role (makes sense). So About the role will contain both intro and company background.
Thus sections:
- About the role (h3) containing prose: intro + company background.
- Responsibilities (h3) containing prose paragraph + ul list of duties.
- Requirements (h3) containing ul list of must-have items + maybe background check note.
- Skills (h3) containing ul list of nice-to-have items.
- Benefits (h3) containing ul list of offerings.
We should not include Qualifications separately if we used Requirements; but we could also split Must Have into Requirements and Qualifications. However we have no explicit qualifications like degree; we could treat Must Have as Requirements and Nice to Have as Skills. That seems fine.
We must not include Pay or Schedule sections.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
Build your future with Sovos ...
Company background ...
But we need to ensure we preserve all substantive info; we need to combine the intro paragraphs and company background into maybe multiple tags.
Let's extract exact text:
Intro paragraph (first paragraph up to "here.") Actually there are multiple sentences. Let's copy:
"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."
Note there is no space after "Sovos" before "If". We'll keep as is.
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
- for any list of duties/requirements/benefits, and
for prose. Thus we will parse the posting and create sections. Let's extract content: 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; could be under About the role. Next: "The Work You’ll Do 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." That's responsibilities prose. Then "More Specifically, You Will" 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 These are duties; we can put under Responsibilities as a list. Next: "What We Need From You" with Must Have bullet list: - Advanced SQL – CTEs, window functions, LATERAL joins, performance tuning, and complex multi-source queries. This is the one 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 These are requirements/qualifications/skills. Could separate: Requirements (years, experience), Qualifications (education? none), Skills (SQL, communication, etc). But we can combine into Requirements section with list. Next: "Nice to Have" bullet list: - Fluency in the revenue data chain: Billing → ARR → Deferred Revenue → Rev Rec → Close Pack - B2B SaaS metrics: ARR, GRR, NRR, churn, and deferred revenue - CRM/ERP integration (NetSuite, Salesforce, or similar): ELT patterns, API pagination, incremental loads - Python for pipeline scripting and orchestration - Model Context Protocol (MCP) or similar frameworks for connecting AI agents to structured data - RAG architecture, hybrid retrieval strategies, or prompt engineering - Domain knowledge in compliance, tax technology, or e-invoicing These could be Skills or Qualifications. Next: "Due to client contractual obligations, the successful candidate will be asked to clear a background check and drug test upon hire." This is a requirement; could be included in Requirements as a note. Next: "What Does Sovos Offer You?" bullet list: - The tools to enhance your life – because we want you to enjoy your life outside of work and inside! - 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! These are Benefits. After that there is EEO boilerplate etc which we need to remove. Also there is "Company Background" section describing Sovos; that's also substantive but maybe could be part of About the role or separate About the company. However rule: we should include sections only when posting has real, specific content for it. The company background is substantive; we could include an "About the company" but not in the list of allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". So we could fold company background into About the role or maybe omit it? But we must preserve ALL substantive information; we cannot drop it. So we need to include it somewhere. The allowed headings are examples; we can use other headings? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we could use other headings if needed? However they say "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". They didn't restrict to only those headings, but they gave examples. Safer to stick to those headings; we can put company background under About the role (makes sense). So About the role will contain both intro and company background. Thus sections: - About the role (h3) containing prose: intro + company background. - Responsibilities (h3) containing prose paragraph + ul list of duties. - Requirements (h3) containing ul list of must-have items + maybe background check note. - Skills (h3) containing ul list of nice-to-have items. - Benefits (h3) containing ul list of offerings. We should not include Qualifications separately if we used Requirements; but we could also split Must Have into Requirements and Qualifications. However we have no explicit qualifications like degree; we could treat Must Have as Requirements and Nice to Have as Skills. That seems fine. We must not include Pay or Schedule sections. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:
About the role
Build your future with Sovos ...
Company background ...
But we need to ensure we preserve all substantive info; we need to combine the intro paragraphs and company background into maybe multipletags. Let's extract exact text: Intro paragraph (first paragraph up to "here.") Actually there are multiple sentences. Let's copy: "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." Note there is no space after "Sovos" before "If". We'll keep as is. 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