Senior Full-Stack Engineer - Mortgage

Stefanini Group is hiring!

Stefanini is looking for a Senior Senior Full-Stack Engineer in Remote - USA

For quick apply, please reach out to Alfher Hidalgo

Call: / Email:

Open for W2 candidates only



***Remote Job***

Client builds loan application software for the US mortgage industry. Client is based in Miami, with a team of five spread across the US West Coast, Brazil, South Africa and Spain. The hard integrations are happening now. They are working through certifications with mortgage agencies and integrations with government data sources, some well along and some just starting.

The role

This is a senior, backend-leaning full-stack role. Most of your time goes into Python services, our GraphQL API and AWS infrastructure. You'll also work in our React/TypeScript frontend. We want someone who shapes the API around what the product actually captures: they look at the forms, the documents and the borrower flow, then design endpoints that fit them. You should be able to reason about how a decision in your area ripples through the rest of the system: the frontend, the integrations, compliance, and the people who maintain it after you.

What you'll do

Design and own the GraphQL schema and the Python services behind it, shaped around the data and flows the frontend captures.Own the mapping between our data model and the loan application (URLA / Form 1003)as MISMO XML, the format we submit to Freddie Mac and Fannie Mae.Build and harden the OCR pipelines that turn borrower documents into structured, verifiable data.Own third-party integrations end to end, including Freddie Mac, Fannie Mae, data and verification providers, and the upcoming IRS integration. That includes the certification work each one requires.Ship frontend features in React/TypeScript when that's the fastest path, and work with design on the upcoming redesign. Break work into pieces you can estimate, commit to dates, and raise slippage early instead of at the deadline. Take on product, QA, infrastructure or vendor work when the stage calls for it, and keep the thread when you switch. Give and ask for direct feedback, in code review, in design discussions and about how the team works.

What we're looking for

Senior-level engineering experience (typically 5+ years), with systems you designed and own running in production. Strong Python backend skills and production experience designing GraphQL APIs. Hands-on AWS experience: you've deployed, operated and debugged what you built. Experience mapping application data to and from large, strict XML schemas. Comparable work in other industries counts, such as HL7 in healthcare, ACORD in insurance, or ISO 20022 and FIX in finance. Working fluency in React and TypeScript, enough to build features and to judge how an API decision lands in the UI. Hands-on experience using agentic AI tools (such as Claude Code, Cursor or Copilot) for coding, testing and documentation, along with the judgment to review and take ownership of what they produce. Startup experience on a small team, where scope was ambiguous and you owned outcomes, not just tickets. Experience in fintech or another regulated domain, such as handling PII, keeping audit trails, or building to external compliance requirements. A track record of estimating work and delivering on it, with examples of what you did when an estimate slipped. Comfort giving and receiving direct feedback, and clear written communication across time zones

Nice to have

Hands-on work with the URLA (Form 1003) and MISMO 3.4 / ULAD, including GSE submissions.Other mortgage industry experience, such as loan origination systems or GSE integrations (Freddie Mac LPA, Fannie Mae DU). OCR or document-processing pipelines in production. Integrations with government data sources, including the IRS. Experience going through a vendor certification or partner approval process.

How we work Feedback goes both ways. We say it directly and early, and we expect the same from you, including about decisions that aren't yours. Estimates are commitments. We expect them to change sometimes. When they do, we say so as soon as we know, not at the deadline. Everyone wears several hats. At five people, you'll move between engineering, product, QA and ops. Do each one well, and be clear about which one you're wearing and who owns what. We decide with the whole system in view. A good backend change considers the frontend, the integrations and the compliance trail.

#LI-AH1#LI-REMOTE