Work With Us
This isn't a job listing.
We're not hiring for a role. We're looking for a certain kind of person—and when we find them, we figure out how to work together.
What We're Building
We're a small team reinventing what consulting looks like when AI changes the cost structure of building. We make tools that help us make tools. Playbooks, pipelines, agents, knowledge systems—configured for our taste, deployed for our customers. The methodology IS the product.
If that sounds interesting, keep reading.
What "Product Engineer" Means Here
We use this term loosely. It's not a title—it's a description of what the work actually requires.
Think of it as three overlapping domains:
Technical systems. You can build things. Integrations, pipelines, prototypes. You're comfortable troubleshooting DNS, talking to IT departments about SSL certificates, or spinning up a proof of concept in an afternoon.
Business dynamics. You understand how organizations actually work. Strategy, incentives, why initiatives fail. You can sit with a customer and understand what's really blocking them—not just what they say is blocking them.
Facilitation. You can communicate. Run a workshop. Translate between technical and non-technical. Make abstract ideas concrete for the person across the table.
Nobody is equally strong in all three. But the work requires fluency across at least two—and curiosity about the third. You might be debugging an integration on Monday and facilitating a strategy session on Thursday. That range is the job.
Who Tends to Thrive
We've noticed patterns in the people who do well here. Not requirements—patterns.
The systems thinker who's been building tools since they were young. Maybe you were writing Perl scripts as a teenager, or building elaborate Factorio factories, or automating everything in your life that could be automated. You think in feedback loops and second-order effects. You see AI as the next leverage point in a long history of building things that build things.
The ambitious builder who grew up modding games. You learned systems thinking through Minecraft redstone or Satisfactory logistics or EverQuest economies. You're younger, you haven't been institutionalized by big-company process, and you're excited by what's now possible. You build things because you can't not build them.
The industry veteran who's tired of decks. You've done the consulting thing, or the enterprise thing, and you're sick of deliverables that get filed away. You want to build, not advise. You see AI changing everything and you want to be building the future, not presenting about it.
These aren't the only paths in. They're just the ones we've seen.
What We Actually Care About
Systems thinking. Seeing how pieces connect. Understanding that changing one thing changes other things. Designing for emergence, not just specification.
Curiosity. The kind that makes you try new tools before you need them. Catnip for interesting problems.
Building. Not talking about building. Actually making things. Using AI to give yourself capabilities you wouldn't otherwise have.
Autonomy. We work in small teams—usually two people. Minimum viable team for the task. That only works if everyone can operate independently and pull in the same direction.
How We Work
Small teams. Usually two people per engagement.
Async-first. Remote. No geographic constraints—if we can hire you from where you are, we will.
Everyone has the same job: find ways to use my talent to help customers. That means something different every week. It's everything from troubleshooting integrations to facilitating strategy sessions to building internal tooling that makes us faster.
We're building the consulting firm we'd want to hire. AI-native from the ground up. Using Claude Code, Lovable, custom agents—whatever gives us leverage. The tools we use to serve customers are the same tools we're refining every day.
Interested?
We don't have an application process. We have conversations.
If this resonates, send us an email. Tell us what you're working on. And answer this:
What have you built for yourself to give yourself leverage?
Doesn't have to be software. Doesn't have to be impressive by anyone else's standards. We want to know what you made because you saw an opportunity to make your own life better—and you couldn't not make it.