About the role
Why us
We started CoLoop in 2020 while still at university. We survived multiple cofounder breakups and all sorts of other near-death experiences. Despite that we built our first product to $1M ARR, and then killed it after realising the opportunity was too small and we didn't have real PMF. We spent six months pivoting, and through that process came to understand just how important customer research is to finding a winning strategy. So we built a product to make it faster, cheaper, and better.
We don't tell you this because we think suffering is something to aspire to. We tell you because if you're evaluating where to work next, you should know who you'd be working with. We are not going to sell early, get comfortable, or lose interest. This is everything to us.
We also take seriously that you're trusting us with your time. Three people who've worked at CoLoop have gone on to become YC founders. When you're here, we'll share everything we know and everything we learn along the way. All we ask is total commitment.
About the role
You'll spend most of your time understanding customers, thinking about what to build, and shipping. Talk to customers directly, sit with the team members who interact with them daily, watch the recordings (in CoLoop). AI handles a lot of the raw building now, so the bottleneck is taste, context, judgement, and polishing.
At CoLoop, engineers own the full cycle. There are no product managers. You gather context from customers and teammates, decide what to build, build it, launch it, measure the impact, and iterate. We track individual attribution in PostHog.
The structure is flat. Influence is earned through skill and context. We'd rather you make a wrong call than wait to be told what to do.
We run 5-6 week company-wide sprints with a decentralised approach and minimal meetings. We're in our Oxford Circus office as often as possible (2 days min per week).
