Product Engineer, Tech Ops

Overview

👋 About Advocate Advocate () is transforming how Americans access government benefits. Our mission is to drive the time between need and relief down to zero. We combine proprietary AI-powered technology with expert human care and compassion to provide an unparalleled experience for claimants and to reduce administrative burdens for government partners.

We’ve proven our cutting-edge AI technology works. We are now focused on scaling the distribution of our offering and the operations that support it. This is a unique challenge that requires a combination of high-tech precision and human-centered support.

At Advocate, the Tech Ops team is the connective tissue of the organization. We sit at the intersection of technology, marketing, and operations, ensuring these functions remain synchronized as we scale. We are not an IT support desk; we are front-line builders who work alongside internal users who interact with claimants. Our mandate is twofold:

• Short-Term Agility:
  We keep the lights on and the systems humming. When roadblocks appear in production, we patch them to ensure our team can continue serving claimants without friction.
• Long-Term Scalability:
  We observe patterns, recognize recurring operational challenges, and build scalable technology solutions to eliminate these hurdles for good.

Tech Ops serves at the pleasure of those serving our claimants, empowering them to do their best work every day while contributing to our mission to drive time-to-relief down to zero.

We are hiring for two Product Engineers to join our Tech Ops team. If you join us, these are some of the projects you will likely own:

• The End-to-End Journey Workbench. Building a centralized internal workbench to visualize the claimant journey from the first ad click to final case closure. You will build connectivity and insights to track onboarding steps, Social Security submissions, case data updates, medical events, and communication touchpoints. This platform will reveal where pipelines fail, where they succeed, and what the user experience feels like across the lifecycle.
• Building the External Claimant Portal. Create a portal for claimants to pull real-time case status, submit medical evidence from providers, and receive critical updates. You could own this build from architectural design to user adoption.
• Engineering the Growth Engine. Scale marketing operations by building data warehouse pipelines to trigger outbound communications (Iterable), integrate with PPC platforms (Google, Meta, Microsoft) for conversion tracking, and ensure robust attribution models. You will bridge engineering and the growth team.
• AI-Driven Developer Velocity. Turn "I see something" into "We did something" faster by building a pipeline that uses Slack change requests and LLMs with repository context to automatically open a Pull Request for engineer review, reducing the distance between feedback and production fixes.
• Front-Line Firefighting & System Resilience. Maintain high availability while balancing short-term fixes with long-term stability. You will handle production fires and refactor systems to prevent recurrence.
• Next-Gen Platform Migration. Lead migration and integration of the current tech stack onto a new architecture to support government benefits (e.g., Veterans’ affairs) with zero downtime for active operations.
• Operational Digitization & Automation. Digitize and automate physical mail processing, automate complex government forms, and establish deep observability to create a single source of truth for data.

We operate as a high-leverage, specialized unit. We are a small team of A-players who value excellence, high availability, and bias for action. We don’t just maintain systems; we are force multipliers for the organization.

• Extreme Ownership. Proactive drivers who own projects from inception to production success. You take responsibility for ongoing success, including opex, user adoption, and long-term stability.
• User-Obsessed Iteration. Build relationships with users, gather feedback, and translate it into what they actually need. Treat user feedback and system data as your north…