Help build Vuluru One.
We’re a small, early-stage company building bookkeeping software for small businesses, and we run our own books on it. We’re looking for a few people who care about small businesses and about getting the details right.
If that’s you, I’d like to hear about your work. — Jason
What would it take to trust this draft?
Imagine Vuluru One proposes a supplier bill. The interesting work goes beyond generating an answer.
Get the context right.
Which supplier, document, and business records belong together?
Make the reasoning visible.
Can the person reviewing it see where the proposal came from?
Respect the decision.
What happens when they accept, edit, or reject it?
Where you could help.
These are areas of work, not advertised vacancies. Use them to tell us where your experience and interests fit.
Engineering
Make connected work dependable. Build the systems behind shared business records, agent proposals, and human approvals. The work spans Rust, Postgres and TypeScript, and the boundaries between them.
How do you make a complex workflow reliable—and know when it isn’t?
See what’s built ↗Product & design
Make consequential work understandable. Help an operator see what changed, why a draft was proposed, and what accepting it will do. Turn complex accounting and operational workflows into clear decisions.
How do you give someone clarity without hiding the details they need?
Explore the product ↗Go-to-market
Connect the product to a real need. Understand how businesses work today, where handoffs break down, and what it takes to change systems. Help turn those conversations into useful positioning, partnerships, and customer relationships.
How do you learn what a customer needs before deciding what to promise?
See what’s built ↗
How we work.
Try a small version. Let the evidence challenge your first idea. Know when to keep going and when to change course. Good judgment matters as much as a bold starting point.
Start with the person doing the work.
Understand the workflow and the stakes before deciding what to build.
Make the work inspectable.
Explain decisions, test assumptions, and surface uncertainty so others can follow your reasoning.
Think across boundaries.
A change in purchasing can affect inventory and accounting. Follow the consequences beyond one screen or service.
Show us how you think.
A short introduction is enough to start. Tell us which work interests you and share something you’ve built, improved, or learned. A link or a written example is welcome.
A useful first note
The kind of work you’d like to contribute.
One example of a problem you helped solve—and your part in it.
Your location, availability, and any working arrangements that matter to you.
We’ll read your note and reply if there’s a fit. Founding-team roles include equity, on terms set out in a written agreement.
Open introductions · No specific job openings are listed on this page.
