We build.
We ship.
We own it.
Jyotvira is a product engineering studio. We don't have account managers, project coordinators, or "delivery teams" insulated from the real work. Everyone here touches code, understands the product, and is accountable for what ships.
What you're actually signing up for
Not a company description — a description of what the day-to-day actually looks like.
You own the problem, not just the ticket
There's no PM handing you a requirements doc that someone else thought through. You'll be in the room (or the call) when the problem is being understood. You'll have opinions on the scope. You'll push back when the requirement doesn't make sense operationally. That's expected — not exceptional.
You'll work across the full stack
This isn't a team where a "frontend" engineer never sees a database query. You'll build features end-to-end. You'll understand the data model behind the UI you're building. You'll read production logs. Specialisation comes with depth — but breadth is the foundation.
You'll see your work deployed and used
We don't hand off to "operations" at launch. The code you write ships to production, gets used by real businesses, and you'll be part of the feedback loop when something works well or needs to change. That's the fastest way to grow as an engineer — and it's non-negotiable for us.
You'll work directly with the founder
Architecture decisions, product tradeoffs, scope calls — you'll be in those conversations, not briefed on them after the fact. This is a small team. The feedback loop is short, the accountability is real, and the learning rate is proportional.
What we look for
Not a checklist of technologies. These are the traits that predict success on this team.
You build things
Projects outside work. Experiments. Things that didn't ship but taught you something. We care more about evidence of building than credentials about studying it.
You ask why before how
The requirement exists for a reason. You want to understand that reason before you start building. You'll push back on a feature if you think it won't actually solve the problem.
You finish things
Half-built features are more expensive than no feature. You take things to done — production-deployed, monitored, with a handover that someone else can maintain.
You communicate clearly
In writing. Asynchronously. Without requiring someone to pull a status update from you. Clear communication at a small company is a load-bearing skill.
You read production like a user
You care what happens after deployment. You read error logs. You think about what breaks at scale before you ship. You treat production like a place real people are depending on.
You're curious about AI
Not hype-curious. Operationally curious. You want to understand where LLMs actually change an outcome in production, and where they add cost without changing anything.
Current openings
We hire when we find the right person, not when we have a head count to fill.
Full-Stack Engineer (PHP / Laravel)
You'll work across AnnvoraPOS, Catalog Builder, and CoachingManager. Laravel-heavy, with frontend involvement in Alpine.js and Tailwind. You'll own features end-to-end and be involved in production support.
AI / Backend Engineer (Python / Node.js)
You'll work on AI-powered systems: Contract Intelligence Engine, Business Communication AI, and the Tourism Call Intelligence platform. LLM integration, streaming, prompt engineering, and production deployment are central to this role.
Open Application
If you don't fit the above roles but build things, ship products, and want to work at this kind of company — send your work. A GitHub profile, a side project, something you built that's live. We'll look at it seriously.