Staff Data Engineer - Data Platform

We need to output HTML fragment with sections: headings

for sections present: About the role, Responsibilities (What You’ll Do), Requirements (What You Bring), Preferred Qualifications maybe as Skills? Could be separate sections: Requirements, Preferred Qualifications, Benefits, Pay, Schedule. The posting includes benefits list under "What We Offer You". So we need Benefits section. No explicit Pay or Schedule, so we should not create those sections. Also we need to include any metadata like Job ID? Not present. So we will produce sections: About the role (maybe from "About The Role" paragraph), Responsibilities (What You’ll Do), Requirements (What You Bring), Preferred Qualifications (Preferred Qualifications), Benefits (What We Offer You). Also maybe "Engineering Leadership" and "Why Join TrendAI?" could be considered part of About? But we should only include sections with real content. Could include "Engineering Leadership" as a section? It's more about role expectations. Could be part of Responsibilities? But we can keep as separate section maybe "Engineering Leadership". However instructions: Prefer few substantive sections over many thin ones. Might combine. But we have clear sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Benefits. Also maybe "What Success Looks Like" could be part of Responsibilities? But it's descriptive of success. Could be its own section but maybe thin. I'd include as part of Responsibilities or separate "Success Metrics". But to keep few sections, maybe incorporate into Responsibilities. However the instruction: "include a section ONLY when the posting has real, specific content for it". So we can include sections for each distinct heading present in the posting: About The Role, What You’ll Do, What You Bring, Preferred Qualifications, What Success Looks Like, Engineering Leadership, Why Join TrendAI?, What We Offer You. That's many sections but each has content. However they said prefer few substantive sections over many thin ones. Some sections like Engineering Leadership and Why Join TrendAI? are somewhat generic but still specific. Could combine Engineering Leadership into About the role or Responsibilities. Why Join TrendAI? could be part of Benefits? Not exactly. Might be better to keep as separate sections but maybe it's okay. However they said "Prefer a few substantive sections over many thin ones." So we should aim to reduce number. Let's decide to have sections: About the role, Responsibilities, Requirements, Preferred Qualifications, Benefits. And incorporate other info into these sections. We need to preserve all substantive information; not invent or summarize away detail. So we must include all details from those sections, but we can embed them under appropriate headings. Thus:

About the role

: include paragraph from "About The Role" plus maybe "Engineering Leadership" and "Why Join TrendAI?"? But those are separate. Could add a paragraph after about role describing leadership and why join. But that might be summarizing? We need to preserve details, not omit. So we need to include those details somewhere. If we put them under About the role, we are not omitting, just placing under that heading. That's acceptable as long as we keep the content. Similarly, "What Success Looks Like" could go under Responsibilities or a separate section but we can put under Responsibilities as it's about outcomes. Thus we will have sections: - About the role (includes the introductory paragraph about TrendAI, the role description, plus Engineering Leadership and Why Join TrendAI? maybe) - Responsibilities (What You’ll Do + What Success Looks Like) - Requirements (What You Bring) - Preferred Qualifications (Preferred Qualifications) - Benefits (What We Offer You) We must not repeat job title as heading. Not include Job ID etc. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list, we need to convert each bullet into
• . The responsibilities are a list of bullet points starting with "Design and build..." etc. We'll wrap in
  . Similarly requirements list: each bullet after "What You Bring" is a list of bullet points. We'll wrap. Preferred qualifications list similarly. Benefits list: after "What We Offer You" there is a list of benefits: Comprehensive medical..., Life insurance..., etc. We'll wrap. We need to use

  for prose paragraphs. We must not include any boilerplate like EEO etc. At the end there is EEO statement; we must remove. We must not include navigation, cookie, legal, etc. Now produce HTML fragment. Let's extract content. About the role paragraph: "TrendAI™, the global AI security leader and enterprise business unit of Trend Micro, empowers organizations with full AI visibility and consolidated security that inspires confidence, drives innovation, and eliminates risk. At TrendAI™, we’re always seeking exceptional talent; people who want to collaborate with the best and push boundaries together. Here, your work goes beyond building a career. You will help protect what matters and play a vital role in shaping a safer, more trustworthy AI-powered future. AI Fearlessly. About The Role We are looking for a Staff Data Engineer – Data Platform to help design and build the next generation of the Vision One Data Platform. This is a highly technical, hands-on role focused on creating a modern data foundation that enables Vision One engineering teams to discover, govern, access, transform, and analyze data across the platform. You will work at the intersection of distributed databases, data engineering, data governance, semantic discovery, and self-service analytics. A key part of the role is enabling dbt as a self-service data transformation and modeling capability across Vision One OLTP databases, while building the underlying architecture, governance, and data movement infrastructure required to do this reliably at scale. You will work closely with platform, product, security, and data engineering teams to establish common data standards and infrastructure that can be reused across Vision One." We might need to remove duplicated "About The Role" heading? We'll just use prose. Engineering Leadership paragraph: "Engineering Leadership As a Staff Engineer, you will be expected to operate beyond the boundaries of a single team. You will shape architecture, establish technical standards, mentor engineers, drive cross-team adoption, and solve ambiguous problems that span multiple products and systems. You should be comfortable going deep into implementation details while simultaneously thinking about the long-term architecture of a large-scale, multi-product security data platform." Why Join TrendAI? paragraph: "Why Join TrendAI? TrendAI is a leader in AI security. We not only delivered the first open-weight, cybersecurity-focused large language model, but also the industry's first security companion agent evaluated directly by customers. Trend Vision One integrates endpoint, cloud, network, email, identity, AI application, and data security into a single, unified platform. In this role, you will help define how a security-critical product is built — including how AI shapes the development process itself. You will partner with engineering leaders applying AI to that process, working in an environment where the bar on systems thinking, critical review, and security instinct has gone up, not down." We can combine these after the About the role paragraph. Now Responsibilities: "What You’ll Do Design and build the Vision One Data Platform, including data ingestion, replication, transformation, governance, discovery, and serving capabilities.Build scalable data pipelines and change-data-capture (CDC) architectures using technologies such as Datastream and similar streaming/replication technologies.Enable self-service dbt across Vision One OLTP data sources, providing product teams with governed capabilities to transform, model, test, document, and expose their data without requiring the central data platform team to build every pipeline.Establish patterns for safely extracting and replicating data from OLTP and distributed SQL databases into analytical and downstream data systems.Design architectures around distributed SQL technologies such as YugabyteDB, CockroachDB, or similar platforms.Work with technologies such as Databricks and modern analytical processing engines to support large-scale data processing and analytics.Build a comprehensive data catalog and metadata foundation that enables teams and AI agents to understand what data exists, where it comes from, what it means, and how it can be used.Develop semantic data discovery capabilities that allow engineers, analysts, applications, and AI agents to discover relevant data based on business meaning rather than only database/schema names.Establish data governance standards covering ownership, lineage, schemas, quality, access control, retention, and lifecycle management.Develop reusable data platform primitives and APIs that product teams can consume as self-service capabilities.Build automated mechanisms for data quality, schema evolution, lineage, observability, and freshness monitoring.Design for evolving product schemas and ensure the platform can accommodate continuous changes without creating excessive duplication or operational overhead.Partner with security and platform engineering teams to establish appropriate fine-grained data access controls across databases, schemas, tables, and data products.Help establish the source-of-truth architecture for Vision One data while minimizing unnecessary data duplication.Provide technical leadership and architectural guidance to other data engineers and product engineering teams.Drive engineering standards around reliability, scalability, performance, cost efficiency, and operational excellence." We need to split into list items. Each sentence seems a bullet. We'll make each as

  • . Now What Success Looks Like: "What Success Looks Like In this role, you will help establish a Data Platform where: Vision One data can be discovered through a common semantic layer, rather than requiring teams to understand every underlying database and schema.Product teams can use dbt as a governed self-service capability across their OLTP data.Data lineage, ownership, quality, and access policies are built into the platform rather than managed manually.Data can move reliably from distributed OLTP systems into analytical and downstream systems through standardized CDC and streaming patterns.Product teams can consume platform capabilities without repeatedly building their own ingestion, transformation, governance, and discovery infrastructure.The platform provides a trusted source of truth while minimizing unnecessary copies of data.The resulting data foundation can support not only traditional analytics and applications, but also AI and agentic experiences across Vision One." We can incorporate as list items under Responsibilities or separate. Let's add as additional
  • items under Responsibilities. Now Requirements: "What You Bring 8+ years of experience in data engineering, distributed systems, backend engineering, or a related field.Strong experience designing and building large-scale data platforms and data pipelines.Deep understanding of OLTP and OLAP architectures and the tradeoffs between them.Hands-on experience with CDC, data replication, and streaming architectures.Strong SQL expertise and experience working with relational databases at scale.Experience with distributed SQL databases, such as YugabyteDB, CockroachDB, Spanner, or similar technologies.Experience building data transformation workflows using dbt or similar data modeling frameworks.Experience with modern analytical/data platforms such as Databricks, Spark, Trino, Snowflake, BigQuery, or equivalent.Strong understanding of data governance concepts including metadata, lineage, data quality, ownership, access control, and data catalogs.Experience designing systems that support self-service data consumption and transformation.Strong software engineering fundamentals, including API design, testing, CI/CD, observability, and production operations.Ability to work across organizational boundaries and influence architecture and engineering standards without relying solely on formal authority." We'll make each as
  • . Preferred Qualifications: list similarly. Now Benefits: list after "What We Offer You". The list: "Comprehensive medical, dental and vision insuranceLife insuranceShort & Long Term DisabilityPre-partum, maternity, parental and medical leaveMental Health Wellness ProgramAdoption AssistanceWellness IncentivePet Insurance401(k) with company matchPaid Time Off14 Annual HolidaysTuition AssistanceEmployee Resource Groups We offer competitive compensation with bonus opportunity tied to company performance, along with room to enhance your skills through ongoing learning and broad technological opportunities. Achieving work-life balance is a priority, complemented by team activities, fostering an environment rooted in equity, inclusion, and collaboration, that is reflected in both our culture and our work. At Trend Micro, we embrace change, empower people, and encourage innovation in a connected world. Our diversity and multicultural workforce are key contributing factors to our success across the globe." We need to separate benefits list items. The benefits appear as a run-on string without punctuation. We need to parse: "Comprehensive medical, dental and vision insuranceLife insuranceShort & Long Term DisabilityPre-partum, maternity, parental and medical leaveMental Health Wellness ProgramAdoption AssistanceWellness IncentivePet Insurance401(k) with company matchPaid Time Off1