Individual Contributor

We’re not hiring a frontend dev. Or a backend dev. Or a QA. Or a “DevOps guy.”

We’re hiring Builders — people who own a feature from empty repo to live in production and stand behind every part of it.

AI-driven development is how we work. You direct, the AI types, and you review every single line. The typing is the cheap part now. The judgment is the job.

If you ship more in a week with AI than a 5-person team did last year — keep reading. If you paste whatever the AI gives you and hope it works, this isn’t for you.

What you’ll own

One role, end to end. Your feature, your slice, your name on it:

• Build the whole vertical — frontend, backend, database, the deployment of your own work. Not “my part.” • Own the quality — you write the tests, you do your own QA pass, and a bug in your feature is your bug. Not someone else’s stage at the end. • Direct the AI — AI-driven development is mandatory here. You use it as leverage and you catch what’s wrong before it ships. You never push a line you don’t understand. • Hit your timeline — estimate honestly, flag slippage early, deliver what you committed to. • Talk to clients when it counts — sometimes you’re the one on the call or writing the update. You can explain what you built and why.

What we’re looking for

• You take an idea on Monday and have it in production by Friday. • You have real fundamentals — you can read what the AI produces and know when it’s wrong. (If you don’t know what Redis or Kafka actually do, you’re the kind of person who’ll have learned it by next week, not the kind who’s fine not knowing.) • You use AI as a force multiplier, not a crutch. • You care about quality more than your title. • When something breaks in prod, your first instinct is to open the logs — not to say “not my module.”

Who should not apply

• Vibe coders. If “the AI wrote it” is your answer for why something broke, we’re not a fit. • Single-lane specialists who refuse to own anything outside their narrow stage. • Manual-only holdouts who won’t adopt AI-driven development. The speed difference is decisive and non-negotiable. • “Not my job” people. Here, if it has your name on it, it’s your job.

What you get

• A flat team where nobody is above the work — including leadership. • Real ownership. You ship whole things, not tickets. • A team that moves at the pace the industry actually moves at now.

How to apply

Share your work — not just a CV full of buzzwords. Show me something you shipped end to end and tell me what the AI did and what you did.

If you build like this already, you’ll know within the first line of your message.We’re not hiring a frontend dev. Or a backend dev. Or a QA. Or a “DevOps guy.”

We’re hiring Builders — people who own a feature from empty repo to live in production and stand behind every part of it.

AI-driven development is how we work. You direct, the AI types, and you review every single line. The typing is the cheap part now. The judgment is the job.

If you ship more in a week with AI than a 5-person team did last year — keep reading. If you paste whatever the AI gives you and hope it works, this isn’t for you.

What you’ll own

One role, end to end. Your feature, your slice, your name on it:

• Build the whole vertical — frontend, backend, database, the deployment of your own work. Not “my part.”
• Own the quality — you write the tests, you do your own QA pass, and a bug in your feature is your bug. Not someone else’s stage at the end.
• Direct the AI — AI-driven development is mandatory here. You use it as leverage and you catch what’s wrong before it ships. You never push a line you don’t understand.
• Hit your timeline — estimate honestly, flag slippage early, deliver what you committed to.
• Talk to clients when it counts — sometimes you’re the one on the call or writing the update. You can explain what you built and why.

What we’re looking for

• You take an idea on Monday and have it in production by Friday.
• You have real fundamentals — you can read what the AI produces and know when it’s wrong. (If you don’t know what Redis or Kafka actually do, you’re the kind of person who’ll have learned it by next week, not the kind who’s fine not knowing.)
• You use AI as a force multiplier, not a crutch.
• You care about quality more than your title.
• When something breaks in prod, your first instinct is to open the logs — not to say “not my module.”

Who should not apply

• Vibe coders. If “the AI wrote it” is your answer for why something broke, we’re not a fit.
• Single-lane specialists who refuse to own anything outside their narrow stage.
• Manual-only holdouts who won’t adopt AI-driven development. The speed difference is decisive and non-negotiable.
• “Not my job” people. Here, if it has your name on it, it’s your job.

What you get

• A flat team where nobody is above the work — including leadership.
• Real ownership. You ship whole things, not tickets.
• A team that moves at the pace the industry actually moves at now.

How to apply

Share your work — not just a CV full of buzzwords. Show me something you shipped end to end and tell me what the AI did and what you did.

If you build like this already, you’ll know within the first line of your message.