Software Developer

Location: United States (remote or hybrid) · Reports to: VP of Engineering · Type: Full-time About the role Universal Background Screening is modernizing its platform with Orion, a cloud-based background-screening platform. It runs alongside long-standing legacy systems while clients migrate. We're looking for a hands-on Senior Development Manager to be the first line of technical response in U.S. hours. You'll log in, investigate, debug and find the root cause of production issues quickly, then drive them to resolution with our global engineering teams. You'll also lead and grow U.S. engineering capability so that Orion can be supported end to end from the United States. This is a player-coach role. You'll spend real time in logs, dashboards, code and data, and you'll build the processes and people that make production support predictable. What you'll do Production support and root-cause analysis (primary focus) Act as the U.S.-hours technical lead for Orion production issues. Triage, reproduce, and investigate through logs, metrics, traces, queries and code. Perform root-cause analysis and deliver a clear diagnosis, workaround or fix path fast, even when the permanent fix is built by another team. Hand off well-documented findings to global engineering teams, so fixes start from evidence, not from scratch. Own incident communication: keep tickets current (status, workaround, fix, target release) and keep stakeholders informed until closure. Lead post-incident reviews and drive the follow-up actions that prevent repeats. Engineering leadership Lead, mentor and grow U.S.-based engineers, and build their ability to support Orion independently. That includes knowledge transfer, runbooks and training. Partner with engineering leaders and teams across time zones on priorities, handoffs and escalations. Help define and run the support model: triage ownership, escalation paths, on-call rotation and U.S./global handoffs. Delivery and quality Work with Product, Program Management and Scrum to turn business needs into clear, prioritized, well-scoped work. Support predictable two-week sprint delivery and releases: release readiness, verification, and rollback when needed. Champion engineering discipline: code review, testing, ticket hygiene, documentation and secure coding. Identify recurring issues and technical debt, and make the case for fixing root causes. Platform knowledge Become an expert in Orion's architecture, integrations and data flows, including how Orion interacts with legacy systems during migration. Keep architecture, runbooks and troubleshooting guides current in Confluence. What you'll bring Required 8+ years in software engineering, including 3+ years leading engineers or teams, while staying hands-on. Strong production debugging and root-cause analysis in distributed, cloud-hosted systems. C# / .NET (.NET 6+), including REST APIs and service-to-service integration. SQL and relational databases (MySQL and/or SQL Server): query analysis, performance tuning, data investigation. Observability tools: centralized logging (e.g. ELK/Elasticsearch), metrics and alerting (e.g. Grafana), and log-driven diagnosis. Containers and cloud: Docker, Kubernetes, and AWS (e.g. RDS). Integrations and security basics: JSON/XML APIs, OAuth 2.0/JWT, certificates, TLS. Source control and delivery: Git branching workflows (e.g. GitFlow), CI/CD pipelines, code quality gates (e.g. SonarQube). Agile tooling: Jira and Confluence. Excellent written communication: clear incident updates, RCAs and handoffs to distributed teams. Comfort working with teams across time zones, with some flexibility for early-morning overlap and occasional evening release windows. Nice to have Experience modernizing or migrating from legacy platforms (e.g. classic ASP, VB, older monoliths) to modern services. Background screening, HR tech or other regulated data (FCRA, PII handling). Experience with ATS or HRIS integrations. MongoDB, load testing (e.g. JMeter) or test automation (e.g. Playwright). Practical use of AI-assisted development and debugging tools, with sound review practices. Experience building on-call programs, runbooks and incident-management processes. What success looks like First 30 days: access to all environments and tools; you know the Orion architecture, key integrations and the support process; you shadow and then lead triage of live issues. First 60?90 days: you independently triage and root-cause most U.S.-hours production issues, with clear handoffs and current tickets; the first runbooks are in place; you're training other U.S. engineers. Ongoing: faster time to diagnosis, fewer repeat incidents, predictable releases, and a U.S. team that can support Orion end to end.