Full Stack Engineer

If you are the engineer who naturally takes ownership of the problems that do not fit neatly into frontend, backend, data, or infrastructure, this role gives you the chance to turn ambiguous business-critical ideas into production software for a real, data-intensive financial platform. You will help build the data, underwriting, and accountability infrastructure behind homebuilder finance, where correctness, reliability, and long-term maintainability matter.

This is a hands-on individual-contributor role on a New York City-based technology team building enterprise-grade software for builders, capital partners, and internal operators. The team has proven the value of moving quickly with modern tools and AI-assisted development, and is now adding a traditional software engineer who can bring deeper production judgment, architecture discipline, and full-stack ownership to the next phase of the platform.

You will have close access to company leadership, a technical blueprint, and meaningful business context — but not a queue of perfectly scoped tickets. The right person is comfortable starting from first principles, clarifying the real problem, making practical technical decisions, and shipping the work all the way into production.

• →Build and ship complete product and platform capabilities across React, TypeScript/Node.js, Express, MySQL, Docker, and AWS.
• →Translate loosely defined business problems into clear technical plans, sensible architecture, and reliable production software.
• →Work across frontend experience, backend APIs, service boundaries, relational data models, infrastructure, testing, and operational details.
• →Own application-facing data decisions, including SQL, relational schemas, migrations, and the tradeoffs behind data-model design.
• →Strengthen production quality through automated testing, observability, deployment discipline, performance improvements, and incident prevention.
• →Use AI coding tools to move faster while personally validating, reviewing, and owning every engineering decision and production outcome.
• →Collaborate with a remote technical leader and an in-office operating team through clear written decisions, diagrams, screen sharing, and practical communication.
• →Close the gaps that fall between product, application, data, and infrastructure ownership.

• In your first 30 days, you understand the system and ship a meaningful improvement on a cross-cutting problem that did not already have an obvious owner.
• By 60 days, you have made and defended an architecture or data-model decision that improves the product’s speed, reliability, or maintainability.
• By 90 days, teammates trust you as a default owner for ambiguous full-stack work, and you are identifying valuable improvements before they become assigned tickets.

• You have delivered production software across both backend APIs/services and modern frontend product experiences.
• You are comfortable working with relational databases, SQL, schemas, migrations, and application-facing data decisions.
• You can explain the tradeoffs behind your architecture, not just list the tools you used.
• You have supported what you ship through testing, deployment, observability, performance work, or incident response.
• You have worked effectively in a startup, small team, or autonomous product group where scope was broad and requirements evolved.
• You are hands-on and willing to own both high-leverage design decisions and unglamorous implementation details.
• You use AI-assisted development as leverage, without outsourcing judgment, security, correctness, or accountability to the tool.

The closest stack match is:

• TypeScript and Node.js
• React
• Express
• MySQL and relational data modeling
• Docker
• AWS

Strong engineers from adjacent cloud-web stacks are encouraged to apply if they can demonstrate transferable full-stack depth, production judgment, and relational-data experience. Python, NoSQL, serverless, PropTech, FinTech, lending, or other regulated-product experience is helpful, but not required.

This role is designed for a mid-level engineer and will often align with roughly 4–10 years of professional software engineering experience. Evidence of ownership, technical judgment, and production delivery matters more than an exact year count.