Skip to content
Search jobs inside your AI agent. Claude, ChatGPT, Claude Code, Codex, Gemini, Cursor and Grok
Connect

HelloCounsel.ai

Software Engineer

Posted 112 views

Description

You will own one workstream in a personal injury case end-to-end- for example, insurance claims - and turn it into an agent that is reliable enough to run fully on its own. That agent has to work across every case-management system a firm might use (Clio, Filevine, Litify, MyCase, and the long tail), onboard new firms with their own custom processes in days, and talk and operate with the judgment of a great paralegal. One person, one workstream, full ownership: the agent's architecture, its integrations, its evals, and how it sounds on the phone with an insurance adjuster.


Responsibilities:

  • Design and ship a production LLM agent that runs for weeks without human babysitting - state, memory, retries, escalation, recovery.
  • Build the integration layer that abstracts a fragmented mess of legal CMS platforms into one clean surface. If you've ever thought about what Plaid did for banks, that's the shape of this problem.
  • Make reliability a discipline: evals, transcript regression suites, edge-case hunts. 95% is measured, not vibes.
  • Obsess over how the agent talks. You'll read and listen to more transcripts than anyone else at the company, and treat the agent's voice as a product surface.
  • Make onboarding a new firm a non-event: their custom intake forms, their process quirks, their CMS, mapped in days.
  • Work directly with the customers, founders and a small team of builders. No managers, no handoffs, no tickets written by someone else.


Requirements:

  • You've shipped LLM agents in production - real users, real failures, real fixes. Not demos, not notebooks.
  • You treat agent reliability as an engineering discipline: you write evals before prompts feel done, and you've built regression testing over transcripts or traces.
  • You've normalised messy third-party systems before - APIs with bad docs, legacy platforms, per-customer configuration - and built a clean abstraction over the chaos.
  • You have product instincts. You read a transcript and flinch at the wrong sentence.
  • You'd rather fix how the agent says no than add a feature.
  • You hold yourself to a high bar without being managed to it. That's how everyone here works, and we trust each other to keep it.
  • You're in Bangalore, or happy to move. We work side by side in person, and that time together is a big part of why this team is fun.

Skills

Apply