A division of Jiranisoko Market Ltd
Investor & Group
Jiranisoko Tech
Request Proposal

Company

Senior engineering, based in Eldoret

We staff engagements with principal and senior engineers rather than with volume. That shapes who we hire, how we develop them, and what we can offer someone who is already good.

How to reach us

What you would actually work on

Core banking migrations, payment rails carrying real money, agent systems inside regulated estates, and platforms our own group depends on to trade. Not a backlog of tickets against someone else's architecture.

Jiranisoko Tech Solutions is the technology division of Jiranisoko Market Ltd. We build for external clients, and we operate the group's own systems — which means the standards we publish are enforced on us nightly, by software we cannot walk away from. Engineers here carry an on-call rota for something real, and they get the architectural authority that ought to come with it.

Why join us

The honest version. These are structural facts about how the firm is set up, not perks.

Seniority, not volume

  • Engagements are staffed with principal and senior engineers
  • You are named to a client, not pooled behind an account manager
  • No billable-hours target dictating how you solve a problem

Real systems, real consequences

  • Production payment rails, auction concurrency, regulated data
  • An on-call rota for software the group actually trades on
  • Post-incident reviews that are published internally, not buried

A published standard

  • Architecture decision records on every engagement
  • Security scanning that fails a build rather than warning
  • An engineering ladder with written expectations at each level

Based in Eldoret, working globally

  • Clients across East Africa, the Gulf, Europe and the UK
  • A working day that overlaps those markets without night shifts
  • Outside the Nairobi churn, which is why our teams stay together
Before launch

This section states structural facts only. If you want to advertise a package — leave, medical cover, learning budget, equipment — add it here once HR has confirmed what is actually on offer. Advertising a benefit that does not exist is discovered at offer stage, with the candidate you most wanted.

The engineering ladder

Four levels, with written expectations. Progression is about the scope of what you can be left to own, not time served.

Engineer
Delivers scoped work within an established architecture, with review. Growing depth in one discipline.
Senior engineer
Owns a component end to end, including its tests, observability and runbook. Reviews other people's work.
Principal engineer
Owns the architecture of an engagement and is answerable for its non-functional characteristics. Writes the decision records, including the options rejected and why.
Practice lead
Accountable for technical quality across one of the six disciplines, and for the engineers working in it.

How we hire

Four steps, roughly two to three weeks. No unpaid take-home project, no whiteboard algorithm round, and we tell you where you stand at every stage.

1

Apply to a role that matches what you actually want to do next. A short note beats a long CV.

2

A conversation with the practice lead about systems you have built and the hardest problem you have owned.

3

A paid technical session on a realistic problem, timeboxed, with one of our engineers working alongside you.

4

An offer with the level, the scope and the package written down, and time to consider it.

Open positions

Nothing is advertised at the moment. That is not the same as not hiring.

No advertised vacancies right now

We would still like to hear from principal and senior engineers, particularly in payments, cloud architecture and applied AI. Tell us what you have built and the hardest problem you have owned; we keep speculative applications on file and come back to them when a role opens.

Write to us

careers@jiranisokotech.co.ke — tell us what you have built and the hardest problem you have owned.

The roles we hire for

The shape of the work here, whether or not any of it is advertised today. When one of these opens it is approved, funded and posted on the job board — and you apply to it there.

Senior Payments Engineer

  • Senior engineer
  • Eldoret, Kenya
  • Hybrid — three days on site
  • FinTech & Payments

Own the money-movement layer on client engagements: mobile money and card rail integration, reconciliation that balances, and cardholder data architectures scoped for audit from the first design session.

What you would own

  • Design and build payment integrations across mobile money, card and bank rails
  • Own idempotency, callback handling and the unhappy paths that define payment work
  • Build reconciliation that proves itself rather than being inspected by hand
  • Keep PCI-DSS scope minimal by design and evidence it for assessment

What we are looking for

  • Five or more years building transactional systems in production
  • Direct experience of a payment rail integration you were on call for
  • Fluency in one of .NET, Laravel or an equivalent server framework
  • Able to explain a reconciliation break to a finance team without jargon

Not advertised today. See what is open.

Principal Cloud Architect

  • Principal engineer
  • Eldoret, Kenya
  • Hybrid — three days on site
  • Cloud & DevOps

Own the target architecture on cloud engagements and be answerable for its non-functional characteristics. Write the decision records, including the options rejected and why.

What you would own

  • Landing zone, identity and network topology design across AWS, Azure and GCP
  • Migration wave planning, cutover rehearsal and rollback design
  • Architecture decision records that survive a client security review
  • Technical mentorship of senior engineers on the engagement

What we are looking for

  • Eight or more years in infrastructure engineering, including cloud migration you led
  • Depth in at least one major cloud and working knowledge of a second
  • Infrastructure as Code as a default rather than an aspiration
  • Willing to recommend against a migration when the case is not there

Not advertised today. See what is open.

AI Engineer — Agentic Systems

  • Senior engineer
  • Eldoret, Kenya
  • Hybrid — three days on site
  • AI & Automation

Build agent systems that take real actions inside client estates, and build the containment around them first: tool boundaries, permission scoping, approval gates and full action audit trails.

What you would own

  • Agent topology, orchestration and tool boundary design
  • Evaluation harnesses and regression suites that gate deployment
  • Retrieval architectures that inherit the source system permission model
  • Human-in-the-loop approval workflows on irreversible operations

What we are looking for

  • Production experience shipping an LLM-backed system real users depended on
  • Strong Python, and comfort with the evaluation problem rather than only the prompt
  • Security instincts: you treat a retrieval index as an access control surface
  • Able to say when retrieval augmentation beats fine-tuning, and show the numbers

Not advertised today. See what is open.

Come and build things that matter

If the work described here is the work you want to be doing, start a conversation. We answer every application from a person, not a tracking system.

Get in touch How we work