Internally this role sits in our Solution Delivery Management team, and the contractual title is Solution Delivery Manager.

Why this job is exciting

As a Solution Delivery Engineer you are the technical owner of how our biometric solutions land at a customer — identity document and passport issuance, national elections, criminal investigation, border crossings and e-gates, and identity verification for banks and enterprises. You design the solution, write the migration code and the tooling that moves real data into it, prove it works, and then explain all of it to the people who have to sign it off.

This is a hands-on engineering role with a customer in the room. Your weeks are spent in schemas, APIs, logs and analyses — and in making that work legible to somebody non-technical. It is also the role with the widest view of what we build: you work across our solution clusters, R&D, product, support and pre-sales, and you are the person a customer's technical lead calls first.

You start broad and then go deep. In your first months you get across all of our solution clusters. Around month three you pick one, with your manager and that cluster's solution owner, and by the end of your first year you are the delivery-side technical reference for the solutions in it.

This is a medior to senior position — T3 to T6 in our career framework. Where you land depends on what you actually bring rather than on years served, and a candidate can come out above or below that range. The coding is not incidental at any of those levels: you will write efficient code for data migrations, build custom tools, debug intricate integration problems and think algorithmically about performance. You get real autonomy, with a support framework around it.

You'll have the opportunity to

Within one month, you will…

• Get across our solution clusters and the solutions in them — Governmental ID and phygital identity (ID issuance, voter management) · Criminal Justice and Law Enforcement (ABIS for criminal investigation) · Border Control and Passenger Facilitation (border control platform, smart corridors and e-gates) · Enterprise IDV (IDV platform and toolkit) · Embedded Biometrics — and understand which customer problem each one answers
• Be able to explain biometrics without notes — enrolment, verification, identification, templates, matching, accuracy, and how to choose a threshold for a use case
• Learn how we handle biometric data, and what that obliges you to do before you touch any dataset
• Shadow a live customer training, then co-deliver one
• Improve at least one piece of our technical material you found unclear, and get the change merged

Within three months, you will…

• Know the APIs of our solutions and how systems integrate with them
• Know our solutions in depth — not only the parts your own project touches — and be able to look at two environments and say what differs between them and what that difference will cause
• Work hands-on with our migration tooling on test data
• Take your first project as primary engineer — the customer's technical counterpart, owning the technical side end to end, and the acceptance authority for the technical solution
• Choose the solution cluster you will specialise in, with your manager and that cluster's solution owner
• Run your first live data migration alongside a senior, and produce a quality analysis and a deduplication analysis on real data
• Run a gap analysis and a sizing, and support a proof of concept
• Deliver a customer training yourself

Within six months, you will…

• Go deep on your cluster — how its solutions are scoped, sized and sold, not only how they are deployed, and what customers usually push back on
• Deliver customer training solo, theory through hands-on
• Write the documents a project is accepted on — Factory Acceptance Test, quality analysis, deduplication report — and explain to a customer what the numbers mean for the decision in front of them
• Plan, run and report a migration without a senior alongside
• Answer the accuracy question properly: where we sit in the independent benchmarks, and what that means for this customer at this volume
• Work our Solution Management tool set unaided

Within one year, you will…

• Be the delivery-side technical reference for your cluster's solutions — the person consulted when one of them is being scoped for a customer, and the one who trains others on it
• Run several technical implementations in parallel, conception to deployment
• Be the technical advisor both customers and colleagues come to
• Lead complex biometric migrations and integrations with third-party platforms
• Feed what you learn on projects into our product roadmap

Requirements

About you

You are an engineer who likes customers. You are comfortable being handed an unclear problem, a half-documented third-party system and a deadline, and working out what is really being asked before you design anything. You write code to solve your own problems — migrations, tooling, automation — and you can read somebody else's code and schema without being walked through them. You would rather write the decision down than explain it three times.

What you need on day one

Five things. We check all five in the interview, and they are the bar at both levels we hire this role at — what changes between medior and senior is the depth we find, not whether it is there.

1. An engineering foundation you use daily. Programming in at least one mainstream language — Java, C#, Python, Go or similar — with recent hands-on work you can talk through in detail. Working SQL, and the ability to read a schema you did not design. Comfort taking a real dataset apart to see what it is telling you.
2. Turning a customer need into scope, assumptions and risks. What is in, what is missing, what we are assuming, what could go wrong — before anybody designs anything.
3. Designing a solution end to end, deciding under uncertainty, and writing both down. Data model, use cases, roles and permissions — and the decisions behind them, recorded so the next person can see why.
4. Keeping everyone aligned on what is in, out and changed — including saying no. With options attached, to a customer as readily as to a colleague.
5. Explaining it to a business audience, in English. Spoken and written: analyses, diagrams and presentations somebody else can act on without you in the room.

Also: a university degree in a technical field — computer science, engineering, mathematics or similar. A business or economics degree works where it comes with real hands-on engineering experience. Flexibility and willingness to travel on short business trips.

Nice to have

The ecosystem we work in. Nobody arrives fluent in all of it, and none of it is a filter.

• Kotlin and other languages from our stack · REST API design and integration · message queues · CI/CD pipelines
• AWS or a similar cloud · GitLab, Docker, Kubernetes · Keycloak
• Exposure to biometric solutions, platforms or SDKs
• Criminal case management, document issuance, ICAO interchange formats
• Conference talks, webinars, running technical workshops
• Fluent in English and Malaysian. Spanish, French, Arabic, Mandarin or another world language is a plus

Location and travel

Location: Kuala Lumpur, hybrid. Short business trips to customers; no fixed travel quota.

Benefits

Compensation

At Innovatrics we offer competitive compensation aligned with role level, experience, skills and location.

Salary: €2,200 – €3,700 / month depending on the assessed seniority level.

Full benefits package: https://careers.innovatrics.com/

Interview process

The whole process is conducted in English.

1. Application - Submit your CV.
2. Few Quick Questions - If your CV interests us, we will reach out with a few questions. Be ready to send one piece of technical writing you produced yourself — a solution design, a gap analysis, a test or FAT document, a runbook, a decision record. One document is enough, customer details removed; a redacted extract is fine.
3. Recruiter screen — 30 minutes. Your background, what you are looking for, and the practicalities.
4. Take-home assignment. We send you the brief after the screening call, with a week to complete it and around three hours of your own time expected. You present it at the interview and talk us through it — there is no separate marking step beforehand.
5. Team interview — 90 minutes. A short self-introduction, your assignment (15 minutes plus questions), a walk through your experience, and a technical conversation with members of the team you would be working with.
6. One or two hands-on technical tasks — the same day. Worked through with the team rather than alone in a room. The second one runs only if we still have a question after the first.
7. CARES interview — 30 minutes. Values fit, with our CARES committee: Collaboration, Accountability, Respect, Excellence, Shared Mission.
8. Reference checks and background verification.

You are welcome to ask for additional conversations with anyone on the team.