Intro call
A conversation about what you have built and what you want to own next. No slide deck to prepare, no exercise beforehand, and you get to interview us for half of it.
We check every model claim against the vendor’s API before it reaches this site, and we say plainly which parts are not connected yet. If that is how you like to work, write to us.
Six things that are already true of the way we build, and that we would expect you to hold us to.
There is no office to be seen in. Proposals, reviews and decisions happen in writing, in the repository and in the docs folder, so the timezone you work from never decides how much influence you have.
Every model parameter on this site was checked against the vendor’s API and recorded in a capability matrix. Nobody here ships a number they have not watched a real request return.
There is no layer of account managers between you and the people using the product. You read the failed tasks, you answer the mail they send, and you fix what you find in it.
There are fewer of us than the product has pages, so you own a whole area end to end: the design, the implementation, the follow-up when a vendor changes an endpoint overnight.
An annual allowance for courses, conferences, hardware and model credits, spent at your own discretion. You tell the team what you learned from it, not what you spent it on.
Every call that changes product behaviour lands in a dated decision record with the reasoning and the options we rejected. You can read why the codebase looks the way it does before your first day.
Every application goes to one shared inbox, careers@vgent.com. Attach whatever shows your work best: a repository, a page you shipped, a written teardown of something that broke.
Own the creation workbench end to end: the composer, the asset library and the task queue. Deep React and CSS craft, plus an eye for the frame-by-frame detail a video tool lives or dies by.
Build the pieces that are still missing: presigned uploads on real object storage, task ownership and signing, and a queue that stays honest when a vendor has an outage. TypeScript, Node, Redis.
Keep the capability matrix true. Probe every vendor model, record what its API actually accepts and charges, and turn the result into the panel model the product reads at runtime.
Design a dark, dense creation surface where every control spends credits. Prototype in code or in a design tool; either way you will see your work merged in the same week you propose it.
Write the guides and walkthroughs that make somebody’s first generation succeed. Half prose, half sample code, and candid about the parts of the platform that are not open yet.
Stand up the community channels we have not opened yet, answer the first thousand questions yourself, and bring the recurring ones back to the team as product changes rather than FAQ entries.
No algorithm whiteboards, no unpaid take-home, and a written answer at every stage whether it is a yes or a no.
A conversation about what you have built and what you want to own next. No slide deck to prepare, no exercise beforehand, and you get to interview us for half of it.
You walk us through something you made: a repository, a design file, an evaluation you ran. We spend most of the time on the trade-offs you considered and rejected.
A scoped piece of real work from our backlog, paid at contractor rate, done on your own schedule. We review it together the way we would review a colleague’s pull request.
You meet everyone you would work with and ask us anything, including the uncomfortable questions. We send a written decision with our reasoning within three working days.
Send an open application anyway. Tell us what you have built, what you want to spend the next two years on, and where you think this product is currently wrong. We read every one of them.
200-credit free allowance planned. Create anonymously today, no card required.