Jr. Software Engineer

Job Summary:

Silvervine Software builds and supports the insurance systems that carriers and their partners rely on every day — policy administration, claims, rating and payments. We are hiring a junior software engineer to join our LAAIR team.

The team owns SvApi, the Silvervine API layer that connects our insurance platform to the outside systems it depends on. When an agent asks for a home or auto quote, SvApi is what reaches out to the data vendors, pulls back motor vehicle records, prior loss history, property valuations and credit information, and turns all of it into a rate. Most of our work is integration work: talking to third-party APIs that we do not control, mapping their responses into our own models, and working out what went wrong when a vendor changes something without telling us.

This is a genuine junior role, not a senior role with a junior title. You will start on well-scoped pieces of that work in C# and ASP.NET Core, with a senior developer reviewing everything you write, and your scope will grow as you learn the domain. We expect you to be new  do not expect you to already know insurance. What we are looking for is solid fundamentals in C# and SQL, care when reading a specification, and the willingness to say early when something does not make sense.

Please read the full job description before applying. It contains specific instructions on what to include in your application, and we do read for them.

Job Description:

About the role

You will join the LAAIR team, which owns SvApi — the Silvervine API layer that sits between our insurance platform and the many outside systems it depends on. When an agent asks for a home or auto quote, SvApi is what goes out to the data vendors, pulls back motor-vehicle records, prior loss history, property valuations and credit scores, and turns all of it into a rate.

That means most of our work is integration work: talking to third-party APIs that we do not control, mapping their responses into our models, and figuring out what went wrong when a vendor changes something without telling us.

You will start on well-scoped pieces of this, with a senior developer reviewing everything you write. As you learn the domain, the scope grows. We expect you to be new  do not expect you to already know insurance.

What you'll work on Building and maintaining REST endpoints in C# and ASP.NET Core across our service set — rating, policy, claims, motor-vehicle records, VIN lookup, loss history, flood risk and document generation.

Integrating third-party insurance data providers. Reading a vendor's schema or documentation, modelling their response, and mapping it into ours. Some of them use clean JSON; some hand you an XML schema that rejects your request for reasons it declines to explain.

Response mapping and projections — deciding which fields our API surfaces to a partner, and making sure none of them silently go missing.

Writing unit and integration tests for your own work, before it is reviewed. We have a standing test-coverage backlog and you will spend real time in it — it is one of the fastest ways to learn a codebase you did not write.

Applying cross-cutting concerns service by service — request validation, global exception handling, security headers, caching. Repetitive by nature, but it takes you through every service we own.

Moving duplicated code into shared libraries. We are consolidating common serialization and filtering into a core package, one service at a time.

Debugging production integration failures. A partner reports a 400 that should have been a 401; a response is dropping a field; a cached token is expiring wrong. You will read logs, compare against the legacy platform's behavior, and find it.

Sprint ceremonies: planning, refinement, standup and retrospective.

What we need from you Working knowledge of C# and the .NET ecosystem (.NET 6 or newer).Comfort with REST APIs — you have called one, and ideally built one.

Enough JSON and/or XML serialization experience to know that mapping between two models is where the bugs live.

Enough SQL to write a join, a GROUP BY, and reason about why a query returns the wrong row count.

Familiarity with git and…