Senior Staff Software Engineer - AI Governance

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". Must include Pay and Schedule only if posting actually states them. The posting includes Salary Range $193,050—$257,400 USD. That's pay. So we need a Pay section with that info. Schedule? The posting mentions "We are embracing an office-first culture, encouraging three days a week in office for most roles". That's schedule info (office-first, three days a week). So we can include Schedule section with that. Benefits: there is a Benefits paragraph describing comprehensive healthcare coverage, flexible PTO, equity RSUs, annual performance bonus opportunities, retirement account support, 14+ weeks of paid parental leave, career development opportunities, company-paid privacy certification exam fees, etc. So we include Benefits section. We need sections: About the role (maybe mission/challenge), Responsibilities (Your Mission bullet points), Requirements/Qualifications/Skills (maybe combine). The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include based on content. We need to avoid thin sections. Probably include About the role (mission/challenge), Responsibilities (Your Mission bullet list), Requirements (Experience includes bullet list), Skills (maybe technical skills list), Benefits, Pay, Schedule. We must not repeat job title as heading. So no heading for Senior Staff Software Engineer. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The posting includes a recruitment fraud warning, data subject request, etc. Those are boilerplate; we should remove them. Also the "Our Commitment to You" and EEO statement maybe considered boilerplate; but it's substantive? It's about equal employment opportunities; likely considered EEO boilerplate, should be removed. Also "Resources" section with links to YouTube, Instagram maybe not needed? It's not boilerplate but maybe not essential; but it's not a section heading we have; we could include as a paragraph? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Resources" section is not exactly those; but it's maybe okay to keep? However it's not under a heading we have; we could include as a paragraph under About the role? Might be considered navigation? Safer to omit it as it's not core job description. Also "Your Data" section about privacy rights is legal boilerplate; remove. Also "Recruitment fraud warning" is boilerplate; remove. Also "Our Commitment to You" maybe considered fluff but could be kept? It's somewhat motivational; but might be considered boilerplate? Not sure. Safer to keep only core sections: About the role (mission/challenge), Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. We need to extract details. Let's parse the posting: Mission/challenge: "Strength in Trust OneTrust’s mission is to enable innovation through the responsible use of data and AI. We believe that ensuring data is trusted shouldn’t slow teams down—it should accelerate what’s possible. This led us to develop the first technology platform for responsible data use in 2016. Today, with AI representing the latest and most impactful expansion of data yet, OneTrust is once again redefining what responsible innovation looks like. OneTrust, the AI‑Ready Governance Platform™, unifies regulatory intelligence, automation, and connected governance workflows so businesses can continue to move at the speed of AI while ensuring good governance to prevent data misuse at scale. Trusted by thousands of organizations worldwide, OneTrust is shaping the future where trusted data becomes a transformative force for business and society. The Challenge As a Senior Staff Software Engineer, you will serve as a technical leader for OneTrust’s AI Governance (AIG) platform, driving the design, scalability, and reliability of systems that enable enterprises to deploy and govern AI and LLM-powered applications responsibly. You will deeply understand how customers build, deploy, and operate AI systems, and translate those needs into secure, compliant, and observable platform capabilities." That's about the role. Responsibilities: "Your Mission Development Lead the design and development of Java/Python microservices and shared libraries integrating with AI platforms for OneTrust’s AI Governance product.Design, build, and test cloud-native applications deployed on Microsoft Azure using Core Java, REST, and the Spring ecosystem.Lead the architecture and development of reusable AIG reporting and dashboard capabilities that integrate governance data from SQL databases and analytical platforms with runtime observability signals.Design reusable semantic-layer and metric-abstraction capabilities, including dataset contracts, metric definitions, query APIs, pre-aggregation, caching, filtering, time-period selection, and drill-down workflows.Lead event-driven integrations using Kafka and Apache Flink to consume normalized observability events and produce dashboard-ready datasets and derived metrics.Integrate with the AI Observability platform through well-defined APIs and data contracts for runtime metrics, logs, traces, alerts, policy decisions, and evidence.Own technical design for critical systems, ensuring scalability, security, and reliability.Partner with frontend engineers to build reusable dashboard shells, visualization components, filters, data tables, and entity drill-down experiences.Maintain strong automated unit and integration test coverage in line with team standards." Also collaboration: "Collaboration Work closely with UX, Product Managers and/or Product Owners, as well as other developers to contribute to planning and grooming sessions and drive team discussions on system architecture and component design. Partner with Product, UX, and Customer Success to understand customer AI use cases and governance needs.Lead architecture discussions and technical planning.Drive alignment across teams on platform design and priorities.Contribute to sprint planning and delivery." Support: "Support Reduce defects by identifying and addressing issues early in the development lifecycle.Ensure critical and high-priority CII’s are delivered per SLA. Promote early defect detection through strong design and testing.Improve system monitoring, resilience, and operational maturity." Code Review: "Code Review Set standards for clean, secure, and maintainable code.Conduct thorough reviews for distributed and AI-enabled systems.Guide engineers on testing, automation, and AI system validation." Lead: "Lead Help build high-performing teams by mentoring the team on new technical skills. Influence technical strategy and long-term platform direction.Build a culture of ownership, learning, and engineering excellence. Lead multi-quarter technical roadmaps across teams and make practical build-versus-reuse decisions." We could combine all these under Responsibilities. Requirements/Qualifications/Skills: The "You Are" and "Your Experience Includes" and "Extra Awesome Experience". We need to capture all. You Are: "A senior technical leader with strong system design and hands-on execution skills, who understands how enterprises use AI and LLMs in real-world workflows and can translate those needs into scalable, secure, and compliant platform solutions." Your Experience Includes: list of bullet-like sentences: - Bachelor’s or master’s degree in computer science, Engineering, or a related technical or business field. - 12+ years of professional software engineering and development experience. - Strong expertise in Java/J2EE, Spring, Python, design patterns, microservices, and cloud-native distributed systems. - Proven experience leading reusable platform, reporting, analytics, or data products that support multiple teams or dashboards. - Hands-on experience with Cube.js, semantic layers, metric layers, or comparable metric/query abstraction systems. - Hands-on experience with Apache Flink for real-time stream processing, windowed aggregation, event correlation, or derived-metric generation. - Experience designing event-driven services and data-ingestion pipelines using Kafka, including integrations with SQL databases, analytical platforms, APIs, and observability systems. - Strong experience with data modeling, dataset contracts, pre-aggregation, read models, caching, query optimization, and data-quality controls. - Experience building secure, multi-tenant SaaS platforms with tenant isolation, authentication, authorization, and secure service-to-service communication. - Experience working with AI/LLM platforms and production AI workloads, including model orchestration, RAG, evaluation, guardrails, or runtime observability. - Good understanding of REST, OAuth, JSON, SQL, NoSQL databases, and Python or Bash scripting. - Experience with CI/CD, automated testing, production monitoring, incident response, and Agile development practices. - Experience with Azure, AWS, Google Cloud, and open-source technologies. - Ability to lead multi-quarter roadmaps, make practical build-versus-reuse decisions, and align engineering, product, UX, security, platform, and observability teams. Extra Awesome Experience: list: - Experience with OpenTelemetry, VictoriaMetrics, Prometheus/MetricsQL, Grafana Loki/LogQL, Grafana Tempo/TraceQL, Alertmanager, or Open Policy Agent. - Experience integrating with Databricks, Delta Lake, Power BI, or other analytical data platforms. - Experience building configurable dashboard systems, data visualization frameworks, or design-system-based frontend platforms. - Experience with AI governance, model risk management, compliance, GRC, audit evidence, or regulatory reporting. - Experience with graph data models, dependency maps, entity resolution, or supply-chain analysis. - Experience designing SDK telemetry, model gateways, runtime instrumentation, or post-market monitoring. - Proficiency in Kubernetes, including cluster deployment, scaling, and management is highly desirable. - Background in enterprise, regulated, or security-focused environments. We could put Requirements (education, years experience) and Skills (technical). But we can also combine into one Requirements section with bullet list. However instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose to include multiple of those if they have substantive content. To avoid thin sections, we could combine Requirements and Qualifications into one "Requirements" section, and Skills into another "Skills" section if we have enough content. But we have lots of technical skills; we could put them under Skills. Requirements could be education + years experience. Qualifications maybe similar; but we can skip Qualifications if redundant. Thus sections: - About the role (mission/challenge) - Responsibilities (Your Mission, Collaboration, Support, Code Review, Lead) - Requirements (education, 12+ years) - Skills (technical expertise list) - Benefits - Pay - Schedule We must not include filler like "commensurate with experience". Not present. Now we need to output HTML fragment only, no /. Use

for headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must include all details from the sections we keep. That means we need to include each bullet point from the responsibilities, each requirement, each skill, each benefit, pay range, schedule. We must not omit any detail. That's a lot but doable. We need to format as HTML. Let's extract each piece. About the role prose: combine the mission/challenge paragraph(s). We'll put as

  . Responsibilities: we have multiple bullet-like sentences. We'll make a

  with each sentence as
  • . Need to ensure we capture all. Let's list responsibilities sentences exactly as in text: From "Your Mission Development Lead the design and development of Java/Python microservices and shared libraries integrating with AI platforms for OneTrust’s AI Governance product." But the text seems missing punctuation; we need to keep as is. Let's copy the block: "Your Mission Development Lead the