# Senior Software Engineer- Rust / C++ at Thomson Reuters

Thomson Reuters is hiring a Senior Software Engineer- Rust / C++ for a remote role open to applicants in United States. It pays $95k-$176k a year and Level rates it Little AI ●○○○; you can [apply on Level](https://jobsbylevel.com/go/208d4317-b797-4387-ac9b-41f5175db247?utm_medium=ai-agent).

AI Level 1, AI centrality 29 out of 100. Remote (United States of America, Eagan, Minnesota).

## Details

- Company: [Thomson Reuters](https://jobsbylevel.com/companies/thomson-reuters)
- AI level: AI Level 1 (score 29 out of 100)
- Location: Remote (United States of America, Eagan, Minnesota)
- Salary: $95k-$176k
- Posted: October 16, 2026
- Apply: https://jobsbylevel.com/go/208d4317-b797-4387-ac9b-41f5175db247?utm_medium=ai-agent

## Prepare for this job

The job page lists 5 likely interview questions for this offer, with a CV checklist: https://jobsbylevel.com/jobs/senior-software-engineer-rust-c-at-thomson-reuters-212eb6

## Description

Job Description: Thomson Reuters is hiring Senior Software Engineers to build the core of the document-processing platform behind our AI products. The platform turns very large volumes of documents, millions of pages a day, into clean, structured output through a queue-driven pipeline. It powers flagship products like Westlaw and CoCounsel and serves internal product teams across the company. The work is mostly Rust in DU Core, with regular work in the C#/.NET services (DU Apps) that sit in front of it. As a Senior Software Engineer II, you’ll lead high-impact projects across Core and Apps, shape how the platform evolves, and set the technical bar for the team. Key Responsibilities: Turn asks into requirements. Take requirements from product owners and consuming teams, and propose your own improvements. Turn them into clear functional and technical requirements: the problem, who is asking, how much traffic it affects, acceptance criteria, non-goals, and how we’ll know it worked Design with explicit trade-offs. Write design docs and ADRs that include all the options considered and why the chosen solution won out. Cover cost, latency, quality, failure modes, operability and security, not just the happy path. Define the architecture. Shape how our services are designed, deployed and run on Azure, and decide where the boundaries between services belong. Find and fix bottlenecks. Use production metrics, profiling, latency distributions and traffic mix to find where the pipeline is slow or wasteful, and to set timeouts, limits, concurrency and rollout plans. Back decisions with benchmarks and load tests, and be clear about what the results do and don’t show. Build and run the processing pipeline end to end. It’s a queue-driven pipeline that handles millions of pages per day. That means autoscaling, rate limiting, retries and failover across third-party vendors, very large inputs, and streaming with bounded memory while minimizing latency and maximizing throughput. Work across Core and Apps. You’ll likely spend most of your time in the core backend Rust services, but be willing to pivot to C#/.NET to support the customer-facing services that sit in front of them. Evolve contracts safely. Change message schemas, API surfaces and feature flags across services, and often across repos, in one coordinated change. Internal product teams depend on our output, so keep changes additive and backward compatible, ship with a rollout and rollback plan that covers every side, and return errors that consumers can act on. Keep a strong engineering mindset. Prefer simple designs over convoluted ones, deliver in small reviewable steps, test at the right layers, and leave code better than you found it. Work agentically. Write specs and plans that coding agents can carry out, break work into reviewable pieces, and check agent output with tests and evidence. Evaluate AI tools for specific use cases. You own the correctness every line you merge, whoever or whatever wrote it. Improve how humans and agents work here. Evolve our agent instructions, skills and review automation so they capture what the team knows, and measure whether they help. Write code, docs and PRs clear enough that a new teammate and an AI agent can both understand the intent, constraints and invariants. Own it in production. Instrument services so you can see how they behave, take part in the on-call rotation and incident response, write blameless postmortems, and turn what you learn into lasting fixes. Lead high-impact work. Own the design and rollout of large projects from requirements through production, break them into pieces the team can deliver, and keep the vision for where they’re headed. Raise the team’s bar. Mentor engineers and set the standard in code and design review. Influence direction. Translate business needs into technical solutions, explain hard trade-offs to technical and non-technical audiences, and shape product and platform decisions with consuming teams and

The description is cut here. Read the full offer: https://jobsbylevel.com/jobs/senior-software-engineer-rust-c-at-thomson-reuters-212eb6

Source: https://jobsbylevel.com/jobs/senior-software-engineer-rust-c-at-thomson-reuters-212eb6

## Cite this page

Level. https://jobsbylevel.com/jobs/senior-software-engineer-rust-c-at-thomson-reuters-212eb6.

Get job alerts: https://jobsbylevel.com/newsletter