**Job Description**As a Software Engineer on the Tabular Analysis team, you will help build tools that let legal professionals put questions to large collections of documents and get back answers they can trace to the source. It is live in CoCounsel today, and it is among the first products running Thomson Reuters’ own in-house model in production. You will work across the full stack, from the backend services that do the heavy processing to the interface lawyers use to read and refine results.This role is aimed at someone early in their career who wants to move quickly. You will get real ownership sooner than is typical, you will be expected to use AI tooling to multiply what one engineer can deliver, and you will work directly alongside the senior engineers who designed these systems and are ready to teach them. If you are looking for a role where your ceiling is set by how fast you learn rather than by how long you have been doing this, that is the role we are describing.**Key Responsibilities**In this opportunity as a Software Engineer, you will:* **Build and ship end to end:** Take a feature from a written requirement through design, implementation, code review and production. You will operate with a moderate level of guidance and own straightforward projects outright.* **Work genuinely full-stack:** Develop across the frontend, the backend and the data layer, with attention to performance and security, rather than specializing in one from day one. Expect to work directly with database schemas and query performance.* **Use AI as a force multiplier:** Apply AI coding and testing tooling to your own work, and help build AI capabilities into the product itself. Translate business requirements into solutions that use AI where it is the right answer,



and do not where it is not.* **Learn the systems deliberately:** Build real working knowledge of the core services behind the product, some of which currently sit with a small number of senior engineers, so that knowledge is shared across the team rather than concentrated in it.* **Diagnose and fix:** Read unfamiliar code, run root cause analysis, troubleshoot production behavior, and act on issues raised by automated code quality inspection.* **Raise the quality bar:** Contribute to automated testing strategy and to continuous integration and delivery pipelines, treating test coverage as part of a feature rather than as a follow-up.* **Collaborate across functions:** Participate actively in design discussions, agile ceremonies and cross-team work with Product, and build direct working relationships with the people who use what you build. The team spans several time zones, so a good deal of this happens in writing.* **Help others as you grow:** Share what you learn, support colleagues on problems you have already solved, and contribute to a team culture where learning out loud is normal.**What makes this hard*** **The correctness bar is unusual.** Our users are lawyers. A citation that points at the wrong document is not a cosmetic bug, it undermines the entire answer.* **The scale is real.** Working across large document collections surfaces problems that simply do not exist at small scale,



and you will meet them.* **We move quickly, so not everything is settled before work starts.** You will sometimes begin building while a question is still open, which means asking early and occasionally revisiting a piece once the answer lands.* **Some of what you need to learn lives in one or two people's heads.** Getting it out of there is part of the job, not an obstacle to it.**Required Qualifications**You are an adecuado fit for the Software Engineer role if your experience includes:* Professional software engineering experience delivering production code in a modern language, with a solid foundation you are actively building on.* Real strength in either frontend or backend development, and genuine appetite for becoming strong at the other.* Experience integrating and consuming APIs in a cloud environment.* Practical use of AI developer tooling in your own workflow, and the judgment to tell when it is helping and when it is not.* **Evidence that you learn fast.** Be ready to point to something specific you taught yourself and then shipped, and to explain how you went about it. This is the quality we care about most and the one we will probe hardest.**Preferred Qualifications**None of the following is required, but any of it would help you get up to speed faster: exposure to containerization, infrastructure-as-code, or continuous integration and delivery pipelines; experience building or integrating large language model features, such as prompt design, evaluation, or retrieval over large document sets; work on data-intensive systems like processing pipelines or query performance; or exposure to the legal domain or other specialist professional users.
#J-18808-Ljbffr

📌 Software Engineer (Ciudad de México)
🏢 Reuters
📍 Ciudad de México