Senior Full-Stack Engineer AI-Native

Standard Conversions is building software to transform the pay-per-call lead generation industry.

We're hiring a full-stack engineer who can architect, build, test, debug, and ship extremely quickly using AI.

This is a small engineering team. You will work directly with the founder and another engineer, and you will have significant ownership over how the platform is built.

We are looking for someone who understands software deeply enough to know why a system works, not someone who simply prompts AI until code appears.

What You'll Own

• Architect full-stack systems from database to backend to frontend
• Build production features quickly from detailed product specifications
• Work across multiple products and workflows inside the same platform
• Design APIs, databases, integrations, and application architecture
• Deploy and own your work in production
• Diagnose difficult production issues independently
• Improve existing architecture where necessary
• Introduce strong automated testing so changes stop breaking unrelated parts of the platform
• Work safely alongside another engineer and multiple AI coding agents
• Understand the business well enough to make good technical decisions without constant supervision

AI-Native Engineering

AI should be part of your everyday engineering workflow.

We currently use tools including Claude Code and GPT, and we want someone comfortable using modern AI coding tools for:

• Architecture and planning
• Full-stack implementation
• Code review
• Debugging
• Refactoring
• Test generation
• Documentation
• Parallel development

We care about speed, but not blind code generation.

You must understand the architecture and be able to explain why your implementation works.

You Must Be Strong at Git

We build in branches and frequently have multiple people working inside the same platform.

You should be highly comfortable with:

• Branching strategies
• Git worktrees
• Rebasing
• Cherry-picking
• Merge conflict resolution
• Git bisect
• Clean commits
• Parallel development
• CI/CD
• Safely separating work between engineers and AI agents

Testing Matters

Our engineering process is becoming much more rigorous around automated testing.

You should be comfortable building:

• Unit tests
• Integration tests
• API tests
• Regression tests
• End-to-end tests
• Playwright or similar browser automation
• CI checks before production deployment

We want engineers who assume that every major feature needs a way to prove it still works after the next feature ships.

What We're Building

Our platform includes multiple interconnected products and workflows, including CRM functionality, call routing, payments, AI systems, and tools used by insurance agencies and agents.

Experience with any of the following is highly valuable:

• Laravel
• Twilio
• Telephony and call routing
• Stripe
• CRM architecture
• Webhooks
• Real-time systems
• High-concurrency systems
• APIs
• AI agents
• Database architecture

Experience with telephony, Stripe, CRMs, and real-time systems is strongly preferred.

What We Expect

• 3+ years of real software engineering experience
• Strong full-stack ability
• Ability to make architectural decisions independently
• Strong debugging ability
• Ability to learn unfamiliar systems quickly
• Excellent Git knowledge
• Strong understanding of databases, APIs, and application architecture
• Comfortable asking questions when requirements are unclear
• Able to receive a spec, identify gaps, clarify them, and then execute independently

Speed matters enormously here.

For appropriately scoped work, we expect engineers to be able to produce a usable first version of a feature within a day, then improve it through iteration.

We would rather ship a solid version quickly, learn, and improve than spend weeks trying to design a theoretically perfect system before users touch it.

This Role Is Not For You If

You:

• Need constant supervision
• Wait around when blocked instead of investigating
• Are uncomfortable owning production systems
• Have weak Git fundamentals
• Use AI primarily as autocomplete
• Cannot debug independently
• Frequently break unrelated functionality
• Over-engineer simple problems
• Cannot explain the architecture behind the code you wrote
• Need weeks to ship work that could reasonably be completed in days

Technical Interview

Final candidates will complete a practical engineering challenge.

You will build a working CRM-style application with a database and use AI as part of your development process.

We will evaluate:

• Your architecture
• Your database design
• Your frontend and backend implementation
• Your Git workflow
• Your use of AI
• Your tests
• Your debugging process
• Your speed
• Your ability to explain why you made each decision

We care less about where you went to school or how impressive your résumé looks.

We care whether you can build serious software quickly, understand what you built, and own it after it ships.