Careers
Build software where the work is done
We hire forward-deployed engineers. You work on site at a manufacturer or a distributor, learn the work by sitting with the people who do it, and build the software and the agents around it.
01 The job
The job, as it is
A forward-deployed engineer works on site at the client's business, learns it first-hand and builds for it. Six things follow from that.
On site
You work at the client's site
The plant, the warehouse and the front office. You sit within earshot of the order desk, not in a conference room on another floor.
Travel
You travel
Engineers are on site by default, so the job means travel. The on-site schedule is agreed with each client before a build starts.
Shadowing
You watch before you design
You sit beside a buyer for a morning, ask why at each step and write down what happens, not what the procedure says.
Building
You build the whole thing
You take a workflow from a sketch to software the order desk uses: the screens, the queues, the rules, the connection to the ERP and the agent.
Shipping weekly
You release every week
During a build, working software goes to the people who use it every week. You are at the desk for the first real work that goes through it.
In pairs
You work in a pair
Our engineers come in pairs. One of you asks the questions while the other writes down the steps and the screens, and each of you checks the other's code.
02 A week
A week during a build
Every week of a build has the same four steps: plan, build, release, measure. On site it looks like this.
Illustrative example
A typical week, not a specific client.
-
Mon
Plan with the workflow owner
You look at last week's measurements together, then agree on this week's change and on how you will know it worked.
-
Tue
Shadow, then build
A morning at the desk, watching the work the change touches. An afternoon building.
-
Wed
Build and show
You run that morning's real documents through the work in progress with the people who will use it. They find what is wrong, and you change it.
-
Thu
Release
You test, the workflow owner signs off, and the change goes to the desk. You stay beside the people using it.
-
Fri
Measure and review
You compare this week's work with last week's, review the result with the workflow owner and write the weekly update for the sponsor.
Before any build
An engagement starts with a Discovery Sprint: 2 weeks on site, shadowing every desk before anything is built.
03 Fit
Who thrives in it, and who does not
This job does not suit every engineer. It is better to find that out here than on a plant floor.
You will like it if
- You want to see the work before you design anything
- You can build end to end: the screen, the rule, the connection to the ERP and the agent
- You are at ease on a plant floor in safety glasses, and at a desk next to accounts payable
- You would rather release something small every week than something large once
- You can say that a workflow should stay with a person, and mean it
- You write plainly enough that a scheduler can check your map of their work
You will not like it if
- You want to build from a specification someone else wrote
- You want to work remotely
- You would rather not travel
- You want to work on AI models, not on purchase orders and invoices
- You are not comfortable working under someone else's site rules and change control
- You measure a week by the code you wrote, not by what the order desk could do on Friday
04 How to apply
Apply by email
There is no form. Write a few lines and send them.
Tell us about
- Something you built end to end, and who used it
- A time you learned a job by watching someone do it
- Whether you can travel to client sites in the United States
Send it to gokusahin@gmail.com. We are a new company, so put your questions about the job in the same email.
Apply
Write to us about the job.
Tell us what you built end to end and who used it. There is no form.