Senior Software Engineer — Customer Files Orchestration

USA018 Thomson Reuters Holdings Inc.

Where
Hybrid in United States of America, Eagan, Minnesota
Pay
$95K a year

Posted 10 days ago· Checked live at USA018 Thomson Reuters Holdings Inc. 4 days ago

Live.Open on the employer's own site.

See how you score for this job

One sentence and your resume. We score it against what USA018 Thomson Reuters Holdings Inc. asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on USA018 Thomson Reuters Holdings Inc.'s own hiring page 4 days ago.
What is the job?
Job Description Job description
What does it pay?
$95K a year, as the posting states.
Our verdict
Live. Open on the employer's own site.

What the job is

Job Description

Job description

Senior Software Engineer — Customer Files Orchestration

CoCounsel Legal is seeking a Senior Software Engineer to help build and operate the Customer Files Orchestration Service – the system that makes a customer's own documents usable by CoCounsel Legal's agents.

Required Qualifications

  • Bachelor's or master's degree – Computer Science, Engineering, or a related field, or equivalent practical experience.
  • 5+ years building production software – With a track record of owning significant components in systems that real customers depend on.
  • Extensive AWS and production Python experience – This is a Python service on AWS, and you should be able to move confidently through both the code and the infrastructure.
  • Concurrency in Python, and a healthy respect for how treacherous it is – You understand the GIL and what it does and does not protect you from, you have written and debugged production asyncio code, and you have been bitten by the classics: fire-and-forget tasks that swallow their own failures, blocking work smuggled onto the event loop, semaphores and pools that quietly cap throughput far below the worker count, and background tasks racing the state they are meant to be updating.
  • Kubernetes in production – Our workers and APIs run as pods with event-driven autoscaling (KEDA). You have tuned scalers and resource requests, and you have debugged the real failure modes.
  • Large-scale orchestration or data pipeline experience – Systems that move large volumes of work through multiple stages across service boundaries, where retries, partial failure, and long-running steps are the normal case rather than the exception.
  • Consistency models – You can explain where eventual consistency is safe and where it silently corrupts a user-visible outcome, and you have debugged the difference in production.
  • Delivery guarantees – At-least-once versus exactly-once, why idempotency is usually the real answer, and what it costs to get it wrong.
  • Queues, fair queuing, rate limiting, and backpressure – Practical, hands-on understanding, including multi-tenant fairness and noisy-neighbor isolation.
  • API design instincts – Versioned contracts, clear ownership, backward compatibility, and treating an internal API as something other teams build on.
  • Real operational ownership – You have carried the pager for something you built, debugged it under pressure, and come out with a fix rather than a workaround.
  • Strong engineering fundamentals – Testing, code review, observability, CI/CD, and infrastructure-as-code as habits rather than obligations.
  • Clear communication – You can write a design down, defend it, change your mind when the evidence says so, and explain the result to someone who does not share your context.

Preferred Qualifications

  • Documents and document management systems – Extraction, OCR, format handling, very large files, and the integration surface of third-party DMS platforms.
  • Event-driven architectures and streaming – Kafka/MSK or similar, managed queueing such as SQS, and event-driven autoscaling.
  • Durable workflow engines – Temporal, Step Functions, or similar, with a clear view of when they are worth adopting.
  • Retrieval, embedding, or indexing pipelines – Supporting LLM or agentic applications.
  • Prior exposure to the legal industry – A real bonus, and a meaningful head start on understanding what our customers actually need from their documents.
  • Team topologies – This organization uses its vocabulary natively (stream-aligned teams, platform teams, and the boundaries between them) to reason about how services and teams are shaped.