Software Developer 2

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 modes

Model and query data correctly, and understand the performance and integrity consequences of the schema and queries you write

Write and maintain automated tests that give the team real confidence, and recognize when a test is protecting behavior rather than only raising coverage

Debug production issues methodically, identify the actual cause, verify the fix, and record what you learned so the next person does not repeat it

Participate in release, deployment, monitoring, and production support for the systems you build

Use AI-assisted development tools as part of normal daily work, and remain fully accountable for every line you ship, whether you or a tool wrote it first

First 90 days: You are delivering defined features independently and your code review comments are useful to other people. You know the shape of our borrower, lender, and internal systems, and you can find your way into unfamiliar code without a guide.

First 6 months: You take on a feature with unclear requirements and come back with a plan rather than a list of questions. You are the reviewer a Software Developer 1 wants on their pull request. You have improved something structural, not only shipped tickets.

First year: You own a component or feature area that others rely on. You are trusted with work that touches lender integrations or borrower-facing flows. A Software Developer 1 is measurably better because of you, and you can name how.

The ladder is Software Developer 1, Software Developer 2, Software Developer 3, Lead Software Developer. Each level has documented expectations. What separates them is the scope and independence of the work you can be trusted with, not years on your resume. You advance to Software Developer 3 when you can own ambiguous, cross-cutting problems, when your technical judgment is sought rather than checked, and when your effect on other engineers is visible. We promote from within, and we will tell you plainly where you stand against the next level.

Work directly with product stakeholders and operations partners to shape features that solve real business problems, not only to receive requirements from them

Coordinate with other engineers on work that crosses service or team boundaries, including agreeing on interfaces before both sides build

Support QA, testing, release, and post-release validation so features work as intended before they reach users

Follow and help enforce internal standards for source control, code quality, documentation, deployment, and team communication

Handle borrower and lender data responsibly and follow all internal security, privacy, and data handling requirements. We operate in a regulated industry. Careful data handling is a condition of the role, not a preference.

Never move production data into a non-production environment, share credentials, or work around a security control to save time. If a control is blocking legitimate work, escalate it and help fix the control.

Contribute to a collaborative engineering culture by being dependable, communicative, and open to feedback

None of the following is required, and their absence will not remove you from consideration.

Experience owning a feature area or service that other engineers depended on

Experience mentoring or onboarding a more junior engineer

Experience integrating with third-party or partner APIs where you did not control the other side

Experience with containerized or cloud-hosted environments and the deployment pipeline that reaches them

Experience with observability tooling, including tracing a real incident through logs and metrics

Experience using AI-assisted development tools with good judgment about when to trust them

Interest in fintech, lending platforms, or transaction-heavy software products

Experience with auto lending, auto refinancing, or consumer credit products.

Familiarity with loan origination systems (LOS), credit decisioning, or lending infrastructure.

Experience working with external partners or B2B clients in a product-led organization.

Yield Solutions Group is an Equal Opportunity Employer. We are committed to creating an inclusive environment for all employees and applicants.