Software Engineer
Software Engineer
Posted today
SENIORITY
Lead
About the role
- 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.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
