Not in the usual sense. It is an index of people who have shipped on site. Anyone can read it, and a profile carries an optional public handle — never an email address.

Do I need a public profile somewhere else?

No, but one verifiable artefact helps: a written case, a talk, a repository. Links survive review; claims alone usually do not.

What if I am employed and do not want to be named?

Say so in the form. The entry can stay as vague as “engineer with two deployments in fintech”, and the reviewer will keep it that way.

Talent

Engineers who have shipped inside a customer's environment and can say what they delivered, at which stage, and what they had to give up.

Submit an entry

Loading listings…

What belongs on this board

Deployments you personally ran, with the stage you were in and the outcome — not a list of skills.
The environment you worked in: the customer's stack, the data constraints, who you answered to on site.
What you will take next and what you will not. The boundary is what makes a profile useful.
At least one result you can defend in a conversation. Numbers are optional; defensibility is not.

Example profile — illustrative, not an open listing

Backend engineer · three on-site rollouts in logistics

Five years of backend work, the last two embedded with logistics customers: a routing model in production at three depots, an ETL cutover, and an evaluation harness the customer's team still runs without help.

Ran the first-week prototype and the metric definition for two of those deployments, and owned the data-boundary work when the customer refused cloud inference. Comfortable being the only engineer in a room full of operations staff. Looking for delivery work of four to twelve weeks: remote, with up to one week on site per month. Not available for a full-time role before next quarter.

Before you post

Is this a job board?: Not in the usual sense. It is an index of people who have shipped on site. Anyone can read it, and a profile carries an optional public handle — never an email address.
Do I need a public profile somewhere else?: No, but one verifiable artefact helps: a written case, a talk, a repository. Links survive review; claims alone usually do not.
What if I am employed and do not want to be named?: Say so in the form. The entry can stay as vague as “engineer with two deployments in fintech”, and the reviewer will keep it that way.

Read before writing the profile

All three indexes

Demand Skills Submit an entry