Staff Software Engineer – C#

ABOUT VICTORY LIVE Victory Live is a private equity backed technology company aimed at maximizing distribution and yield for live event ticket inventory. We provide an end-to-end software platform for the live ticketing industry, managing thousands of sports, theater, and live music event tickets on behalf of artists, promoters, teams, venues, and professional resellers. Victory Live's comprehensive offerings include an established B2B marketplace, along with both a full-service and an automated SaaS platform to handle all elements of the ticket sales lifecycle, from ingestion to sales fulfillment. THE POSITION Victory Live is looking for a Staff Software Engineer to own the technologies and processes that power our B2B marketplace on C# and .NET. You'll ship features across several business-critical services, retire technical debt, and set the standards other engineers build against. This is a chance to shape one of our main revenue engines at a premier live event ticketing company. RESPONSIBILITIES • Collaborate across teams to influence engineering work, ensuring decisions align with divisional strategy • Drive large-scale technical initiatives in our .NET services, solving highly complex problems and shipping scalable, secure solutions • Provide guidance and support to engineers, helping them grow and work through hard technical problems • Work with Architects to design and implement system-level solutions within company standards • Define and promote engineering best practices across teams, from test coverage to service boundaries • Identify and pay down technical debt to keep our .NET services maintainable • Hold the team's code to a high bar through rigorous review, consistent with our quality program • Write high-quality code yourself on the most complex and critical work REQUIREMENTS • 10+ years of professional software development experience • Strong proficiency in C# and .NET • Strong experience building and maintaining high-throughput backend services and APIs at scale • Deep understanding of software engineering best practices • Familiarity with the rest of our stack: Entity Framework Core, RabbitMQ, Kafka, Redis, MSSQL Server, Datadog, Grafana, Kubernetes, Terraform, Docker, GitHub • Familiarity with Azure and AWS services PREFERRED QUALIFICATIONS • Knowledge of live ticket sales or experience working within a fast-paced industry • Mentorship and leadership experience guiding onshore and offshore teams • Genuine interest in growing the engineers around you and shaping team culture, even without a formal management track WHY VICTORY LIVE • You'll build the infrastructure live events run on; millions of tickets, hundreds of venues, many of the largest teams and events in the world • A lean team where decisions move fast and your code reaches real fans, often the same week • Every release has stakes. Every improvement is felt • High expectations, low tolerance for politics, and a culture built on writing well and shipping with care OUR VALUES We build the systems that power live event ticketing, and we hold a high bar for how we do it. Four principles run through everything: • Quality of life. Sustainable processes over heroics. Nobody should be a single point of failure, and nobody should be afraid to take a vacation • Quality of code. Clarity over cleverness. If a teammate needs a long explanation to follow your code, it needs simplifying. Tests prove your work; they aren't optional • Protection of production. Every change is reviewed, tested, and observable. We build with monitoring in mind from day one so we find problems before our users do • Shared knowledge. We work across time zones, so we communicate in the open. Questions go in channels, not DMs, and one answer becomes shared knowledge ENGINEERING PRINCIPLES We are an AI-native engineering team. Here is what that looks like in practice: • AI-assisted engineering. Every engineer uses Claude, Claude Code, Copilot, and agentic tooling as a routine part of their workflow • Async-first. Most decisions happen in writing through Jira, Confluence, PR descriptions, design docs. We over-communicate on changes and under-communicate on noise • Ownership mindset. Engineers are responsible for what they write and no code reaches production without review. Reviewers are co-owners • Observability is part of "done." If the on-call engineer can't understand a system without reading source, more logging, metrics, and dashboards are needed • Preservation of quality of code and life. We write code that is clean, tested, and maintainable so it serves us well over time, and we build sustainable processes so no one burns out or becomes a single point of failure • Shared knowledge and continued education. We grow as a team by learning from each other through reviews, documentation, and collaboration OUR STACK & WAYS OF WORKING • C# and .NET power our B2B marketplace, distribution integrations, and partner-facing APIs • Web & mobile clients, REST APIs, microserv