Senior Data Platform Engineer
Thomson Reuters · New York, NY · 1 mo ago
HybridEngineering$136k/yrFull-time
We need to output only HTML fragment, no html/body tags. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job description.
First, job title is Senior Data Platform Engineer. Not to repeat as heading.
We need sections:
- About the role: description of role: "As a Senior Data Platform Engineer, you will design, build, and maintain the infrastructure that ingests, processes, stores, and serves large volumes of legal and financial document data. You will work across backend services, data pipelines, databases, and cloud infrastructure to ensure the platform remains scalable, reliable, secure, and compliant." Also maybe mention company description? But "About Us" is separate. The "About the role" likely includes the first paragraph after job description? The posting includes "Job Description Noetica is an AI-native legal technology company..." That's about company. Then "As a Senior Data Platform Engineer, you will design..." That's role. So we can put that in About the role.
- Responsibilities: list of key responsibilities bullet points: "Design and optimize pipelines that ingest, transform, and distribute large-scale document data. Build and maintain reliable, high-performance backend services for document storage, retrieval, and processing. Implement data governance, privacy controls, audit trails, and regulatory compliance requirements, including GDPR. Lead database migrations and improve schema design, query performance, and data scalability. Partner with machine learning and AI teams to support model training and inference at scale. Mentor engineers on platform architecture, engineering practices, and system design."
- Requirements: maybe "Required Qualifications" section. Should we separate Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. Typically "Required Qualifications" could go under Requirements or Qualifications. Since we have both headings, we need to split content appropriately. But we must not create empty sections. We need to see if we have distinct content for Requirements vs Qualifications vs Skills.
The posting has "Required Qualifications" list: Seven or more years..., Strong experience..., Proficiency..., Strong knowledge..., Experience..., Experience...
Then "Preferred Qualifications": Experience in legal technology..., A record..., Experience..., Familiarity..., Coding in Python
Also there is "What’s in it For You?" which includes benefits etc.
Thus we can map:
- Requirements: maybe the Required Qualifications (mandatory). Could also include "Required Qualifications" as Requirements.
- Qualifications: maybe Preferred Qualifications.
- Skills: maybe we could extract specific skills like programming languages, distributed systems, etc. But we already have those in qualifications. Could create a Skills section summarizing technical skills: Python, Java, C++, Go, SQL, NoSQL, AWS/GCP/Azure, Kafka/Flink, etc. But we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to take content from the posting that corresponds to skills. The posting includes "Proficiency in at least one systems programming language, such as Python, Java, C++, or Go, and experience designing scalable APIs." "Strong knowledge of SQL and NoSQL databases, data modeling, and query optimization." "Experience with AWS, Google Cloud Platform, or Microsoft Azure and infrastructure-as-code practices." "Experience with data compliance, privacy regulations, or secure data handling." Also "Experience with real-time data processing and streaming technologies such as Kafka or Flink." "Familiarity with machine learning pipelines and feature engineering platforms." "Coding in Python" (maybe duplicate). So we could put those under Skills.
But we need to avoid duplication: If we put those under Skills, we should not also repeat them under Requirements/Qualifications. However the instruction says preserve ALL substantive information; we can reorganize but must not lose info. It's okay to move content to appropriate sections as long as we keep it.
Thus we can have:
- About the role: paragraph describing role.
- Responsibilities: ul list of responsibilities.
- Requirements: maybe list of mandatory years/experience etc. Could include "Seven or more years of software engineering experience, including at least four years focused on data platforms, backend infrastructure, or related systems." plus maybe "Strong experience with distributed systems, data warehousing, or large-scale data technologies such as Hadoop, Spark, or Snowflake." but that's also a skill. Might be better to put under Requirements the experience years and maybe the broad experience, while Skills list specific tech.
- Qualifications: Preferred Qualifications bullet list.
- Skills: list of technical skills (programming languages, databases, cloud, streaming, ML pipelines, etc.)
- Benefits: from "What’s in it For You?" includes hybrid work model, flexibility, career development, industry competitive benefits, culture, social impact, making a real-world impact, plus Thomson Reuters benefits details (health, dental, vision, disability, life insurance, 401k, vacation, mental health days, parental leave, sabbatical, optional hospital insurance, etc.) Also mention base compensation range? That's Pay.
- Pay: The base compensation range: "$136,000 USD - $253,000 USD." Also mention eligibility for annual bonus.
- Schedule: maybe hybrid work model? But schedule is about work hours? The posting mentions hybrid work model, flexibility, work from anywhere up to 8 weeks per year. That could be schedule. However we already used hybrid work model under Benefits. Could put schedule under Schedule: "Hybrid work model with flexibility to work from anywhere up to 8 weeks per year." But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine benefits and schedule? But we need to follow headings only when posting has real specific content. We have content for Benefits, Pay, maybe Schedule (hybrid work). We could include Schedule as separate section if we have specific schedule info. The posting says: "Hybrid Work Model: We’ve adopted a flexible hybrid working environment for our office-based roles while delivering a seamless experience that is digitally and physically connected." Also "Flexibility & Work-Life Balance: Flex My Way is a set of supportive workplace policies designed to help manage personal and professional responsibilities, whether caring for family, giving back to the community, or finding time to refresh and reset. This builds upon our flexible work arrangements, including work from anywhere for up to 8 weeks per year, empowering employees to achieve a better work-life balance." That's schedule/flexibility.
Thus we can have Schedule section with that content.
Benefits section: list of benefits: flexible vacation, two company-wide Mental Health Days off, access to Headspace app, retirement savings, tuition reimbursement, employee incentive programs, resources for mental, physical, and financial wellbeing, culture, social impact, etc. Also Thomson Reuters specific benefits: health, dental, vision, disability, life insurance, 401k plan with company match, vacation, sick and safe paid time off, paid holidays (including two company mental health days off), parental leave, sabbatical leave, optional hospital, accident and sickness insurance, optional life and AD&D insurance, Flexible Spending and Health Savings Accounts, fitness reimbursement, access to Employee Assistance Program, Group Legal Identity Theft Protection benefit, access to 529 Plan, commuter benefits, Adoption & Surrogacy Assistance, Tuition Reimbursement, Employee Stock Purchase Plan.
We need to preserve all substantive information. So we need to include all those.
We must not include boilerplate like EEO, accommodation, fraud warnings, etc.
Thus we need to strip those.
Now craft HTML.
We'll have:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the job description.
First, job title is Senior Data Platform Engineer. Not to repeat as heading.
We need sections:
- About the role: description of role: "As a Senior Data Platform Engineer, you will design, build, and maintain the infrastructure that ingests, processes, stores, and serves large volumes of legal and financial document data. You will work across backend services, data pipelines, databases, and cloud infrastructure to ensure the platform remains scalable, reliable, secure, and compliant." Also maybe mention company description? But "About Us" is separate. The "About the role" likely includes the first paragraph after job description? The posting includes "Job Description Noetica is an AI-native legal technology company..." That's about company. Then "As a Senior Data Platform Engineer, you will design..." That's role. So we can put that in About the role.
- Responsibilities: list of key responsibilities bullet points: "Design and optimize pipelines that ingest, transform, and distribute large-scale document data. Build and maintain reliable, high-performance backend services for document storage, retrieval, and processing. Implement data governance, privacy controls, audit trails, and regulatory compliance requirements, including GDPR. Lead database migrations and improve schema design, query performance, and data scalability. Partner with machine learning and AI teams to support model training and inference at scale. Mentor engineers on platform architecture, engineering practices, and system design."
- Requirements: maybe "Required Qualifications" section. Should we separate Requirements and Qualifications? The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what content goes where. Typically "Required Qualifications" could go under Requirements or Qualifications. Since we have both headings, we need to split content appropriately. But we must not create empty sections. We need to see if we have distinct content for Requirements vs Qualifications vs Skills.
The posting has "Required Qualifications" list: Seven or more years..., Strong experience..., Proficiency..., Strong knowledge..., Experience..., Experience...
Then "Preferred Qualifications": Experience in legal technology..., A record..., Experience..., Familiarity..., Coding in Python
Also there is "What’s in it For You?" which includes benefits etc.
Thus we can map:
- Requirements: maybe the Required Qualifications (mandatory). Could also include "Required Qualifications" as Requirements.
- Qualifications: maybe Preferred Qualifications.
- Skills: maybe we could extract specific skills like programming languages, distributed systems, etc. But we already have those in qualifications. Could create a Skills section summarizing technical skills: Python, Java, C++, Go, SQL, NoSQL, AWS/GCP/Azure, Kafka/Flink, etc. But we must not invent or summarize away detail; we must preserve ALL substantive information. If we create a Skills section, we need to take content from the posting that corresponds to skills. The posting includes "Proficiency in at least one systems programming language, such as Python, Java, C++, or Go, and experience designing scalable APIs." "Strong knowledge of SQL and NoSQL databases, data modeling, and query optimization." "Experience with AWS, Google Cloud Platform, or Microsoft Azure and infrastructure-as-code practices." "Experience with data compliance, privacy regulations, or secure data handling." Also "Experience with real-time data processing and streaming technologies such as Kafka or Flink." "Familiarity with machine learning pipelines and feature engineering platforms." "Coding in Python" (maybe duplicate). So we could put those under Skills.
But we need to avoid duplication: If we put those under Skills, we should not also repeat them under Requirements/Qualifications. However the instruction says preserve ALL substantive information; we can reorganize but must not lose info. It's okay to move content to appropriate sections as long as we keep it.
Thus we can have:
- About the role: paragraph describing role.
- Responsibilities: ul list of responsibilities.
- Requirements: maybe list of mandatory years/experience etc. Could include "Seven or more years of software engineering experience, including at least four years focused on data platforms, backend infrastructure, or related systems." plus maybe "Strong experience with distributed systems, data warehousing, or large-scale data technologies such as Hadoop, Spark, or Snowflake." but that's also a skill. Might be better to put under Requirements the experience years and maybe the broad experience, while Skills list specific tech.
- Qualifications: Preferred Qualifications bullet list.
- Skills: list of technical skills (programming languages, databases, cloud, streaming, ML pipelines, etc.)
- Benefits: from "What’s in it For You?" includes hybrid work model, flexibility, career development, industry competitive benefits, culture, social impact, making a real-world impact, plus Thomson Reuters benefits details (health, dental, vision, disability, life insurance, 401k, vacation, mental health days, parental leave, sabbatical, optional hospital insurance, etc.) Also mention base compensation range? That's Pay.
- Pay: The base compensation range: "$136,000 USD - $253,000 USD." Also mention eligibility for annual bonus.
- Schedule: maybe hybrid work model? But schedule is about work hours? The posting mentions hybrid work model, flexibility, work from anywhere up to 8 weeks per year. That could be schedule. However we already used hybrid work model under Benefits. Could put schedule under Schedule: "Hybrid work model with flexibility to work from anywhere up to 8 weeks per year." But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine benefits and schedule? But we need to follow headings only when posting has real specific content. We have content for Benefits, Pay, maybe Schedule (hybrid work). We could include Schedule as separate section if we have specific schedule info. The posting says: "Hybrid Work Model: We’ve adopted a flexible hybrid working environment for our office-based roles while delivering a seamless experience that is digitally and physically connected." Also "Flexibility & Work-Life Balance: Flex My Way is a set of supportive workplace policies designed to help manage personal and professional responsibilities, whether caring for family, giving back to the community, or finding time to refresh and reset. This builds upon our flexible work arrangements, including work from anywhere for up to 8 weeks per year, empowering employees to achieve a better work-life balance." That's schedule/flexibility.
Thus we can have Schedule section with that content.
Benefits section: list of benefits: flexible vacation, two company-wide Mental Health Days off, access to Headspace app, retirement savings, tuition reimbursement, employee incentive programs, resources for mental, physical, and financial wellbeing, culture, social impact, etc. Also Thomson Reuters specific benefits: health, dental, vision, disability, life insurance, 401k plan with company match, vacation, sick and safe paid time off, paid holidays (including two company mental health days off), parental leave, sabbatical leave, optional hospital, accident and sickness insurance, optional life and AD&D insurance, Flexible Spending and Health Savings Accounts, fitness reimbursement, access to Employee Assistance Program, Group Legal Identity Theft Protection benefit, access to 529 Plan, commuter benefits, Adoption & Surrogacy Assistance, Tuition Reimbursement, Employee Stock Purchase Plan.
We need to preserve all substantive information. So we need to include all those.
We must not include boilerplate like EEO, accommodation, fraud warnings, etc.
Thus we need to strip those.
Now craft HTML.
We'll have:
About the role
As a Senior Data Platform Engineer, you will design, build, and maintain the infrastructure that ingests, processes, stores, and serves large volumes of legal and financial document data. You will work across backend services, data pipelines, databases, and cloud infrastructure to ensure the platform remains scalable, reliable, secure, and compliant.
Responsibilities
- Design and optimize pipelines that ingest, transform, and distribute large-scale document data.
- Build and maintain reliable, high-performance backend services for document storage, retrieval, and processing.
- Implement data governance, privacy controls, audit trails, and regulatory compliance requirements, including GDPR.
- Lead database migrations and improve schema design, query performance, and data scalability.
- Partner with machine learning and AI teams to support model training and inference at scale.
- Mentor engineers on platform architecture, engineering practices, and system design.
Requirements
- Seven or more years of software engineering experience, including at least four years focused on data platforms, backend infrastructure, or related systems.
- Strong experience with distributed systems, data warehousing, or large-scale data technologies such as Hadoop, Spark, or Snowflake.
- Proficiency in at least one systems programming language, such as Python, Java, C++, or Go, and experience designing scalable APIs.
- Strong knowledge of SQL and NoSQL databases, data modeling, and query optimization.
- Experience with AWS, Google Cloud Platform, or Microsoft Azure and infrastructure-as-code practices.
- Experience with data compliance, privacy regulations, or secure data handling.
Qualifications
- Experience in legal technology, financial services, or another highly regulated industry.
- A record of leading cross-functional initiatives and mentoring engineers.
- Experience with real-time data processing and streaming technologies such as Kafka or Flink.
- Familiarity with machine learning pipelines and feature engineering platforms.
- Coding in Python.
Skills
- Systems programming languages: Python, Java, C++, Go.
- SQL and NoSQL databases, data modeling, query optimization.
- Cloud platforms: AWS, GCP, Azure; infrastructure-as-code.
- Data compliance, privacy regulations, secure data handling.
- Streaming technologies: Kafka, Flink.
- Machine learning pipelines and feature engineering.