Manager, Software Engineering — Customer Files Orchestration

We need to output HTML fragment with sections: About the role? The posting includes Overview Of The Role, Job Description, Key Responsibilities, Required Qualifications, Preferred Qualifications, What Success Looks Like (with 90 days, six months, first year), What’s in it For You? (benefits). We must use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short

  or drop it. Remove boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to preserve all substantive information. Must not invent or summarize away detail. So we need to include all details from the posting, but we can group them logically. We need to decide sections: maybe "Overview", "Responsibilities", "Qualifications", "Success Metrics", "Benefits". Use

  for each. We must not include sections like "Pay" or "Schedule" unless posting actually states them. It does not mention pay or schedule specifics, so omit. We need to include benefits: Hybrid Work Model, Flexibility & Work-Life Balance, Career Development and Growth, Industry Competitive Benefits (with details). Those are benefits. We need to include "What Success Looks Like" details (90 days, six months, first year). Could be a section "Success Expectations" with subpoints. We need to include "Key Responsibilities" (list). Also "Overview Of The Role" (prose). Also "Job Description" (maybe same as responsibilities). But we need to avoid duplication. The posting has "Overview Of The Role" then "Job Description" then "Key Responsibilities". The "Key Responsibilities" section actually says "You're an ideal fit if you have:" then lists required qualifications. Wait reading: after "Key Responsibilities" they wrote "You're an ideal fit if you have:" then list of required qualifications. Actually the posting: Key Responsibilities You're an ideal fit if you have: Required Qualifications Bachelor's or master's degree – Computer Science, Engineering, or related field. ... It seems they mislabeled. The "Key Responsibilities" heading is followed by "You're an ideal fit if you have:" which is actually qualifications. Then "Required Qualifications" list. Then "Preferred Qualifications". Then "What Success Looks Like". Then "This posting is for proactive recruitment..." then "What’s in it For You?" benefits. Thus we need to parse correctly. Let's extract sections: - Overview Of The Role: paragraph describing role. - Job Description: bullet list of duties (Service & Technical Leadership, Team Management, Strategic Delivery). Those are responsibilities. - Key Responsibilities: actually qualifications? The text after "Key Responsibilities You're an ideal fit if you have:" then list of required qualifications. So we treat that as Required Qualifications. - Required Qualifications: list of items (Bachelor's or master's degree, Direct people management experience, Large-scale enterprise orchestration systems, Extensive AWS and production Python experience, Concurrency in Python, Containerized workloads on Kubernetes, Consistency models, Delivery guarantees, Queues..., API-first instincts, Building, owning, and operating a production service end-to-end, Distributed systems and cloud fundamentals, Communication and alignment). - Preferred Qualifications: list (Documents and document management systems, Team Topologies, Event-driven architectures and streaming, Durable workflow engines, Retrieval, embedding, or indexing pipelines, Prior exposure to the legal industry). - What Success Looks Like: sub-sections: In the first 90 days, In The First Six Months, In The First Year. Each with bullet points. - What’s in it For You?: benefits list: Hybrid Work Model, Flexibility & Work-Life Balance, Career Development and Growth, Industry Competitive Benefits (with subpoints: flexible vacation, two company-wi... truncated). The text cut off: "Industry Competitive Benefits: We offer comprehensive benefit plans to include flexible vacation, two company-wi". It seems truncated; we must preserve as is, not invent. We'll include that sentence as is. We must not include boilerplate like "This posting is for proactive recruitment purposes..." maybe we can drop as it's not substantive? It's generic. Probably drop. We must not repeat job title as heading. We must not include application instructions. Now produce HTML fragment. We need to use

  for section headings. Use

  • for any list of duties/requirements/benefits, and

    for prose. Thus:

    Overview of the Role

    ... prose from Overview Of The Role ...

    Job Description

    • Service & Technical Leadership: ... (the bullet points)
    • Team Management: ...
    • Strategic Delivery: ...
    But the Job Description bullet points are long sentences; we can keep as list items. Alternatively we could keep as

    but instruction says use

    • for any list of duties/requirements/benefits. So we treat those as list. Now Required Qualifications: heading

      Required Qualifications

      then
      • each item. Preferred Qualifications similarly. Success Expectations: maybe

        Success Expectations

        then we could have subheadings? But we cannot use

        for subheadings? Only section headings use

        . Could we use

        ? Not allowed? The instruction only says use

        for section headings. It doesn't forbid other headings, but to be safe we could just use

        with bold? But we must not invent headings. Better to keep as

        with strong text? However we need to preserve structure. Could use

        In the first 90 days: ...

        etc. Benefits:

        Benefits

        then
        • each benefit item. We must not include filler like "commensurate with experience". Not present. Now we need to ensure we preserve all substantive information. Let's copy the text exactly (or close) but we can rephrase slightly? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must not omit details, but we can rephrase as long as we keep all info. Safer to keep original phrasing. Let's extract each piece. Overview Of The Role text: "Software Engineering Manager Overview Of The Role CoCounsel Legal is seeking a Software Engineering Manager to lead the team that owns the Customer Files Orchestration Service – the system that makes a customer documents usable by CoCounsel Legal's agents. Every file a customer brings to CoCounsel passes through this team: upload, storage, extraction, embedding, and indexing, orchestrated end-to-end. You make millions of customer files available to CoCounsel. Bringing a customer's content together with Thomson Reuters' world-class proprietary content and the latest frontier models – including TR's own custom large language models – is what makes our products highly differentiated and our agent experiences genuinely grounded. This team is a critical part of what makes that combination possible. It is also, unavoidably, a hard distributed systems problem. Supporting millions of files means real engineering: dedicated workers, fair queuing so one busy customer cannot starve another, durable state, idempotent processing, and honest reasoning about consistency and delivery guarantees across systems. The team owns what it builds, designing, implementing, testing, deploying, scaling, and operating the service end-to-end. This role will help take a recently formed, cross-functional group and shape it into a durable, high-performing engineering team with clear ownership, a stable operational posture, and the credibility to lead decisions about design, roadmaps, and opportunity costs within the team and across stakeholders." We need to remove the repeated "Software Engineering Manager Overview Of The Role" maybe keep as prose. We'll just start after that. Job Description bullet points: From "Job Description In this position, you will:" then list: - Service & Technical Leadership - Own customer file orchestration service end-to-end – Upload, storage, content extraction, embedding, indexing, and observability and monitoring – balancing new capability delivery against reliability. - Drive API-first execution – The file and workspace APIs this team owns serves a growing set of consumers beyond orchestration, and this team treats them as a product – clear ownership, versioned contracts, documented behavior, deliberate change management, and independent deployability – not an incidental collection of backend endpoints - Lead the team's judgment on the problems that define the domain – Consistency models (where eventual consistency is acceptable and where a strongly-consistent read is the only correct answer), delivery guarantees (at-least-once with idempotent processors versus the cost of true exactly-once), lease and heartbeat models for crash recovery, and state transitions across asynchronous service boundaries - Own the queuing and flow-control architecture – Fair queuing, rate limiting, backpressure, circuit breaking, dead-letter handling, and autoscaling. - Champion full operational ownership – The team designs, builds, tests, deploys, scales, and operates what it ships – with on-call, incident response, SLOs, and testing treated as first-class engineering work, not afterthoughts. - Partner with platforms and client applications teams to deliver a world class product – Leverage robust orchestration across other (internal and external) services to enable both human users and agents with world-class experiences. - Team Management - Build and lead the Files Orchestration engineering team – Hiring, onboarding, performance, and career development – turning a recently-formed cross-functional group into a stable team with clear, durable ownership - Develop engineers who combine distributed systems depth with real operational responsibility – Lead an engineering team who owns their work from the first line of code to the production dashboard, and who own testing/QA, deployments, and support rather than handing them off. - Translate complex orchestration and scale trade-offs to product managers and business leaders – Making the meaning of a throughput number and the risk in a deadline legible to non-engineers. - Establish operating rhythms and ways of working – Establish principled ways of working, empowering the team to own their operating rhythms: roadmap, stand-ups, demos, retros, support rotations, and beyond. - Strong technical leadership via effective negotiation and influence – Earn the trust of leaders and external teams, negotiating capacity and roadmaps to converge on technical decisions that result in world class products. - Strategic Delivery - Define and maintain engineering processes – Rigorous design, code review, testing, and instrumentation good enough to proactively identify and fix issues, provide great support and reliable service. - Establish service health benchmarks – Ingest throughput, end-to-end time-to-available, failure and retry rates, per-tenant fairness under load, and API reliability SLOs – used to drive continuous improvement rather than to decorate a dashboard. - Sequence foundational infrastructure work against product deadlines – Know when to ship the pragmatic stopgap, when to insist on the structural fix, and how to make the difference visible to leadership. - Align the roadmap with CoCounsel's priorities – Collaborate closely with product management and adjacent engineering teams to deliver high-quality capabilities and strong technical foundations. Now Required Qualifications list (after "Key Responsibilities You're an ideal fit if you have:" then list): - Bachelor's or master's degree – Computer Science, Engineering, or related field. - Direct people management experience – 8+ years of software engineering experience, including 3+ years of managing engineers. You have hired, coached, and managed performance, and you want to keep doing it. - Large-scale, enterprise orchestration systems – Demonstrated experience designing and operating them in production: pipelines that move large volumes of work through multiple stages, across service boundaries, with retries, partial failure, and long-running