A cycle is reviewed in parallel by several people, each looking through a single lens — access, isolation, integrity, pipeline. Depth beats breadth per head.
Every serious finding is checked against the actual code before it reaches a report. A false positive costs a client’s trust, so we spend the time.
Severity, why it exists, what it risks, the specific fix — and what you could not verify. Writing is half the job, not the paperwork after it.
Anything that appears twice becomes an enforced check you build. The aim is to make your own findings rarer, which is an unusual incentive to work under.
One lens, read properly, for a whole cycle. You get to be the person who actually knows how a system behaves rather than the person who closed the most items.
Guardrails enforced versus written, findings per unit of new work — the same numbers the client sees every cycle. No performance narrative required.
Client work in businesses that are actually running on the thing you are reading. Small team, so the range arrives early.
If none of these is recognisably you, the honest answer is that you would be bored here within a quarter.
Engineers who would rather read a system than add to it
People who can write a finding an owner understands without a translator
Anyone comfortable saying “I could not verify this” in writing, to a client
Builders who want their own findings to get rarer, not their seat to get safer
No panel, no personality test, no take-home project built to a brief. We look at work you already care about and we read what you write.
Both are in Kochi, full time, and both start with the same thing: one thing you built, written the way we write them.
Build the harness, not the model: context that reaches the agent, routing keyed to a measured quality bar, and evaluation that says whether a cheaper model still cleared it.
Own features end to end inside real businesses — data model, API, interface, and the gate that decides whether your change is allowed to merge.
Those are the two roles open right now. If neither is you but the work is, write to us anyway — we have hired people for roles that did not exist until they asked.
Send us one thing you have built that you are proud of — shipped, half-finished, or purely for your own amusement. Tell us what it is, why you made it, and the part you would defend in a room. That tells us more than a CV, and we reply either way.
Not a role — a project? Talk to us instead.Applications go to hey@tghtech.com. One of us reads them, not a queue.
