Careers · Bengaluru, India
Come build systems people actually run.
A small engineering team building AI automation, FinTech and trading infrastructure for clients worldwide.
- Own modules end to end
- Ship to real users, same week
- One team, no layers
Inside the work
Small teams, shared screens.
Most days are two or three people around one problem, in an office in Indiranagar, on a clock that often belongs to a client somewhere else.
Life at THWorks
What the week actually looks like.
A small studio takes on client work in a particular way. This is the honest version of it, including the parts that are demanding.
You own the module
From the schema to the deploy. No hand-off, no queue of approvals in between.
Review is a conversation
Code review argues with the decision, not the person who made it.
It goes to real users
Client work, in production, with people on the other end of it the same week.
Nobody here is more than one conversation away from the person who decides. That is the whole advantage of being this size.
Perks and benefits
How we set you up to do your best work.
The arrangements are simple and there are not many of them, which is what being a small studio actually buys you.
Client-aligned schedule
Your hours follow the client you support, which for US work means evenings or nights. The window is fixed and agreed up front — no surprise shifts.
Performance bonuses
Paid quarterly against outcomes that were written down before the quarter started.
Team retreats
One offsite a year, somewhere worth the flight. Past trips: Goa, Coorg and Hampi.
A new stack most quarters
Client work moves across AI tooling, trading systems and web. You will not spend three years in one framework unless you want to.
Monthly one-to-ones
A standing conversation about your growth, with specifics rather than "be more proactive".
A decision either way
Screening, a practical interview, then an answer. We would rather tell you no in a week than leave you waiting on a maybe.
Open roles
1 open role
Stay safe. We only ever write from @thworks.org addresses, and we never ask a candidate for money, bank details or documents at any stage of hiring.
Applying here
What to expect if you apply.
How applications are handled, what the work is like, and how to tell a real message from us apart from a fake one.
Yes. The listings above are the roles we are actively filling, not the only ones we would open. If you can point at something you built and explain the decisions in it, send that — an unsolicited application with real work attached is read more carefully than a matching CV without one.
You get an answer either way. A no is still a reply, and it comes without you having to chase it — being left to guess is the part of applying for a job that we think is worth fixing, and it is the one commitment we make about the process.
You own a module rather than a ticket queue, and you own it far enough to make decisions inside it. Review is a conversation rather than a gate, and what you write goes to real users on a real schedule — which is the part that makes the other two matter.
No. A good chunk of what we do is trading and financial infrastructure, and most people learn that here rather than arriving with it. What does not transfer easily is the habit of writing software that has to be correct when it fails — if you have that from anywhere, the domain is learnable.
We only ever write from @thworks.org addresses, and we never ask a candidate for money, bank details or documents at any stage of hiring. If you receive anything asking for either in our name, it is not us — please forward it to contact@thworks.org so we can report it.
Open application
Nothing fits today? Send it anyway.
We are a small team and the list above is short, but it is not the whole picture of who we would talk to. Tell us what you build and leave a CV.