Full Stack Engineer

Scalable Path; United States; Remote; USD 180,000 - 240,000; Full time

Benefits offered by this job

Remote work

Job summary

Scalable Path is seeking a Senior AI-First Full-Stack TypeScript Engineer with Postgres Focus to join the team remotely. You will own the data-centric system of record for an AI-driven loan origination and automated underwriting platform, directing the build and reviewing AI-generated code.

Your work will emphasize immutable schemas, row-level security, and reliable Postgres workflows. You’ll collaborate with a co-founder and a platform engineer, ensuring correct migrations, performance tuning,

Qualifications

• Senior full-stack TypeScript with a database center of gravity.
• Deep PostgreSQL—schema design, row-level security and grant-based access control, window functions, partitioning, and performance work at the query-plan level.
• Production event-driven design: transactional outbox or equivalent, idempotency, at-least-once delivery and what it actually costs you.
• Production AWS. We are AWS-native — EventBridge, S3, KMS, RDS/Aurora, Bedrock.
• You will work in a codebase that bans floating-point arithmetic and enforces a decimal type through lint rules, with contract and numeric invariants checked in CI.
• You need to be fluent enough in TypeScript's type system to work inside that discipline rather than around it.
• Strongly preferred: ledgers, payments, financial calculation engines, rules engines.
• Nice to have: exposure to Temporal or another durable-execution engine.

Responsibilities

• Own the system of record: append-only envelope storage for application facts, with access enforced at the database layer (grants + row-level security).
• Persist decisions and their complete evaluation traces, with snapshot hashing for byte-for-byte re-derivation.
• Own the headless intake API and contract-first integration path—the API contract as the artifact.
• Build the Postgres-based event path to AWS EventBridge with idempotency and delivery guarantees.
• Design and own the Postgres schema—partitioning, indexing, and query-plan-level performance for append-only tables.
• Own the historical application loader: ingest years of prior applications into the fact model.
• Own the data side of document extraction: schema, validation, confidence thresholds, routing.
• Build KPI and reporting surfaces over the system of record with as-of queries and history.

Skills

TypeScript

PostgreSQL

AWS

Data modeling

Code review

Immutable data

Tools

EventBridge

S3

KMS

RDS/Aurora

Bedrock

CI/CD

Job description

Scalable Path is looking for a Senior AI-First Full-Stack TypeScript Engineer with Postgres Focus to join the team. This is a remote, full-time (40 hours/week) position.

Client company description:

The client is a well-backed New York startup in building a generic loan origination and automated underwriting platform from scratch.

Overview:

The client is building a loan origination and automated underwriting platform. The build is AI-primary: most of the code is generated by AI against a loosely specified architecture that needs input/ratification from you. You are the human who owns the data side of that. You direct the build, review what comes out, finish what the AI cannot, and sign off on merges as one of two engineering reviewers.

Your lane is the system of record — an immutable, append-only store of application facts, decisions, and their full evaluation traces, reproducible byte-for-byte months later — plus the intake API that feeds it, the historical loader that backfills it from years of prior applications, and the data side of document extraction. The hard parts are schema design under immutability constraints, access enforced at the database layer, as-of queries over history, getting events out of Postgres reliably — and knowing, when the AI's version is subtly wrong, exactly why.

This suits someone who would rather own outcomes than type every line, who can read a schema or a migration and spot the flaw before it ships, and who finds a codebase built from specs and vectors rather than tribal knowledge a relief. If you have built ledgers, financial calculation engines, or anything where "roughly right" was never acceptable, this will feel familiar.

Responsibilities:

• Own the system of record: append-only envelope storage for application facts, with access enforced at the database layer (grants + row-level security) rather than in application code.
• Persist decisions and their complete evaluation traces, with snapshot hashing, so any historical decision can be re-derived and verified byte-for-byte.
• Own the headless intake API and programmatic path — how applications enter the platform — contract-first, with the API contract as the artifact.
• Build the event path out of Postgres: transactional outbox into AWS EventBridge, with the idempotency and delivery guarantees that implies. Design the boundary with the Temporal workflow layer (owned by the platform-focused engineer) so outbox delivery and workflow retry semantics compose rather than collide.
• Design and own the Postgres schema — partitioning, indexing, and query-plan-level performance against append-only tables that only ever grow.
• Own the historical application loader: ingest years of prior applications and their outcomes into the fact model to support backtesting.
• Own the data side of document extraction: fact-model schemas, validation of extracted candidate facts, confidence thresholds and routing into the store.
• Build KPI and reporting surfaces over the system of record — as-of queries, window functions, history that never rewrites itself.

Qualifications:

• Senior full-stack TypeScript with a database center of gravity. You direct AI tooling to do most of the typing, and you could code all of it yourself if you had to — the second part is what makes the first part safe.
• Deep PostgreSQL — not "I use an ORM" deep. Schema design, row-level security and grant-based access control, window functions, partitioning, and performance work at the query-plan level.
• Production event-driven design: transactional outbox or equivalent, idempotency, at-least-once delivery and what it actually costs you.
• Production AWS. We are AWS-native — EventBridge, S3, KMS, RDS/Aurora, Bedrock.
• You will work in a codebase that bans floating-point arithmetic and enforces a decimal type through lint rules, with contract and numeric invariants checked in CI. You need to be fluent enough in TypeScript's type system to work inside that discipline rather than around it — including where values cross the boundary into and out of Postgres.
• You are comfortable being the reviewer of record. You can read a migration, a schema, or a query plan produced by someone — or something — else and tell whether it is right, and you would rather own that judgment than the keystrokes.
• Strongly preferred: you have worked somewhere exact numbers and reproducible results were non-negotiable — ledgers, payments, financial calculation engines, rules engines. Be specific about what you owned.
• Strongly preferred: some production exposure to LLM structured outputs or document extraction — enough to own the data side of an extraction pipeline (schemas, validation, confidence thresholds), not to research models.
• Please point us at something concrete: a schema you designed under audit or immutability constraints, or a case where you enforced correctness at the database layer instead of in application code. This weighs more than a résumé.
• Nice to have: exposure to Temporal or another durable-execution engine. You will not be authoring workflows, but you will be designing the persistence boundary they run on.
• A plus: experience in mortgage or consumer lending — origination, underwriting, servicing, or the vendor ecosystem around them (credit bureaus, AVMs, fraud, e-signature, etc.).

Relationships - who you'll be working with:

You will work directly with the co-founder — technical, hands-on, and the product owner — alongside a second senior full-stack engineer with a platform and engine focus, a part-time security engineer, a junior engineer who joins a month or two in, and a business-side integrations lead who owns vendor relationships. The originating lender's own underwriters validate and countersign what the platform decides. No layers between you and the decision-maker. You are expected to overlap with most of the US East Coast working day.

12+ months

If all works out this is expected to be an ongoing role

Preferred regions:

The client's preference is for candidates to be located in Latin America or Canada.

Notes:

The right candidate will have very strong skills in using AI to do the heavy lifting. This project is going to move fast and we want someone who can keep up. It's going to be a fun ride.