Software Developer, Software Engineer, Software Architect

Location:

Centennial, CO ( In-Office – No relocation) Company:
Yield Solutions Group

Reports to:

Director of Software Development

Yield Solutions Group processes more than thousands of auto refinance applications per month across 30+ lending partners. The systems that support that volume handle real financial data, operate under regulatory constraints, and need to be reliably under load.

• Own architectural decisions for complex, cross-service features. This is not influence from the side; it is accountability for the outcome. When an architectural decision goes wrong, it is yours to fix.
• Set and enforce front-end and full stack standards across the team:
  React component architecture, Type Script patterns, state management conventions, API contract design, test coverage thresholds, and AI engineering practice.
• Conduct authoritative code reviews that evaluate architectural fit, service boundary integrity, performance under load, and security posture alongside correctness. This applies with equal rigor to AI-generated code, which carries its own failure modes: hallucinated APIs, plausible-but-wrong logic, and implementations that pass tests but violate service boundaries or data contracts.
• Apply and model the delegation model from Nate B Jones' five levels framework: make principled, documented decisions about which tasks to delegate to AI agents, at what level of autonomy, and where human ownership is non-negotiable. Other engineers look to you to calibrate their own judgment against yours.
• Raise architectural concerns during sprint planning, design reviews, and roadmap discussions before they become production problems. At this level, that means shaping the conversation, not reacting to it.
• Mentor Full Stack Java Engineers and earlier-career engineers on both technical fundamentals and AI engineering practice: spec authoring, agent output validation, delegation model application, and the discipline of treating AI instructions as engineering artifacts.

• Author structured spec files that define problem scope, constraints, acceptance criteria, and edge cases before any implementation begins, whether by a human or an AI agent. The spec is the source of truth. AI output is an implementation candidate that must be validated against it.
• Craft prompts and AI agent instructions with engineering precision: decompose problems clearly, specify constraints explicitly, and iterate based on what the output reveals about gaps in the original intent.
• Design REST APIs and inter-service contracts across the microservices architecture that are stable, versioned, and defensible. You are setting contracts that other services depend on; treat backward compatibility and versioning strategy as first-class design requirements.
• Manage complex application state with a clear, documented rationale that a teammate can understand and extend without your involvement.
• Write unit and integration tests as part of the development cycle, not after the fact. Coverage and testability are part of the definition of done for every feature, regardless of how it was implemented.
• Resolve architectural blockers independently. You are the person other engineers come to when they are stuck on something hard. You are expected to have an answer, or to produce one.

• Use Datadog to monitor service health, trace requests across microservices, identify latency bottlenecks, and build alerting that catches problems before users do. At this level, you are not consuming observability infrastructure; you are designing it.
• Profile and improve front-end performance with measurable targets: bundle size reduction, render bottleneck elimination, caching strategy design, and load time benchmarking…