Small team, unusually large surface

What working here is actually like

We are a small team building an unusually large surface: a lifecycle platform, an MCP layer, a multi-tenant permission model, and the products that run on top of it. That means the work is broad and the ownership is real — there is nobody to hand a half-finished thing to.

It also means we are honest about the trade-off. If you want a narrow, well-defined role with a large team around you, this is not that. If you want to see a feature from requirement to production and then answer the ticket about it yourself, keep reading.

How we work

• Written thinking. Decisions are written down with the reasoning attached, because the next reader may be a colleague who joins in a year — or an AI agent tomorrow.
• Small changes, verified. We prefer a change that ships today with a test over a rewrite that lands next quarter.
• Bahasa Indonesia internally, English in the product. Both matter; neither has to be perfect.

Where we expect to hire

We are not running a permanent open-roles page we cannot honour. These are the areas where a strong person would change what we can do — if that is you, write to us before a role is posted.

Internships and campus

We work with Indonesian universities and vocational schools through the education programme, and we take a small number of interns who contribute real, reviewed changes. If your campus wants to use Oprex for coursework, that is a conversation we always say yes to — see Education.