Data Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes "Why Pythian", "Why You", "What You Will Be Doing", "What We Need From You", "What Sets You Apart From Other Applicants", "What You Will Receive", "The Pay Range For This Role Is ...". Also maybe "Pythian Careers" etc but we ignore boilerplate. We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings as appropriate. The posting doesn't have explicit headings but we can infer sections: "Why Pythian" maybe about company, could be "About the role"? Actually "About the role" is generic; we could use "About the role" heading for description of role? But we have "Why You" and "What You Will Be Doing" etc. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content. We should include sections that have real specific content. We have: - Why Pythian: company overview. Could be placed under "About the role"? Not exactly. Could be "About the company"? Not in list. But we can still use "About the role" maybe for role description? However we have "What You Will Be Doing" which is responsibilities. So we can put that under

Responsibilities

. - "What We Need From You" is requirements/qualifications. Could be

Requirements

or

Qualifications

. We'll choose Requirements. - "What Sets You Apart From Other Applicants" could be Skills or Qualifications? It's additional differentiators. Could be

Skills

or

Qualifications

. We'll maybe put under Skills. - "What You Will Receive" is benefits. So

Benefits

. - Pay range:

Pay

. - Schedule: Not mentioned explicitly, but there is "Flexibly work remotely from your home, there’s no daily travel requirement to an office!" That's schedule/remote work info. Could be under Schedule? The instruction says include Schedule section only if posting actually states them. It does mention remote work flexibility, which is schedule/location. We could include Schedule with that content. - Also "Why You" maybe could be "About the role"? But we already have responsibilities. Could combine "Why You" as a brief intro maybe under About the role? But we need to avoid filler. "Why You" is a motivational paragraph: "We are looking for someone who can design a data platform and then help build it..." That's more about role expectations, could be part of About the role or Responsibilities. But we already have responsibilities detailed. Might be okay to include as a short paragraph under About the role. Thus sections:

About the role

with content from "Why Pythian" and "Why You"? Actually "Why Pythian" is company overview, not role. Might be better as a separate section like "About Pythian" but not in allowed headings. However we could still use About the role for role description, and maybe include company overview as part of About the role? The instruction says use those headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings; we could also use other headings? Probably safer to stick to those. So we need to map content to those headings. Thus: - About the role: could include "Why Pythian" (company context) and "Why You" (role motivation). Might be okay. - Responsibilities: "What You Will Be Doing". - Requirements: "What We Need From You". - Skills: "What Sets You Apart From Other Applicants". - Benefits: "What You Will Receive". - Pay: "The Pay Range For This Role Is ...". - Schedule: remote work flexibility note. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from those sections. We need to use

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

  for prose. Thus we need to identify lists within each section. Let's extract content. **Why Pythian** paragraph: multiple sentences about company. We'll put as

  . **Why You**: paragraph about role and invitation. We'll put as

  . **What You Will Be Doing**: bullet list? It's a series of sentences each starting with a verb. Could treat as list items. We'll make

  • each line. List: - Own the end to end architecture: ingestion, lakehouse and warehouse layers, transformation, modeling, and delivery to reporting and analytics tools. - Build it. Write and deploy pipelines, Spark and SQL transformations, and data models, and review the code the rest of the team writes. - Design lakehouse architectures on Databricks or Fabric, including medallion layering, Delta table design, and the semantic layer that sits on top. - Make the platform call and defend it. Databricks, Fabric, or a mix, based on the client's workloads, existing licensing, skills, and cost profile. - Set up governance and access control using Unity Catalog, Purview, or the equivalent, and apply it consistently rather than bolting it on at the end. - Design and build ingestion from a wide range of sources: databases, SaaS applications, APIs, files, and legacy systems that were never meant to be integrated. **What We Need From You**: list of requirements. We'll make
    • . List: - Eight or more years in data engineering, with at least three years owning architecture and design decisions. - Proven hands on delivery. You should be able to point at platforms you designed and also built. - Deep hands on experience with Databricks or Microsoft Fabric, and working knowledge of the other. Comfortable explaining where each one fits and where it does not. - Strong Spark and SQL. Solid Python or an equivalent language used in production data work. - Experience with Delta Lake, medallion architecture, and lakehouse patterns in production, not just in a demo. - Power BI, including how the semantic model is built and where it should live. - Solid dimensional and semantic modeling skills. You should have opinions about where business logic belongs and be able to explain why. - Working knowledge of data governance: classification, lineage, cataloging, and access control. - CI/CD, version control, and testing practices applied to data work, not just to application code. **What Sets You Apart From Other Applicants**: list. - Azure Government or GCC High delivery experience. - Unity Catalog or Purview implementation experience. - Azure Data Factory, Synapse, or Azure SQL background. - Consulting or client facing delivery experience. - Experience in a regulated environment with real compliance constraints. - Databricks or Microsoft certifications. **What You Will Receive**: benefits list. - Love your career: Competitive total rewards package. Blog during work hours; take a day off and volunteer for your favorite charity. - Love your work/life balance: Flexibly work remotely from your home, there’s no daily travel requirement to an office! All you need is a stable internet connection. - Love your coworkers: Collaborate with some of the best and brightest in the industry! - Love your development: Hone your skills or learn new ones with our substantial training allowance; participate in professional development days, attend training, become certified, whatever you like! - Love your workspace: We give you all the equipment you need to work from home including a laptop with your choice of OS, and an annual budget to personalize your work environment! - Love yourself: Pythian cares about the health and well-being of our team. You will have an annual wellness budget to make yourself a priority (use it on gym memberships, massages, fitness and more). Additionally, you will receive a generous amount of paid vacation and sick days, as well as a day off to volunteer for your favorite charity. Note: Some of these contain multiple sentences; we could keep as
    • with inner

      ? But instruction: use

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

        for prose. So each list item can be plain text; if there are multiple sentences inside, still okay as text. **Pay**: The Pay Range For This Role Is 160,000 - 200,000 USD per year (USA). We'll put as

        under

        Pay

        . **Schedule**: remote work flexibility note already in benefits; but we could still have a Schedule section with that note. However we already used that note in benefits; but we could still include schedule section with same content? Might duplicate. Better to put schedule info under Schedule heading, and maybe remove from benefits? But benefits already includes that line; we could keep it there and also have schedule? Might duplicate. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep that info somewhere. If we put it under Schedule, we still need to keep it somewhere else if also in benefits. But we could decide to not duplicate: we could move that sentence from benefits to schedule, and keep other benefit items. However the benefits list includes that sentence as part of "Love your work/life balance". If we remove it, we lose that benefit detail. But we could keep it in benefits and also have schedule section with same content? That would duplicate. The instruction says preserve ALL substantive information; duplication is not prohibited but might be considered redundant. Better to keep it only once. Since schedule section is about schedule, we can put that sentence there, and adjust benefits list to exclude that sentence (maybe rephrase the benefit item to not include that). But we must preserve all substantive information; we can keep the sentence under Schedule and still keep the benefit item but maybe rephrase to not include that sentence? That would lose the detail about remote work flexibility. However we could keep the benefit item but change it to exclude the remote work sentence, and put that sentence under Schedule. That would preserve the info (still present) but not duplicate. Let's do that. Thus benefits list items: - Love your career: Competitive total rewards package. Blog during work hours; take a day off and volunteer for your favorite charity. - Love your coworkers: Collaborate with some of the best and brightest in the industry! - Love your development: Hone your skills or learn new ones with our substantial training allowance; participate in professional development days, attend training, become certified, whatever you like! - Love your workspace: We give you all the equipment you need to work from home including a laptop with your choice of OS, and an annual budget to personalize your work environment! - Love yourself: Pythian cares about the health and well-being of our team. You will have an annual wellness budget to make yourself a priority (use it on gym memberships, massages, fitness and more). Additionally, you will receive a generous amount of paid vacation and sick days, as well as a day off to volunteer for your favorite charity. Now schedule section:

        Schedule

        with

        Love your work/life balance: Flexibly work remotely from your home, there’s no daily travel requirement to an office! All you need is a stable internet connection.

        Now About the role: combine Why Pythian and Why You paragraphs. We'll put two

        under About the role. Now ensure we don't include boilerplate like "Hiring Disclaimer", "AI Disclaimer", etc. Remove those. Now produce HTML fragment. Let's craft.

        About the role

        Why Pyth