{"id":1967071,"url":"https://alion.io/job/thomson-reuters-jreq203081-staff-software-engineer-i-open","title":"JREQ203081 Staff Software Engineer I (Open)","company":{"id":1951,"name":"Thomson Reuters","domain":"thomsonreuters.com","url":"https://alion.io/company/thomson-reuters","size_band":"5000+","is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":"Workday","truth_index":{"grade":"A","score":87,"open_postings":97,"ghost_share":0.031,"stale_share":0.34,"repost_share":0.165,"time_to_fill_p50_days":25,"computed_at":"2026-10-28T05:59:10Z"}},"role":"Backend","role_family":"Backend","seniority":"staff","employment_type":"full_time","work_mode":"hybrid","remote_scope":null,"remote_scope_basis":null,"remote_working_hours":null,"hiring_geo_confidence":"structured","locations":["Frisco, United States","Toronto, Canada","United States"],"countries":["US","CA"],"hiring_countries":[],"hiring_countries_total":0,"salary":{"min":118400,"max":219800,"currency":"USD","period":"year","gross":null,"usd_annual":219800},"salary_estimate":null,"experience_years_min":8,"visa_sponsorship":false,"relocation_package":false,"has_equity":true,"technologies":[{"name":"AI Agents","optional":false},{"name":"Claude","optional":false},{"name":"FastAPI","optional":false},{"name":"Hybrid Search","optional":false},{"name":"LLM","optional":false},{"name":"Model Context Protocol","optional":false},{"name":"OpenAI Agents SDK","optional":false},{"name":"Python","optional":false},{"name":"SLI/SLO/SLA","optional":false},{"name":"Vespa","optional":false},{"name":"CI/CD","optional":true},{"name":"ElasticSearch","optional":true},{"name":"OpenSearch","optional":true},{"name":"Prompt Engineering","optional":true},{"name":"Terraform","optional":true}],"status":"live","first_seen_at":"2026-10-06T17:46:11Z","employer_posted_date":"2026-10-06","last_verified_at":"2026-10-28T19:14:15Z","board_verified":true,"closed_at":null,"days_open":22,"trust":{"level":"ok","repost_count":null,"flags":[],"days_open":22},"description":"Job Description\nStaff Software Engineer - Content Tools\nContent Tools\nCoCounsel Agent Context\nOverview of the Role\nThe CoCounsel Agent Context team is seeking a Staff Software Engineer to set the technical direction for Content Tools - the purpose-built APIs that give AI agents precise, governed access to Thomson Reuters’ proprietary legal content across various international jurisdictions. Content Tools are the bridge between TR’s authoritative content and the AI products, such as CoCounsel Legal, that depend on them, and they carry high stakes - every result an agent returns must be accurate and grounded in TR’s authoritative content. This Staff Engineer defines how those tools are designed, evaluated, and operated, and sets the patterns that every engineer - on this team and on contributing partner teams - builds against.\nThis is a high-leverage role at the intersection of API design, information retrieval, and agentic systems. Staff Engineers here define what to build and why, not just how: they solve ambiguous problems that span multiple teams and systems, and their work is felt well beyond their own code. The team’s operating principles are non-negotiable. You own your work end-to-end, from the first commit to the production dashboard. You ship to production constantly, and you treat delivery friction as an engineering problem to solve, not a fact of life. You use AI-assisted development as a primary tool, with the majority of code written with AI assistance. And you practice verified spec-driven development: acceptance criteria and an evaluation suite define a tool’s behavior before the implementation exists and gate every change in CI. Because AI writes most of the code, what you truly own is the spec and the eval that verifies it - the eval is the spec, and you are accountable for the outcome, not the lines. The successful candidate brings platform thinking, deep API and evaluation instincts, enterprise-grade security awareness, and a product-minded approach to developer experience - treating each tool’s contract as a product in its own right.\nKey Responsibilities\nIn this position, you will focus on:\nContent Tool Architecture & API Ownership\nSet the technical direction for the Content Tools catalog: define the design patterns, schema templates, and contribution standards every tool is built against, and the guidance on when to create a new tool versus extend an existing one - resolving problems of broad scope with little precedent to guide solutions\nDrive an API-first, contract-driven approach: every tool ships with a versioned contract, schema, and ownership metadata that makes it discoverable and self-service for consuming teams and agent developers, who should never need to ask you how to use your tool\nArchitect the retrieval and search layer behind the catalog - relevance and ranking quality on the team’s Vespa based search platform, and the trade-offs between structured and semantic retrieval - partnering with TR Labs on the underlying search algorithms\nDefine the agent invocation model for the catalog: clean tool boundaries exposed over MCP (Model Context Protocol), result payloads designed for token economy, and latency budgets that hold across multi-hop retrieval chains, giving agent orchestrators predictable, well-documented interfaces to TR and third-party content\nBuild and own the shared development and testing infrastructure - common libraries, scaffolding generators, mock services, and local environments, built on the team’s Python, FastAPI, and Claude Agent SDK stack - that makes it easy for any team member to build a Content Tool correctly the first time\nVerified Spec-Driven Development & Evaluation\nOwn verified spec-driven development as a team-wide standard: define how acceptance criteria and evaluation datasets are written before implementation to specify a tool’s behavior, IR metrics (precision, recall, NDCG), and CI gates that verify every change and set the bar every engineer’s eval suite follows\nTreat evaluation as foundational infrastructure the team is still maturing: assess current coverage across tool families, close the highest-risk gaps first, and prevent teams from redundantly reinventing evaluation capability\nDefine how offline grading pipelines and online signals combine into a continuous, trustworthy quality picture for every tool in production\nReliability & Operations\nTake full operational responsibility for what you and your area own - you built it, you own it, you run it: own the on-call model and SLO targets for your services, and build the automation that reduces operational toil for the whole team\nLead incident response for high-severity issues, write thorough post-mortems, and drive systematic fixes that prevent recurrence\nBuild the observability that makes reliability visible - including trace-level instrumentation for agentic retrieval paths, where standard request/response logging cannot explain a non-deterministic failure\nOwn performance and cost strategy for the tool layer: capacity planning, caching, and rate limiting that keep the platform reliable and economical as tenants, content volumes, and query traffic grow, with fast, safe delivery treated as a first-class engineering goal rather than a trade-off against reliability\nTechnical Leadership & Governance\nFunction as the technical authority other engineers and partner teams turn to for Content Tools API, evaluation, and architecture decisions; author cross-team Architecture Decision Records for cross-cutting choices and contribute to the code- and design-review policy the team follows\nMultiply the team: develop Senior engineers through architecture guidance, design pairing, and constructive review, with measurable growth in the people you mentor - your impact is the patterns you set and the engineers you grow\nBuild durable relationships with the teams that depend on you - CoCounsel Engineering, TR Labs, and product owners - , feeding structured requirements back into the roadmap, and reducing time-to-value for new adopters\nEstablish team-wide AI-assisted development patterns and model them visibly; capture decisions in writing where the team can find them, so work is legible to async readers\nMake the hard calls: say no to unnecessary complexity, advise senior leadership on complex , and champion ethical AI and responsible, secure deployment across the team’s work\nYou’re an ideal fit if you have:\n\nRequired Qualifications\nBachelor’s or Master’s degree in Computer Science, Engineering, or a related field\n8+ years of software engineering experience with demonstrated progression to staff-level or equivalent technical leadership - including ownership of a functional area and leadership of significant cross-team initiatives\nMastery of Python and strong fundamentals across API design, testing strategy (unit, integration, load and evaluation), system design, and security architecture\nTrack record of designing and operating API-first systems consumed by multiple teams, with a product mindset toward developer experience - including versioning, backward compatibility, and clear contracts\nWorking fluency with information-retrieval concepts (precision/recall trade-offs, hybrid search, ranking, citation networks) sufficient to make sound architectural decisions and partner credibly with research scientists\nDemonstrated experience designing or owning evaluation frameworks for retrieval or LLM systems: dataset design, IR metrics, CI-gated eval suites, and tracing and observability for non-deterministic workflows\nProven reliability ownership at the system level: designing on-call models, setting SLOs, leading incident response, and a clear philosophy that shipping frequently and operating reliably are complementary, not in tension\nDemonstrated security and access-control practice:\nFluency with AI-assisted development tools; you write the majority of your code with AI assistance, produce higher-quality work because of it, and establish the patterns that help the team do the same\nStrong communication: you explain complex retrieval and architecture concepts to technical and non-technical audiences and build alignment across engineering, product, and science\nPreferred Qualifications\nExperience building tools or APIs for agentic AI systems, including tool protocols such as MCP (Model Context Protocol) or similar\nBackground in legal technology, knowledge management, or other high-stakes information domains where source attribution, accuracy, and entitlement enforcement are critical\nHands-on experience operating search and retrieval engines (OpenSearch, Vespa, Elasticsearch) - cluster sizing, index lifecycle, and the trade-offs between semantic and structured search\nExperience operationalizing tooling for LLM-powered workflows: tool-description design, prompt engineering, and agent invocation patterns\nExperience establishing contribution governance for a platform built on by multiple teams - review workflows, registry/namespace management, and deprecation and migration policies\nFamiliarity with content licensing and policy-based entitlements in multi-tenant environments\nWorking understanding of infrastructure-as-code (Terraform) and API gateways (such as Apigee) - enough to operate, secure, and reason about the services you own\nWhat Success Looks Like\nIn the first 90 days:\nDevelop a comprehensive mental model of the Content Tools architecture - tool inventory, CI/CD pipelines, evaluation infrastructure, and the legacy dependencies and migration paths in flight - and identify the top architectural risks and debt items across the team’s systems by shipping multiple tools\nEstablish working relationships with CoCounsel Engineering, Product, and TR Labs, understanding each stakeholder’s priorities and integration pain points firsthand\nEstablish your AI-assisted development workflow and model it visibly for the team; take on-call ownership for your functional area\nShip at least one high-impact improvement that demonstrates judgement and taste, not just velocity, and assess eval coverage across tool families to pinpoint the most urgent gaps\nIn the first year:\nDrive the architecture for a major Content Tools initiative - a significant catalog expansion, the evaluation framework, or a comparable platform milestone - from design through production, establishing the patterns and templates other engineers build against\nEstablish Content Tools as a well-documented, measurably reliable internal platform: verified spec-driven development as the default, SLO coverage across core services, automated eval gates in CI, on-call runbooks, and a track record of fast, high-quality incident resolution\nMultiply the team: at least two Senior engineers have grown measurably through your architecture guidance, design pairing, and mentorship\nBe recognized across the organization as the Content Tools architecture authority - shaping team standards, influencing cross-team architecture, and advising leadership on complex\nThis posting is for proactive recruitment purposes and may be used to fill current openings or future vacancies within our organization.\nWhat’s in it For You?\nHybrid Work Model: We’ve adopted a flexible hybrid working environment for our office-based roles while delivering a seamless experience that is digitally and physically connected.\nFlexibility & Work-Life Balance: Flex My Way is a set of supportive workplace policies designed to help manage personal and professional responsibilities, whether caring for family, giving back to the community, or finding time to refresh and reset. This builds upon our flexible work arrangements, including work from anywhere for up to 8 weeks per year, empowering employees to achieve a better work-life balance.\nCareer Development and Growth: By fostering a culture of continuous learning and skill development, we prepare our talent to tackle tomorrow’s challenges and deliver real-world solutions. Our Grow My Way programming and skills-first approach ensures you have the...","description_format":"text","description_chars":18221,"description_truncated":true,"requirements":{"experience_years_min":8,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":{"level":"bachelor","optional":false},"security_clearance":false,"languages":[]},"benefits":["401k plan","Continuous learning","Equity","Flexible schedule","Hybrid work","Life insurance","Parental leave"],"hiring_locations":[{"name":"United States","iso":"US","kind":"country"}],"hiring_excludes":[],"relocation_offered":false,"industries":["Artificial Intelligence","Cybersecurity","Financial Services","Professional Services"],"lifecycle":[{"event":"open","at":"2026-10-06T17:46:11Z"}],"visa":[{"country":"US","licensed_sponsor":true,"evidence":"H-1B filings in 12 months: 51 · green card filings: 1","filings_12m":51,"filings_prev_12m":46,"green_card_filings_12m":1,"median_offered_wage_usd":133846,"route":null,"cap_exempt":false,"checked_at":"2026-10-15T11:24:14+00:00","sources":["US Department of Labor: LCA disclosure data (H-1B, H-1B1, E-3)","US Department of Labor: PERM disclosure data (green cards)"],"filings_for_role_12m":32}],"liveness":{"score":62,"band":"ok","label":"Likely open","p_open":1,"p_active":0.828,"p_room":0.75,"age_days":21,"expected_fill_days":25,"reasons":["conf:2","velocity","win:late","comp:brand"],"computed_at":"2026-10-28T05:59:10Z"},"pay":{"stated_usd_annual":219800,"is_top_pay":false},"html_url":"https://alion.io/job/thomson-reuters-jreq203081-staff-software-engineer-i-open","json_url":"https://alion.io/job/thomson-reuters-jreq203081-staff-software-engineer-i-open.json","meta":{"generated_at":"2026-10-28T21:14:46Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","about":"Alion is a live layer of people, companies and AI agents: who they are, whether they are real and active right now, what they do and how to work with them, readable by people and by agents and paid per call.","catalog":"https://alion.io/catalog.json","usage":{"tier":"crawler_verified","counted_by":"address","units_charged":1,"used_today":29267,"day_limit":null,"remaining_today":null,"minute_limit":300,"resets_at":"2026-10-29T00:00:00Z"}},"offers":[{"id":"company.slices","title":"One company in depth, by slice","status":"live","price":{"credits":0.02,"usd":0.002,"plus_per_slice":{"credits":0.05,"usd":0.005}},"unit":"per company, plus each slice with data","note":"the employer in depth","call":{"mcp_tool":"get_company","arguments":{"id":1951},"rest":"https://alion.io/mcp/rest/get_company?id=1951"},"human":"https://alion.io/catalog?offer=company.slices&for=job%2Fthomson-reuters-jreq203081-staff-software-engineer-i-open"},{"id":"market.stats","title":"A market slice: pay, demand and time to fill","status":"live","price":{"credits":1,"usd":0.1},"unit":"per slice","note":"pay, demand and time to fill for this role and place","call":{"mcp_tool":"market_stats"},"human":"https://alion.io/catalog?offer=market.stats&for=job%2Fthomson-reuters-jreq203081-staff-software-engineer-i-open"},{"id":"job.search","title":"Open jobs by role, technology, place, pay and visa","status":"live","price":{"credits":0.02,"usd":0.002},"unit":"per posting in a list","note":"similar open postings","call":{"mcp_tool":"search_jobs"},"human":"https://alion.io/catalog?offer=job.search&for=job%2Fthomson-reuters-jreq203081-staff-software-engineer-i-open"},{"id":"company.verify","title":"Is this company real and active right now","status":"pilot","price":null,"unit":"per company","request":{"url":"https://alion.io/catalog/request","method":"POST","body":"{\"offer\": \"company.verify\", \"for\": \"job/thomson-reuters-jreq203081-staff-software-engineer-i-open\", \"note\": \"what you need it for\"}"},"human":"https://alion.io/catalog?offer=company.verify&for=job%2Fthomson-reuters-jreq203081-staff-software-engineer-i-open"}],"agent":{"mcp":"https://alion.io/mcp/jobs","mcp_open":"https://alion.io/mcp/open","next":[{"tool":"get_job","arguments":{"id":1967071}},{"tool":"search_jobs","arguments":{"company":"thomsonreuters.com","detail":"compact"}},{"tool":"match_people","arguments":{"job_id":1967071},"note":"people open to offers who fit this vacancy"}],"note":"The same data through MCP tools: https://alion.io/mcp/open needs no sign-in (compact searches, postings, people); https://alion.io/mcp with an Alion account has everything. Docs: https://alion.io/developers"}}