KGT Kamathi GlobeISS Technologies Limited
Careers

There are no open roles.

This page exists to say that plainly, and to describe how the team works for anyone deciding whether to write to us anyway.

Openings

Nothing is listed.

The company has no listed openings at present. There is no hidden list, no pipeline of roles awaiting sign-off, and nothing that is about to be posted. When a role opens it will appear on this page, with a description, and this notice will be replaced.

Saying so is preferable to keeping a permanent advertisement up. A page of aspirational roles at a company that is not hiring costs applicants real time, and it tells you nothing accurate about the company. The honest version is short: the team is small, it is not currently growing, and that is the whole state of it.

What follows is here for the case where you want to write regardless. It describes how the work is done, so that the decision to send something is an informed one.

How we work

What the work is actually like.

Not values, but conditions. These are the things that would determine whether this is somewhere you would want to work.

  • The team is small
    Small enough that everyone is close to the product and nobody is insulated from what ships. There is no layer of people who only coordinate other people, and there is unlikely to be one soon.
  • We operate what we build
    The company builds and runs its own products rather than funding other people to. Whoever writes a service is the person who understands its failure modes, and is expected to still be there when it has them.
  • Money handling is treated as serious
    Integer minor units, double-entry accounting, daily reconciliation against the payment provider. Work that touches the money path is reviewed on the assumption that being approximately right is the same as being wrong.
  • The constraints are local and real
    Modest hardware, intermittent connectivity, mobile money rails that behave the way they behave rather than the way documentation says. Products are designed for the conditions of this market, not adapted to them afterwards.
  • Written decisions
    Rules that govern a product are written down before they are relied on. The four rules behind the NdioLa catalogue are an example. A decision that exists only as a shared understanding is a decision that quietly changes.
If you write anyway

What to send.

Speculative approaches are read. They are not always answered quickly, and there is nothing to apply for, so the useful version is short and specific.

  1. Something you built, and what it does
    A link is enough. Working software, a repository, a piece of writing that shows how you think about a problem. We are more interested in one thing you can explain in depth than in a list of technologies you have touched.
  2. What went wrong with it
    The failure you did not anticipate, and what you changed afterwards. Anyone who has run something in production against real payment rails has an answer to this. It is the most informative question we know of.
  3. What you would want to work on here
    Named specifically. The market mechanics, the money path, the settlement sources a question resolves against. This is also the fastest way to tell us that there is nothing here for you, which is a useful outcome as well.
  • Where to send it
    Write to info@kgtlimited.com and mark it for the attention of the directors.
  • What not to send
    Generic applications addressed to no one, and CVs with no accompanying note. Neither gets a reply, and it is fairer to say so here than to leave the sender waiting.
Contact About the company