Software Engineer (AI-Native)

Job Description

Job Description

This Is Not a Remote Position.

Software development is changing faster than most companies are willing to admit.

We believe the future belongs to engineers who can direct AI systems, evaluate their output, and make good decisions at speed.

The era of measuring engineering value by lines of code written is ending. The bottleneck is no longer typing. The bottleneck is judgment.

AI can generate thousands of lines of code before lunch.

The hard part is knowing what should be built, recognizing when generated code is wrong, and making architectural decisions that still look intelligent six months later.

That's the job.

What We're Building:

• We're building a closed-loop operating system for the automotive service industry.
• Shop management.
• Accounts payable automation.
• Document reconciliation.
• Accounting.
• Payroll.

Every system shares information. Every workflow feeds another workflow. Every decision should make the platform more intelligent.

We're not building disconnected products. We're building a system.

Our stack includes Rust, Go, Python, React, and AI agent workflows.

We use agentic development extensively. You will spend far more time directing, reviewing, validating, and improving generated code than manually writing it.

If that sounds uncomfortable, this is probably not the right role.

If that sounds exciting, keep reading.

What You'll Actually Do:

• Work directly with the CTO.
• No management layers.
• No committee meetings.
• No product managers translating requirements through three levels of abstraction.
• Just real problems and the responsibility to solve them.
  

You will:

• Build backend services and processing systems in Go, Rust, and Python.
• Design workflows that allow AI agents to reconcile documents and financial records with minimal human intervention.
• Build interfaces that give business owners visibility into their operations.
• Review, challenge, and improve AI-generated implementations.
• Make architectural decisions that affect the long-term direction of the platform.
• Own problems from concept to production.
  

Some days you'll design systems.

Some days you'll review thousands of lines of generated code.

Some days you'll discover that the real problem isn't the one anyone thought they were solving.

That's normal.

Who Thrives Here:

• You probably have somewhere between a few and ten years of serious engineering experience.
• You have shipped real things.
• Not tickets.
• Not isolated features.
• Products, systems, businesses, tools, platforms, or infrastructure that people actually depended on.
• You are comfortable learning whatever technology a problem requires.
• You don't need someone to tell you exactly what to do next.
• You care about whether a system is correct more than whether it is clever.
• You understand that generated code is not automatically good code.
• You can evaluate tradeoffs.
• You can explain your reasoning.
• You can change your mind when new information appears.
  

Most importantly:

You are excited by the idea that one disciplined engineer equipped with modern AI tooling can now accomplish what once required an entire team.

Who Probably Won't Enjoy This:

• People looking for highly structured environments.
• People who need detailed specifications before starting.
• People who want every technical decision reviewed by a committee.
  People who believe AI-generated code is worthless.
• People who believe AI-generated code should be accepted without scrutiny.
• People who measure engineering quality by how many hours were spent typing code manually.
  

Compensation:

• We'll be direct.
• Cash compensation is below what larger companies can offer.
• Equity is a meaningful part of the package.
• If the company succeeds, your participation should matter in a real way.
  

Benefits include:

• Health insurance.
• Dental insurance.
• Vision insurance.
• 401(k) with company match.
• Paid vacation.
• Paid holidays.
  

How To Apply:

• Do not send a cover letter.
• Do not spend time formatting a resume.
• Show us something you built.
• Something you owned.
• Something where the decisions were yours.
  

Tell us:

• What problem you were solving.
• Why you approached it the way you did.
• What tradeoffs you made.
• What you would do differently today.
  

If there is a project you've worked on that other people never fully appreciated, start there.