vibencode
Work that ships.
We split our time between client projects, our own products, and training the people who join us. Whichever one you land in, the work has to run in somebody else’s environment, be handed over, and keep working once we have gone.
You will work on production systems, not sandboxes.
Client environments, live data, constraints you did not choose. The mess is the job. A tidy problem would not have needed us.
You will write things down.
Evaluations, architecture decisions, handover documentation. Work that cannot be explained cannot be handed over, and everything we do gets handed over.
You will sometimes argue against the project.
Saying “this does not need AI” is part of the role, not a failure of it. We would rather lose the work than build the wrong thing.
You will talk to the people who do the work.
Engineers, designers and the founder’s office all sit in discovery. Whoever watched somebody work for an afternoon usually spots the real problem before the spec does.
Nobody here is protected from feedback, including the founders.
- Engineering Backend, full-stack and early-career. Mostly Python.
- Design UI and UX, on products people actually have to use every day.
- Product Roadmaps for AI-powered applications, MVPs and custom builds.
- Growth and marketing Demand, positioning and the experiments that tell you which is working.
- Sales and business development Out of the founder’s office, close to what is being sold and why.
- Internships Frontend, testing and the founder’s office. Real work, not a shadowing exercise.
Openings go up as they are approved and come down when they are filled. If nothing is listed, that is the board being current, not stale.
See the job boardApply
Through the board if a role fits, or directly if none does. Send something you made: a project, a repository, a piece of writing. A CV is fine but it is rarely the interesting part.
Conversation with the team
How you think, what you have built, and whether the way we work suits the way you work. Both directions.
A real problem
Not a puzzle. We are more interested in how you reason about an ambiguous brief than in whether you memorised an algorithm.
Offer
Terms in writing, questions answered honestly, and a start date that works for you.
What do you look for in candidates?
Skill, curiosity and the ability to work with an unclear brief. Most of what we do starts as a vague sentence from someone who is not technical, so asking the second and third question matters as much as what you can build.
What is the stack?
Mostly Python on the backend. More useful than the list: the AI work sits inside the application rather than beside it, so it has to ship somewhere a team can maintain.
Do you take fresh graduates and interns?
Both. We have run frontend, testing and founder’s office internships, and hired people straight out of university. What matters is evidence you have built something and can explain the decisions you made.
Where is the team?
Indore is home, and the team is spread across India working remotely. Discovery and handover go better in a room together, so some travel comes up whichever city you are in.
Is every role technical?
No. Product, design, growth, sales and the founder’s office all appear on the board. The common requirement is being able to sit with a half-formed problem without needing it tidied up first.
How do I ask about campus placements?
Write to hello@vibencode.com with your institution and the timeline you are working to.