No more whiteboards

Skip one-pointer linked list reversals. Start with technical people. Get a startup job.

No more whiteboards

Skip one-pointer linked list reversals. Start with technical people. Get a startup job.

No more whiteboards

Skip one-pointer linked list reversals. Start with technical people. Get a startup job.

Step 1

Tell us what you want

Be as specific as you like. We'll only reach out if we have something that fits your goals.

At least 220k cash comp

At least 220k cash comp

At least 220k cash comp

Less than 3 meetings/week

Less than 3 meetings/week

Less than 3 meetings/week

No crypto companies

No crypto companies

No crypto companies

Rust or Go, no C++ please

Rust or Go, no C++ please

Rust or Go, no C++ please

Trans friendly health insurance

Trans friendly health insurance

Trans friendly health insurance

Step 2

Take our interview

90 min with an engineer. No AI, no obscure leetcode algos. Try our practice problem.

"The interview is solid. Very tough but not unfair."


"I will be honest, I have never had such an amazing interview experience before. This is how every tech interview should be!"

Step 3

Skip the line

No convincing anyone you have "five years of JSON experience". Skip to talking to technical people.

"I went in with no expectations and ended up with a job that I'm actually excited about."

Take a no-gimmick interview

Our interview is about actual skills, not interview prep. We'll ask you to convert plain English requirements into working code, not invert a binary tree on the fly.

Learn more about our interview

Try a practice coding problem

Talk to technical people

Our entire team is technical.

When you interview with us, you talk to 10+ year ex-FAANG, ex-startup engineers. Our founder is a mathematician, not an MBA. We don't do non-technical calls, because technical skills should do the talking.

Get actionable feedback

Functions should be black boxes. Job hunting shouldn't be.

We'll tell you exactly how you scored and why. We can offer guidance on what companies are looking for, or on how to approach tricky questions. And in most cases, if a company turns you down, we can tell you why they did that, too.

Arch.

Pass

Summary

Great on the basics, weak scaling. Trade-offs were good, could explain why he went with MySQL vs Postgres and why he’d set up a structured API over GraphQL for this problem. Some of the scaling details were off, though; I would’ve really liked to hear him bring up caching given the constraints of the problem (where some queries are going to be way more common than others). He ended up talking about normalization for quite a while instead, which is pretty wrong (not that it can never improve performance but it’s likely to hurt it here).

Arch.

Pass

Summary

Great on the basics, weak scaling. Trade-offs were good, could explain why he went with MySQL vs Postgres and why he’d set up a structured API over GraphQL for this problem. Some of the scaling details were off, though; I would’ve really liked to hear him bring up caching given the constraints of the problem (where some queries are going to be way more common than others). He ended up talking about normalization for quite a while instead, which is pretty wrong (not that it can never improve performance but it’s likely to hurt it here).

Arch.

Pass

Summary

Great on the basics, weak scaling. Trade-offs were good, could explain why he went with MySQL vs Postgres and why he’d set up a structured API over GraphQL for this problem. I would’ve really liked to hear him bring up caching for the high-scale version given the constraints of the problem (where some queries are going to be way more common than others). He ended up talking about normalization for quite a while instead, which is pretty wrong (not that it can never improve performance but it’s likely to hurt it here).

FAQ

?

What kinds of jobs do you work with?

We work mostly with generalist/product or infrastructure engineering roles at startups. If your typical title is something like "back-end engineer" or "full-stack engineer" or the like, you're probably a fit.

We don't currently work with native mobile development or ML/AI roles (although we work with plenty of AI companies). If that's what you do, you're welcome to sign up - we won't bug you unless we have a role for you, and we're likely to open to such roles in the future.

?

What kinds of jobs do you work with?

We work mostly with generalist/product or infrastructure engineering roles at startups. If your typical title is something like "back-end engineer" or "full-stack engineer" or the like, you're probably a fit.

We don't currently work with native mobile development or ML/AI roles (although we work with plenty of AI companies). If that's what you do, you're welcome to sign up - we won't bug you unless we have a role for you, and we're likely to open to such roles in the future.

?

What kinds of jobs do you work with?

We work mostly with generalist/product or infrastructure engineering roles at startups. If your typical title is something like "back-end engineer" or "full-stack engineer" or the like, you're probably a fit.

We don't currently work with native mobile development or ML/AI roles (although we work with plenty of AI companies). If that's what you do, you're welcome to sign up - we won't bug you unless we have a role for you, and we're likely to open to such roles in the future.

?

Does it cost anything?

?

Does it cost anything?

?

Does it cost anything?

?

Do you work with candidates outside the US?

?

Do you work with candidates outside the US?

?

Do you work with candidates outside the US?

?

Can I retry the interview if I don't pass?

?

Can I retry the interview if I don't pass?

?

Can I retry the interview if I don't pass?

Sound good?

Sign up, and let's get started.

Sound good?

Sign up, and let's get started.

Sound good?

Sign up, and let's get started.