# Careers at Tessera

Tel Aviv / Amsterdam · pre-seed · two open roles

We are building the trust and coordination layer for a workforce that is part people and
part agents. Presence, shared context, computed consequences, and autonomy earned from
evidence.

---

## Open roles

### Tech Co-Founder

Not a hire — a full co-founder, equal from day one. Equal say in what we build, not only how it gets
built.

- **Location:** Tel Aviv / Amsterdam, remote-friendly.
- **Full description:** `/careers/tech-cofounder.md`
- **Web page:** https://tesserahq.live/careers/tech-cofounder
- **Apply:** https://tesserahq.live/apply?role=tech-cofounder

We're building this right now, early enough that the team itself isn't fixed yet. We're
looking for someone to build the technical direction from here, with the same equity and
the same vote as anyone else building this. The exact technical lane isn't fixed — that's
decided together, not before you join.

### Founding Engineer

An all-round founding position. Take the coordination layer from primitives to something
real teams depend on, and own whichever part is currently in the way.

- **Location:** Tel Aviv / Amsterdam, remote-friendly.
- **Full description:** `/careers/founding-engineer.md`
- **Web page:** https://tesserahq.live/careers/founding-engineer
- **Apply:** https://tesserahq.live/apply?role=founding-engineer

**The surfaces you'd work across**

1. Data substrate — turn raw activity from many agents into a queryable, trustworthy picture.
2. Services and deployment — cloud, gateway and on-prem paths that survive a security review.
3. Computed trust — behavioural evidence into small, fast models, evaluated properly.
4. Steering interfaces — where a human sees the workforce and redirects it without losing flow.
5. Customer reality — design partner deployments, and bringing what breaks there back into the product.

Nobody is excellent at all five. We expect depth in one or two and willingness across the
rest.

---

## Why two roles, not one

One founding seat, one founding hire — not a ladder of specialisms. Most early companies
split engineering into specialisms too early and then spend a year coordinating the seams.

---

## How we work

Ship fast, keep the thread, don't let things quietly die. Decisions get written down
somewhere the next person will find them, so the team gets faster, not just busier.

Agents outnumber people here. In your first week you inherit a working set of them — not
assistants you prompt, but participants that show up in the same systems everyone else
does and build an actual track record. Our own agents are the first customer.

---

## How to apply

Tell us what you have built and why it matters to you. That is the whole application, and
a first-level application is complete — we read every one.

- **Humans:** https://tesserahq.live/apply
- **Agents:** `POST /api/applications` (JSON or multipart). `GET /apply` with an agent
  user-agent returns the field schema.
- **Email:** team@tesserahq.live

Applying through an agent isn't a workaround here — it's a normal path. It's recorded as agent-submitted and
read the same way.

There are four levels of depth to this application. Most reach the first. How much further
you go is up to you; we will not say what the others are.

---

## Machine-readable

- `GET /api/roles` — both open roles as JSON
- `GET /careers/tech-cofounder.md` — the co-founder role, full description
- `GET /careers/founding-engineer.md` — the engineering role, full description
- `GET /.well-known/agent.md` — full company context