AnticipyAll roles

Founding Software Engineer

The pendant hears what you said. You own everything that happens next.

That means browser agents. Someone mentions they'll book the flight, and an agent on their computer goes and books it. When it works, it's the best demo I've ever shown anyone. When it doesn't, it clicks the wrong button and reports success anyway.

The current answer is running the same task several ways and letting the results vote. It beats one agent trying harder. Making that faster, cheaper, and less wrong isn't a roadmap item — it is the product, and it is wide open for someone who wants to own it.

Your first month

Replace my anecdotal sense of where the agent fails with actual numbers.

Bring cost per task down without giving back reliability. Every trick I've found so far trades one for the other.

The honest part

A lot of the week is reading traces to figure out why an agent did something dumb. It's unglamorous, and it matters more than anything else here.

There's no QA team and no on-call. If it breaks at 11pm, it's yours and mine.

You'll probably fit if

You've been building things since before anyone paid you to, and you can show me.

You'd rather spend an hour reading a trace than five minutes guessing.

Something you made has been used by people who aren't you. Side project counts.

You're probably better than your title says. That's the whole point.

Before you apply

Read anticipy.ai/ambient-intent. If you think the whole premise is wrong, say so in your application. That's a better first conversation than agreeing with me.

Apply for this role

No cover letter, no resume required. Omar reads every application himself.

Founding Software EngineerApply