Small teams win
There are no middle-management layers between finding a problem and solving it. Engineers join customer calls, shape product decisions, contribute to go-to-market ideas, and work wherever they can create the most leverage. GTM builds prototypes for features, brainstorms UX ideas, and fixes UI issues in the product.
The ideal feels less like a traditional company and more like your smartest friends finishing an impossible project together: high trust, clear ownership, a little urgency, and the confidence that everyone will deliver.
Our job is simple: find exceptional people and give them hard problems.
Reasons why Replo is a great fit
You wanna win (in an almost insane way)
We learned quickly that the most important predictor of success is determination. At first we thought it might be intelligence.
If someone tells you that you can’t do something, you wanna get out there, do it, and prove them wrong. Some people join startups because “working at a startup” sounds like a fun lifestyle. That is a bad reason. You should join because you want to build something GREAT that’s never been done before.
You want actual ownership
Artists aren’t merely capable of shipping. They insist on it. So if you don’t let people ship, you won’t have any artists.
Everyone wants ownership, but usually that means a PM writes a ticket and takes the call from the customer while you decide how to implement the solution. That’s not what we mean. If you find an important enough problem, we expect you to go solve it end-to-end—from product to design to engineering.
You are AI-pilled in an extreme way
Everyone writes code here. Engineers ship features. Marketing builds prototypes. Everyone uses Cursor and Claude Code. If AI is not changing how you work every month, you’re behind.
You have a strong sense of urgency
If something can be done today, you’ll do it today. If an agent can work overnight, you kick it off before bed and leave your laptop plugged in.
You’re scrappy
Scrappy means being relentlessly resourceful. Being relentless isn’t enough—the problems you encounter at a startup are novel, so brute force alone won’t get you through them. You keep the goal fixed while changing the plan as often as necessary. If someone tells you something is gonna need X, Y, and Z, you figure out how to get it done with 10% of the resources and 10x the speed. You don’t wait for the perfect tools, more headcount, or someone’s permission. You keep trying new things until you make it work.
You wanna build a culture of builders
You wanna work with people who are thoughtful, creative, and extremely good at what they do. We argue, debate, and disagree vehemently, but at the end of the day, everyone is working toward the same goal: building the best product imaginable. The hackathons, workout classes, and ski trips aren’t manufactured company culture—they happen naturally because we genuinely enjoy spending time together.
You don’t have time for bullshit
We don’t say fake things to spare each other’s feelings. Don’t be an asshole. Be nice to each other, but don’t sugarcoat hard problems and issues. Celebrate the wins and learn from your losses.
Transparency matters to us, and we want to build a tight-knit team. If you didn’t get to something, just say you didn’t have time. If you need help, ask for help. We’re here to win as a team, and if we don’t keep communicating this way, it’s not gonna be fun for anyone.
Reasons why Replo is probably a bad fit
You’re not technical
If you’re not able to write code, you’re probably not a good fit. We exclusively hire people with strong technical backgrounds and a quantitative mindset, regardless of title. You don’t need a computer science degree. You do need to use LLMs well, spot workflows that can be automated, make decisions with data, and reason from first principles.
You’re interviewing companies big and small
A version of this is that all your friends are working at startups, so you thought, “I might as well give it a go.” Paul Graham has a great article on why you shouldn’t start a startup just because it feels like the thing ambitious people are supposed to do. Startups are all-consuming, lack structure and mentorship, and constantly force you to solve problems you’re not prepared for. You should consciously decide you want to join one before you start interviewing.
Working here will improve your career opportunities down the road because you’ll need to do a bit of everything. It’ll build resilience, motivation, and a can-do attitude that none of your peers will get from working on a button at Meta for two years. There’s a reason recruiters at big tech companies always try to convince you that the team you’re joining is a “startup within a big company.”
You want to be a manager in your next role
You can grow into management here. But you need to join as an individual contributor. Hiring should not be the de facto solution to any problem, and coming in expecting that you’ll be managing the actual makers is a recipe for getting fired. Also read The One Thing CEOs Should Delay as Long as Possible.
You like the “strategy” but not the small details
The number of times a candidate says, “I wanna work on strategy,” during our conversation is inversely proportional to the probability of getting the role. Ideas are cheap. We expect everyone to do strategy, ask AI tools why their ideas won’t work, iterate, and implement those ideas from 0 → 1.
This video is an instructive example of people who only wanna do strategy and don’t actually do the work. If you own a project and hear yourself saying, “I’m not an engineer,” “I’m not in sales,” or “We need to hire someone for that,” Replo is probably not the right fit. If you don’t know how to do it, figure it out.
If Noah and I had waited to hire a recruiter before we hired engineers, we’d never have a team. If we had waited to hire a designer, we’d never have a product.