Roles & skills
A short list, because a long one would be a lie
Five roles we actually staff, in areas where the work has been delivered. Not every technology that exists, and not a menu designed to match whatever you searched for.
UTC+8. Full working-day overlap with Australia, Singapore, Hong Kong and Japan. Morning overlap with Europe and the Middle East, evening overlap with the US west coast. The expected hours go into the engagement in writing.
The roles
Automation & integration engineer
Coren8n · Make.com · REST/GraphQL · webhooks · queues · Postgres
Builds the workflows and the connective tissue between systems. Thinks in failure modes: retries, idempotency, rate limits, what happens when a record does not match.
AI / LLM engineer
CoreOpenAI · Anthropic · RAG · vector search · evals · structured output
Builds extraction, classification and retrieval pipelines, and — the part that matters — the evaluation set that proves they work on your data.
Backend & data engineer
CorePython · Node · SQL · ETL · reporting pipelines
Data plumbing, migrations, and the reporting layer on top. The work nobody demos and everybody depends on.
Full-stack developer
React · TypeScript · Tailwind · Vite · Node · Postgres
The interface on top of an automated process: internal tools, dashboards, client portals, marketing sites.
QA & process documentation
Test plans · runbooks · SOPs · handover packs
Writes the runbook and tests the exception paths. This is the role most outsourcing quietly omits, and the reason most handovers fail.
Seniority, described by what they can do
Years of experience is a poor proxy. These describe the level of ambiguity a person can absorb.
Senior
Takes an ambiguous business problem, decides what should and should not be automated, designs the architecture, and is accountable for the outcome. Works unsupervised and will tell you when your idea is wrong.
Mid
Takes a defined scope and delivers it, including the exception handling. Asks the right questions early rather than guessing. Needs a review, not supervision.
Support
Executes well-specified tasks, monitors runs, handles documentation and first-line triage. Cost-effective for volume work under a senior's design.
Rates are not published, because a rate without a scope is meaningless. How pricing works.
What comes with every engagement
- A named person, not a pool. You know who is doing the work and can talk to them.
- Written IP assignment before any access is granted, so deliverables are cleanly yours.
- Confidentiality obligations covering your data and your own clients' data.
- Weekly written report: shipped, blocked, hours against cap.
- A two-week paid trial before any longer engagement — you judge the output, not a CV.
- Replacement on notice if the fit is wrong, without renegotiating the whole engagement.
What we are not
- A fifty-seat delivery centre. We take on fewer engagements than an agency and will say so on the first call.
- 24/7 follow-the-sun coverage. We work Philippine business hours with an agreed overlap.
- Roles outside the list above. If you need a mobile developer or a data scientist, we will tell you to hire elsewhere.
- Anyone starting before the subcontractor agreement is signed. That is not a delay we will shortcut.
Straight answer
How the bench actually works
Repomanta Information Technology Services is led by its principal engineer, who does the engineering and the client-facing work directly. Additional capacity comes from a vetted network of contract engineers, engaged per project under written agreements that include confidentiality and a present assignment of intellectual property.
There is no large permanent bench, and this page does not pretend otherwise. Nobody is allocated to your engagement before their agreement is signed, because the IP chain is what allows us to hand you ownership of the deliverable.
The trade-off is real and worth stating: fewer simultaneous engagements, and we are the wrong choice for a large fixed-capacity contract. In exchange you get a named engineer who is accountable for the outcome rather than an account manager relaying messages to a pool.
Straight answers
How large is the bench, really?
Repomanta Digital Lab is small and deliberately so. The principal engineer does engineering and client-facing work directly, and additional capacity comes from a vetted network of contract engineers engaged per project under written agreements including IP assignment. There is no large permanent bench, and this page does not claim one. For the engagement sizes we take on, one accountable engineer beats a rotating pool.
Why are there no rates on this page?
Because a rate without a scope is meaningless — the same seniority costs differently depending on allocation, term, timezone overlap and what the work actually is. You get a real number in a written quotation after a thirty-minute scope call, and both the call and the quotation are free.
Can we interview the engineer before committing?
Yes, and you should. You also get a two-week paid trial on real work before any longer engagement, which tells you far more than an interview does. If the fit is wrong at the end of it, you walk away with the work done and no further obligation.
What timezone overlap can we expect?
Philippine Standard Time, UTC+8. That is a full working-day overlap with Australia, Singapore, Hong Kong and Japan; a morning overlap with the Middle East and Europe; and an evening overlap with the US west coast. The expected overlap hours go into the engagement in writing rather than being assumed.
Who manages the engineer day to day?
You do, on a dedicated or staff-augmentation engagement — they work in your tools, your standups and your board. We handle the contracts, the IP chain, continuity and replacement. On a fixed-fee project we manage delivery and you review against acceptance criteria.
Tell us the role and the work
You get a written quotation with the model, the named person, the start date and the notice period. Then a two-week paid trial before anything longer.
Request a quote