SurgeX is one endpoint in front of every AI provider, and the work is the part nobody else wants to own: routing under failure, latency at the tail, and money that has to reconcile exactly. If that sounds like the good part, we should talk.
Remote, senior, small
Everyone here ships. There is no layer between writing the code and seeing it serve a request, and there will not be one for a long time.
You own a surface
Not a ticket queue. You take an area of the product, decide how it should work, and answer for it when it breaks.
Honest by default
We publish measured numbers and leave them blank when we have not measured them. That standard applies to how we work too.
Open roles
Infrastructure Engineer
Routing·Remote·Full time
Own the path a request takes from our edge to a provider and back. This is the part of the product people actually pay for, and it is measured in milliseconds.
What you would do
Work on the router itself: capability filtering, scoring, hedged racing and failover.
Build the latency measurement that the rankings page publishes, and make it honest under load.
Take provider outages from an incident to a routing rule that handles them automatically.
Keep first token time down when a provider degrades rather than fails outright.
What we are looking for
You have run something in production that had to stay up while a dependency did not.
You are comfortable reasoning about tail latency, streaming and cancellation.
You would rather delete a layer than add one.
TypeScript and Postgres are what we use; the thinking matters more than the stack.
Protocol Engineer
Payments·Remote·Full time
Own the money. On chain deposits, the credit ledger, and everything that has to reconcile exactly, every time, with no manual correction.
What you would do
Extend the deposit flow and the watcher that credits accounts from on chain events.
Harden the ledger: holds, settlement, idempotency, and the guarantees that stop a double charge.
Build the tooling that lets support resolve a payment question without touching the database.
Work through the failure cases that only appear with real money moving.
What we are looking for
You have shipped something that handled other people’s funds and did not lose any.
You treat an append only ledger as a correctness property, not an implementation detail.
Solidity and EVM tooling are familiar, and you know where the sharp edges are.
You write the test for the race condition before you write the fix.
Product Designer
Design·Remote·Full time
Own how SurgeX looks and how it reads. A developer tool earns trust in the first ten seconds, and most of that is design.
What you would do
Take the interface end to end: marketing site, dashboard, documentation and the chat surface.
Design the things that carry real data, where the hard part is what to show when there is none yet.
Hold the brand steady across a product that keeps growing new surfaces.
Decide what does not ship, which on a small team is most of the job.
What we are looking for
You have designed something technical and can show the before and after.
You work in the browser, not only in a design file.
You can argue for restraint and mean it.
Motion is a tool you reach for rarely and deliberately.
Developer Relations
Growth·Remote·Full time
Be the reason a developer tries SurgeX and the reason they stay. Documentation, examples, and being genuinely useful in public.
What you would do
Own the documentation: the quickstart, the routing guide, and every example that has to keep working.
Build the integrations and sample apps that make the first request take two minutes.
Answer real questions in public, and turn the recurring ones into product changes.
Write the technical posts that explain how the routing actually works.
What we are looking for
You write clearly about hard things and you have published proof of it.
You have integrated an inference API yourself and remember what was annoying.
You would rather fix the confusing thing than document around it.
How to apply
Send the role name and something you have built. A repository, a post, a product, a design file: whatever shows how you think. A CV is fine but it is not the part we read first, and a cover letter written by a model is the part we read least.