Senior Software Engineer, Data Product - SF Only

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, no invention. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove sections like "About The Team", "Learn About TRM Speed In This Position", "About TRM's Engineering Levels", "Individual pay is determined...". But we need to extract relevant content: The posting includes description of role, impact, responsibilities, requirements, qualifications, skills, benefits, pay, schedule. We need to parse the text. Let's extract: - About the role: The first paragraph: "Build a Safer World. TRM Labs provides AI-powered intelligence solutions that help public and private sector agencies investigate and disrupt crime. TRM's platforms enable investigators to trace illicit activity, build cases, and construct operating pictures of threat networks. Leading agencies and businesses worldwide rely on TRM to make the world safer and more secure. The Data Product team collaborates with an experienced group of data scientists, engineers, and product managers to build highly scalable features that power TRM's products and services. As a Senior Data Engineer on the Data Product team, you will be responsible for designing and building mission-critical data services. These features analyze and provide insights into blockchain transaction activity at petabyte scale, and ultimately work to build a safer financial system for billions of people." That's about the role. - Responsibilities: The Impact You’ll Have Here bullet list: "Build highly scalable features that integrate with dozens of blockchains. Design and architect intricate data models for optimal storage and retrieval to support sub-second latency for querying blockchain data. Collaborate across departments, partnering with data scientists, backend engineers, and product managers to design and implement novel data models that enhance TRM’s products. Collaborate across departments, partnering with data scientists, backend engineers, and product managers to design and implement novel data models that enhance TRM’s products. You’ll work closely with product managers, data scientists, and customer-facing teams to deeply understand user needs and translate them into scalable data solutions.”Our best engineers are also exceptional communicators. They write clear design docs, proactively share tradeoffs, and build alignment across disciplines.Bonus: Experience with LLMs or AI-powered workflows (e.g., prompt engineering, internal tooling, semantic search)." We need to deduplicate repeated lines. Also "Collaborate across departments..." appears twice; we keep one. Also "Our best engineers..." etc. - Requirements: "What We’re Looking For Bachelor's degree (or equivalent) in Computer Science or a related field.A proven track record, with 5+ years of hands-on experience in architecting scalable API development, distributed system architecture, guiding projects from initial ideation through to successful production deployment.Exceptional programming skills in Python, as well as adeptness in SQL or SparkSQL.Versatility that spans the entire spectrum of data engineering in one or more of the following areas:In-depth experience with data stores such as BigQuery and Postgres.You’ve owned 0–1 systems: building pipelines, data platforms, or ML/BI workflows from scratch—not just maintaining legacy.”You simplify complexity. You’re skilled at writing and communicating technical decisions clearly to both technical and non-technical stakeholders.You’re cost-conscious: you design for performance, scale, and efficiency.You’ve mentored engineers or analysts and enjoy leveling up those around youIn-depth experience with data stores such as BigQuery and Postgres.Proficiency in data pipeline and workflow orchestration tools like Airflow and DBT.Expertise in data processing technologies and streaming workflows including Dataflow, Spark, Kafka, and Flink.Competence in deploying and monitoring infrastructure within public cloud platforms, utilizing tools such as Docker, Terraform, Kubernetes, and Datadog.Proven ability in loading, querying, and transforming extensive datasets" We need to parse into bullet list. - Qualifications: Might be same as Requirements? The posting lumps them. Could treat "What We’re Looking For" as Requirements/Qualifications. Might separate: Qualifications could be education + experience. But we can combine into one section maybe "Requirements". However instructions: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. We have content for About the role, Responsibilities, Requirements (education, experience), Qualifications (maybe same), Skills (technical skills), Benefits (maybe equity plan, etc.), Pay (salary range), Schedule (work location requirement: at least 3 days per week in SF office). Also maybe "About The Team" etc but we should not include unless specific content; but we can drop as not requested headings. We need to avoid duplication and filler. Let's extract each. **About the role**: as above. **Responsibilities**: list items: - Build highly scalable features that integrate with dozens of blockchains. - Design and architect intricate data models for optimal storage and retrieval to support sub-second latency for querying blockchain data. - Collaborate across departments, partnering with data scientists, backend engineers, and product managers to design and implement novel data models that enhance TRM’s products. - Work closely with product managers, data scientists, and customer-facing teams to deeply understand user needs and translate them into scalable data solutions. - Write clear design docs, proactively share tradeoffs, and build alignment across disciplines. - Bonus: Experience with LLMs or AI-powered workflows (e.g., prompt engineering, internal tooling, semantic search). We could keep bonus as separate bullet. **Requirements**: Education + experience: - Bachelor's degree (or equivalent) in Computer Science or a related field. - 5+ years of hands-on experience in architecting scalable API development, distributed system architecture, guiding projects from initial ideation through to successful production deployment. - Exceptional programming skills in Python, as well as adeptness in SQL or SparkSQL. - Versatility that spans the entire spectrum of data engineering in one or more of the following areas: - In-depth experience with data stores such as BigQuery and Postgres. - You’ve owned 0–1 systems: building pipelines, data platforms, or ML/BI workflows from scratch—not just maintaining legacy. - You simplify complexity. You’re skilled at writing and communicating technical decisions clearly to both technical and non-technical stakeholders. - You’re cost-conscious: you design for performance, scale, and efficiency. - You’ve mentored engineers or analysts and enjoy leveling up those around you. - In-depth experience with data stores such as BigQuery and Postgres. (duplicate) - Proficiency in data pipeline and workflow orchestration tools like Airflow and DBT. - Expertise in data processing technologies and streaming workflows including Dataflow, Spark, Kafka, and Flink. - Competence in deploying and monitoring infrastructure within public cloud platforms, utilizing tools such as Docker, Terraform, Kubernetes, and Datadog. - Proven ability in loading, querying, and transforming extensive datasets. We need to deduplicate duplicate "In-depth experience with data stores such as BigQuery and Postgres." appears twice; keep one. Also "Versatility that spans the entire spectrum of data engineering in one or more of the following areas:" then list items; we can treat each as bullet. **Qualifications**: Might be similar to Requirements; but we could treat "What We’re Looking For" as Qualifications. However we already used Requirements for education/experience. Could separate: Qualifications could be the "versatility" list? But that seems overlapping. Perhaps we can combine Requirements and Qualifications into one section? But instructions say we can include sections only when posting has real specific content. It does have both "What We’re Looking For" (which includes education, experience, versatility) and later "What We’re Looking For" again? Actually the text repeats some content. There's also "About The Team" etc. There's no separate "Qualifications" heading in the posting. So we may not have distinct Qualifications content beyond what we already captured. Could still create a Qualifications section with the same content? Might be considered duplication. Better to omit Qualifications if no distinct content. But we need to decide. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section called "Requirements". But they ask to use headings for those specific names if we include them. If we don't have distinct content for Qualifications, we should not include it. Similarly Skills: we have technical skills list (Python, SQL, SparkSQL, BigQuery, Postgres, Airflow, DBT, Dataflow, Spark, Kafka, Flink, Docker, Terraform, Kubernetes, Datadog). Could extract as Skills. Benefits: The posting mentions: "Additionally, this role may be eligible to participate in TRM’s equity plan." Also maybe other benefits not mentioned. So we can include Benefits: equity plan eligibility. Pay: Salary range: $190,000 - $220,000 base salary. Also mention that compensation details reflect US base salary only. Schedule: Work Location Requirement: based in San Francisco office, expected to work from office at least three (3) days per week. We should not include "Individual pay is determined by skills, qualifications, experience, and location." That's generic; we can omit as filler? It's not specific; but it's part of posting. However it's somewhat generic; but we could include as part of Pay section? It says "Individual pay is determined by skills, qualifications, experience, and location." That's generic but still substantive? Might be considered filler but it's actual statement. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This statement is not placeholder; it's a statement about determination. Could include but maybe we can keep Pay section with salary range and note that compensation is based on skills, qualifications, experience, location. We'll include Pay: base salary range $190k-$220k, plus equity eligibility, and note that individual pay determined by skills, qualifications, experience, location. Schedule: work location requirement: San Francisco office, at least 3 days per week. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We must not include or . Just the fragment. Let's craft. Section About the role:

  About the role

  then

  with the prose. Responsibilities:

  Responsibilities

  then
  with items. Requirements:

  Requirements

  then
  with items. Skills:

  Skills

  then
  with technical skills. Benefits:

  Benefits

  then
  maybe with equity plan. Pay:

  Pay

  then

  with salary range and note. Schedule:

  Schedule

  then

  with work location. Check for duplication: Ensure we didn't repeat same bullet. Let's list responsibilities bullets clearly: - Build highly scalable features that integrate with dozens of blockchains. - Design and architect intricate data models for optimal storage and retrieval to support sub-second latency for querying blockchain data. - Collaborate across departments, partnering with data scientists, backend engineers, and product managers to design and implement novel data models that enhance TRM’s products. - Work closely with product managers, data scientists, and customer-facing teams to deeply understand user needs and translate them into scalable data solutions. - Write clear design docs, proactively share tradeoffs, and build alignment across disciplines. - Bonus: Experience with LLMs or AI-powered workflows (e.g., prompt engineering, internal tooling, semantic search). Now Requirements bullets: We need to capture education, experience, versatility items. Let's list: - Bachelor's degree (or equivalent) in Computer Science or a