Senior Software Engineer

We're looking for a Senior Software Engineer to grow into full ownership of our engineering function. You'll work directly alongside our current engineering leader — learning the codebase, the systems, the integrations, and the team — until you can run everything independently. This is a genuine succession track: we want someone who can step into the seat at any moment, not eventually. Day to day you'll carry real ownership — architecture decisions, release authority, backend work, incident response — while building the institutional knowledge to be fully self-sufficient. No ramp period is permanent; readiness is the milestone.

Key Responsibilities

Senior Software Engineering Leadership

• Develop independent judgment on prioritization and architecture.
• Lead and coordinate backend engineers — assignments, sprint reviews, PR approvals, and technical mentorship.
• Share go/no-go authority for production deployments; make hotfix vs. queue calls jointly with QA.
• Build working knowledge of every product area: Glovebox, MPI, PromisePay, scheduler, OEM feeds, reporting.

Hands-On Backend Work

• Stay active in the codebase — reviewing PRs, diagnosing production issues, and shipping fixes directly when needed.
• Own queue architecture work: the ongoing ActiveMQ → SQS migration, consumer management, and backlog triage.
• Monitor and respond to application-layer health via DataDog, CloudWatch, and AWS X-Ray.
• Identify and lead infrastructure cost-reduction initiatives (DocumentDB ReadIOPS, Lambda efficiency, etc.).

DMS & OEM Integrations

• Become the internal expert on DMS integrations: Reynolds & Reynolds, CDK, DealerTrack, DealerBuilt, AutoSoft, AutoMate, Dominion, and more.
• Own engineering for OEM data pipelines — Toyota/Lexus TMNA feeds, Honda/Acura programs, Mazda, Ford GUDB, Hyundai/Genesis SLT, Kia, Audi/VW/BMW monthly reports.
• Provide technical guidance to Support and Customer Success on DMS-specific issues and integration edge cases.

Incident Response & Escalation

• Serve as a primary escalation point for P0/P1 incidents — respond, contain, communicate, and document.
• Author RCAs following significant production events.
• Maintain runbook documentation in Confluence; keep escalation contacts current.

Security & Compliance

• Own application-layer security: code-level vulnerability remediation, SAST findings, dependency management, and repo access.
• Serve as the engineering point of contact in SOC 2 and PCI-DSS audits.
• Coordinate with IT and SRE on cross-functional security policies.

Originally posted on Himalayas