Work with us
Contract engineering work, described honestly
Repomanta Digital Lab engages contract engineers per project. This page tells you exactly what that means, including the parts that might put you off — because finding those out later wastes your time and ours.
Who we want to hear from
Automation & integration engineers
n8n or Make.com to a professional standard, plus real API work. You should be able to explain idempotency and why a naive retry duplicates records.
AI / LLM engineers
Retrieval pipelines and structured extraction. You should care more about the evaluation set than the prompt.
Backend & data engineers
Python or Node, SQL that is not generated for you, and the patience for migrations and reporting pipelines.
Full-stack developers
React and TypeScript, with enough taste to build an internal tool that is not painful to use.
What this is, and what it is not
Both columns are true. Read the second one properly.
Paid at your rate, on stated terms
You quote, we agree it in writing per work order, and invoices are paid within the stated terms. No trial work that is not paid.
Real ownership of a piece of work
You are named on the engagement internally, you talk to the client where the work needs it, and you are trusted with the design rather than handed tickets.
No timesheet theatre
Hours logged against an agreed cap, reported honestly. Nobody is monitoring your screen or counting keystrokes.
Not employment
These are contract engagements, per project. No salary, no benefits, no guaranteed volume. You are responsible for your own taxes and registrations.
Not a steady pipeline, yet
Work comes as engagements land. If you need predictable full-time income right now, this is not that, and we would rather say so up front.
IP assignment is non-negotiable
Work you do for a client engagement assigns to us at creation, so we can assign it on to the client. If that is a problem, this will not work.
How it goes
01
You send work, not a CV
A repository, a workflow export, or a written description of something you built and what broke. We read the second part most carefully.
02
A conversation
Forty-five minutes about how you approach a problem. No whiteboard algorithms — the work does not involve inverting binary trees.
03
A small paid task
Real, scoped, and paid at your rate. We would rather see you work than test you.
04
Agreement, then work
A subcontractor agreement including confidentiality and IP assignment, signed before any client access. Then work as it comes.
Straight answers
Is this employment or contract work?
Contract, per project. Repomanta Information Technology Services engages contractors under a written subcontractor agreement — there is no salaried position on offer, and we are not going to describe one as though there were. You invoice us, you handle your own taxes and registrations, and you control how you work.
How much work is there?
It varies with engagements landing. Some months there is a full-time-equivalent piece of work, some months there is none. If you need guaranteed volume, take a role somewhere that can promise it — we cannot, and pretending otherwise would waste your time.
Do I have to be in the Philippines?
Preferably, mainly for timezone overlap with our clients in Australia and Asia-Pacific, and because contracting is simpler domestically. Elsewhere is possible for the right person, but the working-hours overlap has to actually work.
What does the IP assignment mean for me?
Work you produce for a client engagement belongs to us at the moment you create it, so we can validly assign it to the client. It does not touch anything you built before, or anything you build on your own time — those are yours, and the agreement says so explicitly. You just have to disclose any pre-existing or open-source components you bring in.
Can I use AI tools?
Yes, and we do. You have to disclose which ones, confirm no client data went into a service we have not approved, and stand behind the output as your own work. A generated solution you cannot explain is not acceptable — but that was already true before the tools existed.
Send something you built
A repo, a workflow export, or a paragraph about something that broke and how you fixed it. That tells us more than a CV does.
build@repomanta.com