How the work is done here
There are no open roles today, and that belongs at the top of the page rather than three scrolls down. What follows is how the work is actually done — useful if you want to be told when a role opens, and just as useful if it tells you this is not how you want to work.
The standard
Verify, then write
Nothing gets stated that has not been checked against the running system. Not an API shape, not a schema column, not a port number. "I recall that it does" is not a source, and a build passing is not evidence that a query names real columns.
Root-cause, never paper over
No widening a tolerance, no adjusting an expectation until it matches the output, no retry added to make a symptom disappear. Each of those freezes the bug in and hands it to whoever is next.
Say what you did not do
Skipped scope, checks that could not run, assumptions made — stated plainly. Silence reads as completion, and a silent gap costs somebody else a day.
Guards, not vigilance
When a mistake reaches production, the fix is a test that fails the build if it comes back. A rule that depends on somebody remembering has already been broken; it just has not been noticed.
What that is like in practice
The comparison page names where a competitor is the better choice. The roadmap lists the gaps rather than hiding them, and the changelog records what an early AI finding actually turned out to be. None of that is modesty for its own sake; it is what the standard above produces when it is applied to the public pages as well.
If reading those pages made you want to argue with a specific claim on one of them, that is the most useful possible first message.
If you want to be told
Write to [email protected] with what you would want to work on and something you have built. There is no form, no tracking pixel and no talent pipeline behind this page — the mail goes to the same place customer mail does.
Contributions from outside are also possible on the published parts: the command line and the browser SDK are on npm, and a bug report against either is a real contribution.
Or just use it
The most direct way to find out whether the standard above is real is to send the platform some telemetry and see whether it tells you the truth about your own system.