Senior Software Engineer, AI

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. We must not repeat job title. Must not include Job ID etc. Must not include boilerplate like EEO, legal, scam warning, application instructions. Must preserve all substantive info. We need to parse the posting. Let's extract sections: - About The Role: paragraph describing building AI-driven systems etc. That's content. - Responsibilities: The bullet points under "About The Role" maybe? Actually the posting has "About The Role" then bullet list: Build and ship AI-driven systems..., Explore and apply emerging AI practices..., Provide technical depth and collaboration..., Ensure quality, security, and operational excellence..., Partner across disciplines... Those are responsibilities. - About You: includes qualifications, requirements, skills. We need to separate into Requirements, Qualifications, Skills maybe. The posting lists: Bachelor's degree..., 5+ years..., Proven track record..., Strong proficiency in Java/Spring Boot..., hands-on experience with modern front-end frameworks..., experience building production RESTful APIs..., solid understanding of web security..., Strong proficiency in Python..., experience with AI/ML frameworks..., Hands-on experience with AWS..., Strong collaboration skills..., Experience on teams building AI-driven systems..., Strong knowledge of vector databases..., Track record contributing to AI product launches..., exposure to AI governance..., publications, patents, or speaking experience... We can treat these as Requirements (education, years experience) and Qualifications (technical proficiencies) and Skills (soft skills). But we need to decide based on content. Better: Use sections: About the role (already), Responsibilities (the bullet list under About The Role), Requirements (education + years experience + core experience), Qualifications (technical proficiencies: Java/Spring Boot, front-end, APIs, security, Python, AI/ML frameworks, AWS, Docker/K8s/Terraform, vector DBs, etc.), Skills (collaboration, communication, ability to work independently, etc.) Benefits (the "What’s in it For You?" section includes hybrid work model, flexibility, career development, benefits, culture, social impact, making real-world impact, plus detailed benefits list). Pay: includes base compensation range $110,000 - $204,200 USD, mention annual bonus eligibility. Schedule: not explicitly mentioned; there is hybrid work model, flexibility, work from anywhere up to 8 weeks per year. That could be schedule info. The posting does not give explicit schedule like full-time, but we can infer flexible hybrid. However rule: never create Schedule section unless posting actually states them. It does mention flexible hybrid working environment, work from anywhere up to 8 weeks per year. That's schedule-related. So we can include Schedule section with that info. We must not include boilerplate like EEO, equal opportunity, scam warning, legal, etc. Also must not include "About Us" maybe? That's substantive but not a required heading; we could include as part of About the role? But we have About the role already. "About Us" is separate but could be considered company description; not required heading but we could include as a paragraph maybe under a generic section? The instruction: Use headings for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says prefer a few substantive sections over many thin ones. We could combine About Us into About the role or maybe omit if not needed. But we must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the About Us content somewhere. Could we put it under a heading like "About the company"? Not allowed headings list only those. But we could embed it as a paragraph under "About the role" maybe? That would be mixing. Better to add a section "About the company" but not allowed. However instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we must fit all content under those headings. We can put company description under "About the role" maybe as a preamble. Or we could add a paragraph under "Benefits" or "Pay"? Not appropriate. We could create a section "About the role" that includes both role description and company overview. That seems acceptable: "About the role" heading can contain description of role and also company context. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have About the role heading and then include paragraphs about role and company. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to extract content for each. Let's gather: About the role: combine the introductory paragraph before "About The Role" and maybe the "About Us" paragraph. Intro: "Are you passionate about building AI-driven software that transforms how professionals work? Join our fast-moving, forward-thinking group that is creating AI-driven software for professionals through our investigative platform, CLEAR (Consolidated Lead Evaluation and Reporting), which empowers users to search and analyze billions of public and proprietary records from a unified interface. We invest deeply in AI technologies and explore emerging fields with the backing of Thomson Reuters, a global leader. As a Senior Software Engineer, AI, you will play a hands-on role in full-stack web development, focusing on AI solutions, agents, and RAG, as well as traditional application layers such as gateways, APIs, and user interfaces—building intelligent systems that power the next generation of expert solutions across legal, tax, risk, and compliance domains." Then after that there is "About The Role" heading and bullet list of responsibilities. We'll treat that as Responsibilities section. Then after responsibilities, there is "About You" heading with qualifications etc. Then after that, "What’s in it For You?" heading with benefits etc. Then after that, "About Us" heading with company description. Then after that, "As a global business..." EEO etc (boilerplate) which we must remove. Also there is "Thomson Reuters complies with local laws that require upfront disclosure of the expected pay range for a position. The base compensation range varies across locations. For any eligible US locations, unless otherwise noted, the base compensation range for this role is $110,000 USD - $204,200 USD. Base pay is positioned within the range based on several factors including an individual’s knowledge, skills and experience with consideration given to internal equity. Base pay is one part of a comprehensive Total Reward program which also includes flexible and supportive benefits and other wellbeing programs. This role may also be eligible for an Annual Bonus based on a combination of enterprise and individual performance." That's Pay section. Schedule: Not explicit but we have hybrid work model, flexibility, work from anywhere up to 8 weeks per year. That's under What’s in it For You? Actually the "What’s in it For You?" includes Hybrid Work Model, Flexibility & Work-Life Balance, Career Development and Growth, Industry Competitive Benefits, Culture, Social Impact, Making a Real-World Impact, then detailed benefits. So schedule info is there: Hybrid Work Model: flexible hybrid working environment, work from anywhere for up to 8 weeks per year. We'll extract that for Schedule. Now we need to avoid boilerplate like "Flex My Way is a set of supportive workplace policies..." etc. That's part of benefits? It's about flexibility. We'll keep as part of Benefits or Schedule? It's about flexibility and work-life balance; could be Benefits. But we already have Schedule for hybrid model. We'll keep flexibility details under Benefits maybe. We must not include duplicated lines. Ensure we preserve all substantive info. Let's craft each section. Section About the role (

About the role

): include the intro paragraph and maybe also the company description from About Us? Let's include company description there as well to preserve it. The About Us paragraph: "Thomson Reuters informs the way forward by bringing together the trusted content and technology that people and organizations need to make the right decisions. We serve professionals across legal, tax, accounting, compliance, government, and media. Our products combine highly specialized software and insights to empower professionals with the data, intelligence, and solutions needed to make informed decisions, and to help institutions in their pursuit of justice, truth, and transparency. Reuters, part of Thomson Reuters, is a world leading provider of trusted journalism and news. We are powered by the talents of 26,000 employees across more than 70 countries, where everyone has a chance to contribute and grow professionally in flexible work environments. At a time when objectivity, accuracy, fairness, and transparency are under attack, we consider it our duty to pursue them." We can include that as a paragraph after the intro. Now Responsibilities (

Responsibilities

): list the bullet points under About The Role: - Build and ship AI-driven systems — Contribute to the design and implementation of enterprise-scale AI systems, including multi-component pipelines, retrieval-augmented generation (RAG) architectures, and autonomous AI agents with multi-step reasoning; develop full-stack features from AI orchestration and RAG through API gateways, microservices, and modern web UIs, in partnership with tech leads and architects. - Explore and apply emerging AI practices — Evaluate and help adopt new AI techniques; contribute to proof-of-concept work and technical feasibility for AI-driven features; stay current with AI research and apply practical insights to implementation; optionally participate in internal tech talks or community learning. - Provide technical depth and collaboration — Participate in architecture and design discussions; translate business requirements into clear technical approaches alongside your team; mentor and support other engineers; follow and help improve MLOps and LLMOps practices for the AI model lifecycle. - Ensure quality, security, and operational excellence — Implement testing, monitoring, and observability for AI systems; follow ethical AI, security, and regulatory requirements; support governance for AI model lifecycle management in production. - Partner across disciplines — Work closely with AI researchers, engineering leadership, design, and product to turn AI capabilities into market-leading applications; optimize performance for latency, cost, and user experience; bring strong technical judgment to roadmap and feature discussions. We need to put each as

inside

. Now Requirements (

Requirements

): education and years experience and core experience. From About You: "Bachelor's degree in Computer Science, Engineering, or equivalent experience, and 5+ years of software engineering experience with at least 2 years hands-on building production AI/ML or GenAI features (RAG, LLMs, agents, or similar)—as a software engineer, not primarily as a data scientist or ML researcher." Also "Proven track record delivering software with AI expertise, including experience across the lifecycle: solution discovery, architecture, tooling, evaluation, deployment, operations, and metrics." That could be considered requirement as well. We'll include both. Now Qualifications (

Qualifications

): technical proficiencies. List: - Strong proficiency in Java/Spring Boot for backend services and APIs; hands-on experience with modern front-end frameworks (React, Angular, or Vue.js) and full-stack web application development; experience building production RESTful APIs, microservices, and API gateways; solid understanding of web security, authentication/authorization, and API design. - Strong proficiency in Python and practical experience with AI/ML frameworks (e.g., PyTorch, TensorFlow, JAX); solid understanding of ML principles, evaluation methodologies, and distributed systems; experience with MLOps/LLMOps and shipping AI capabilities to production. - Hands-on experience with AWS and orchestration tools (Docker, Kubernetes, Terraform); ability to integrate AI models into production systems via APIs, data pipelines, and cloud-native architectures. - Strong knowledge of vector databases, embeddings, semantic search, and information retrieval; domain familiarity with legal, tax, accounting, or regulated