Senior Full-Stack Engineer (AI-Native)
- Compensation
- Not disclosed
- Location
- Remote (United States)
- Work setup
- Remote
- Seniority
- Senior
- Employment
- Full time
- Experience
- 5+ years
- Category
- Fullstack
- Posted
Skills
Must have
- 5+ years of professional software engineering, with senior-level ownership of production systems
- Production features shipped using Claude Code, Cursor, Codex, Devin, or similar as your primary way of building, not occasional experimentation
- Own the testing for what you build, from unit through integration, and ensure it meets production-readiness standards before release.
- Finish things. Some of what you pick up will be sitting at 70 percent, and getting it to done counts more here than starting something new.
- A recent example (within the last six months) of using AI tooling to deliver something 3–5x faster than you could have without it
- Range across the stack: Python, modern JavaScript/TypeScript, SQL, REST/GraphQL, and cloud deployment (AWS preferred)
- Depth in agent orchestration (loops, graphs, multi-step tool use, multi-agent patterns; LangGraph or similar), with LLM APIs, RAG and vector databases, prompt engineering, and evals running in product
- Build-vs-adopt judgment: fluent enough in the open-source AI ecosystem to reach for a strong community project rather than hand-rolling what already exists
- The engineering fundamentals to recognize when AI output is wrong
Nice to have
- Salesforce APIs, Snowflake, or fintech/lending data models
- Contributions to open-source AI projects
- Experience shipping solo or on a small founding team
Full description
Location: Remote (U.S.)
Employment Type: Full-time
Department: Engineering
Why This Role Matters
Cardiff's edge is how quickly we can convert a lead into a funded customer. Today our average turnaround is 24 business hours; our goal is minutes, through automated systems with human-in-the-loop oversight. AI-native engineering has changed what one strong engineer can deliver, and we're staffing accordingly: not more headcount doing traditional work, but engineers who have rebuilt how they work around modern tooling and ship in days what used to take weeks. The work you do here goes straight into the systems that will get us there.
The Role
You'll own vertical projects end to end: the customer-facing products and internal tools that sit on top of Cardiff's shared platform. You'll report directly to the Managing Partner, work with our Lead AI Architect on system design, and sit with the stakeholders behind each project (operations, sales, underwriting, marketing, finance) to turn what they need into working product, often inside a week. The team is small and senior. Your work will be in production your first week, and what you own will grow as fast as you show you can carry it.
What Success Looks Like
In your first 90 days, you will:
- Ship a product to production that materially beats the status quo for the department you serve, measured on the KPI that fits: speed, accuracy, ROI, or conversions
- Take at least two more prototypes to production with clearly defined before-and-after KPIs
- Build positive working relationships with stakeholders
- Learn Cardiff's business model and integration surface well enough to ship against it without hand-holding
By the end of your first year:
- A portfolio of production systems you own, with attributable impact on funding volume, conversion, or operating cost
- Faster product cycles across the team, with AI-assisted development patterns you introduced now in common use
- A track record of judgment: systems that scale, and AI-generated code that got read, audited, and corrected rather than merged on faith
What You'll Do
- Own each project end to end: backend, frontend, deployment, and iteration once it's live
- Design and launch AI agents that talk to customers, tied to results you can measure
- Work with the Lead AI Architect on architecture and the ongoing evolution of Cardiff's AI platform
- Build against our shared integrations: Salesforce, Snowflake, Gmail, Zoom, Slack, and internal tools
- Reach for best-in-class open source before building from scratch: where the work isn't core IP, adopting a strong community project (think Buzz, the agent-native workspace Block recently open-sourced) beats owning the support and upgrade burden of a homegrown clone