Software Developer, Software Engineer, Backend Developer

Location:

Centennial, CO (In-Office)
Company:
Refi Jet

Reports to:

Director of Software Development

Refi Jet processes a high volume of auto refinance applications every month across a network of 30+ lending partners. The software running that operation spans borrower‑facing applications, lender integrations, and internal tools used by our operations teams. The quality, reliability, and usability of that software directly affects real financial outcomes for real people.

Software Developer 2 is the level where you stop needing the work handed to you fully defined. You already know how to ship. This role is about widening what you can be trusted with: features that touch more than one system, requirements that arrive incomplete, and problems where the right answer is not obvious from the ticket. You will work across frontend applications, backend services, APIs, lender integrations, and internal operations tools.

This level carries in both directions. You are still learning, and you still have people invested in your development: structured code review, a manager whose job includes your growth, and senior engineers who will make you better when you use them. You are also now someone other people learn from. You will mentor Software Developer 1 engineers, review their code with care rather than speed, and answer the questions that are still hard when you are new to a codebase.

Carrying someone else is part of the job at this level, not an extra.

We are deliberately stack and platform agnostic. We care that you can think clearly, learn a codebase quickly, and write code other engineers can build on. We do not care which language or framework you learned first. The specific technologies you will work in are covered in the interview process, and they will change over the course of your career here.

The fundamentals will not.

Plan on five days per week on site in Centennial, Colorado. We say that plainly instead of calling the role hybrid, because the mentoring and cross‑team work this level depends on happens faster in person and because we would rather be clear now than surprise you at offer stage. One or two remote days per week may become available once you are established and performing well.

You earn it, the Director of Software Development decides it, and no date is attached to it.

At this level, leadership means owning outcomes rather than tasks, and starting to make the engineers around you better.

• Own the features and components assigned to you end to end, including design decisions within an agreed approach, testing, release, and support after release
• Mentor Software Developer 1 engineers through pairing, code review, and onboarding, and treat their questions as part of your workload rather than an interruption
• Review code as a contributor of useful feedback, not a rubber stamp. Catch the design problem, not only the style problem.
• Push back on work that does not hold together, and propose the alternative rather than only naming the objection
• Estimate your own work with enough accuracy that others can plan around it, and communicate a slipping estimate before the date, not after
• Improve how the team works by strengthening documentation, tightening standards, and reducing recurring toil
• Represent engineering credibly in conversations with product, operations, and other internal partners, including explaining technical constraints in terms a non‑engineer can act on

• Deliver features across frontend applications, backend services, APIs, and internal tools, including work that spans more than one service or team boundary
• Take a requirement that is incomplete or ambiguous, ask the questions that make it concrete, and turn it into a workable plan before writing code
• Author specifications for your own work and review specifications written by others, under our spec‑driven development practice in which a feature is specified in writing and agreed before it is built
• Design and build API integrations, including work with external lending partner systems, with attention to error handling, retries, idempotency, and failure…