Software Engineer

## The Role

We're hiring a **Software Engineer** to build and extend Nliven, our real-time ticketing platform for theaters, cultural institutions, and attractions. You'll work full stack, from a well-scoped bug to a feature you own from design through production, on software that sells tickets to Broadway and West End houses while the box office watches the seat map change in real time. This is a role for someone who likes shipping to a product where a slow page or a dropped payment is an empty seat.

## What You'll Do

- Build features and fix bugs across the stack, from tightly-scoped tasks to work you own end to end
- Write the .NET Core services and the React or Vue front ends that keep seat availability, holds, and checkout correct under concurrent load
- Review teammates' code, pair on hard problems, and keep the test suite honest
- Take your turn on production support, because the people on the other end are selling live events with a clock running
- Partner with product and design to turn a venue's real workflow into something that feels simple to the person at the box office

## What We're Looking For

- Professional full-stack experience (we hire at two levels: early-career through a few years in, and experienced SaaS engineers)
- Comfort with a modern front-end framework (React, Vue, or Angular) and backend/API work, .NET Core preferred
- Solid SQL and relational-database fundamentals
- A habit of writing automated tests and reading code as carefully as you write it
- Clear communication; you can explain a tradeoff to a product manager without hand-waving

## Strong Advantages

Nice-to-haves, not strict requirements.

- C# / .NET Core depth and Vue component testing
- Payment-integration experience, Stripe especially, where correctness is non-negotiable
- Azure, GitHub Actions, Terraform, or Datadog in your day-to-day
- Any time spent on high-concurrency, real-time, or inventory-style systems (tickets are inventory with a very unforgiving refresh rate)

## Why This Role Is Special

Ticketing is a harder real-time problem than it looks: a few hundred people can hit the same on-sale for the same reserved seats in the same second, and the seat either holds correctly or a patron pays for a seat that's already gone. You'll work on the part of the product where that correctness lives, for venues that have trusted us because the software is calm under that load.

## Location

Remote within the US, in one of the states we're set up to hire in. Occasional travel for team meetups.

## Next Steps

Tell us about one thing you shipped across the stack and how you knew it held up. One real example beats a polished resume here.