Chief Technology Officer (CTO)

Build the operating system for a new institutional asset class, and help more American homes get built.

America's housing shortage is also a capital-infrastructure problem. Regional and local homebuilders can deliver the homes communities need, but their loans remain fragmented, their data is inconsistent, and every transaction can feel bespoke. Unlike residential mortgages, homebuilder finance has never had standardized rails that allow institutional capital to invest at scale.

A New York City-based real estate capital platform has raised more than $100 million to build those rails: shared data, underwriting standards, decision systems, and software that connect homebuilders with institutional investors.

The market is proven. The enduring platform is still yours to shape, AI-native from the start.

The Mandate

• Build the core platform across builder intake, underwriting, credit analysis, capital matching, portfolio monitoring, and reporting.
• Create a shared data layer connecting documents, financial models, investment memoranda, underwriting decisions, and capital-partner requirements.
• Design agentic workflows that can research, reason, execute, escalate, and improve without becoming opaque or fragile.
• Decide where deterministic software ends, where agents begin, and where human judgment must remain in control.
• Own the full production lifecycle from architecture and code through deployment, observability, and iteration.

The Builder

You may be a Staff Engineer, Principal Engineer, Lead Engineer, or Engineering Director ready for your first CTO mandate. What matters is not whether you have held the title. It is whether you can earn the scope.

You can move from writing production code to pressure-testing an underwriting workflow to explaining a technical decision in business terms. You turn ambitious ideas into durable systems without waiting for a perfectly specified roadmap.

• Typically seven or more years of professional software engineering, strong computer-science fundamentals, and ownership of consequential production systems.
• Current hands-on full-stack depth across modern frontend development, JavaScript or TypeScript, backend systems, APIs, databases, cloud infrastructure, and production operations.
• Advanced use of coding agents such as Claude Code, Codex, Cursor, or comparable tools, plus direct experience shipping agentic or LLM-powered systems.
• Practical understanding of AI evaluation, failure modes, permissions, observability, deterministic controls, and human review.
• Experience in lending, credit, structured finance, capital markets, mortgage technology, fintech, investment management, real estate finance, or a similarly complex financial environment.
• Evidence that you can operate across engineering, product, finance, operations, and real user needs.

Exceptional builders with a shorter career arc are welcome when their technical depth, ownership, and production record are extraordinary.

This is not the role for someone seeking a CTO title while moving away from the code, or for someone whose default answer to scale is a larger engineering organization.

The Environment

You will begin with one product manager and two engineers. You can build the team over time, but the product should create nonlinear leverage without depending on rapid headcount growth.

This role is based in New York City and requires regular in-person work with the team in Manhattan on a hybrid basis. It is not a remote role.

• Base salary: $200,000 to $250,000
• Target total cash earnings: Approximately $350,000 to $400,000, including performance bonus
• Equity: Meaningful equity participation

Why This Role

Most greenfield CTO roles begin with an idea searching for a market. This one begins with more than $100 million raised, real transactions, institutional relationships, and the chance to define the technical standard for an emerging financial category.

If you succeed, you will help create the infrastructure through which institutional capital can finance more American homes.

The Interview

You will not be asked to prepare a project or provide work samples when applying. If selected for a video interview, be ready to describe, and ideally demonstrate:

• A consequential system you helped architect, build, launch, and operate.
• An agentic or LLM-powered workflow you shipped and what production use taught you.
• A moment when your judgment prevented the wrong long-term technical decision.

At Urrly, fairness matters. We review every application against the same clear, job-related requirements and evaluate candidates on relevant experience, demonstrated skills, and evidence of ownership.

Apply now.