Finkraft is a B2B SaaS platform that helps enterprises recover what they're owed from the complexity of modern business travel and finance - starting with GST input tax credit recovery and reconciliation. We work with 100+ enterprises today, including Fortune 500 corporates, global consulting firms, airlines, embassies, and travel ecosystems.

We're now building something larger: the finance operating system that sits between booking, identity, invoicing, payment, and reconciliation across the UAE and the wider GCC.

Why this matters now :

Over the next 12-24 months, every business in the UAE moves to structured e-invoicing. Thousands of hotels, travel companies, corporates, banks, and payment providers will need to exchange invoices, payments, identities, and compliance records in real time - and they'll need something that makes that whole flow work end-to-end.

Most companies see compliance plumbing. We see the chance to build the rail that moves money, settles invoices, and creates the trusted audit trail underneath the entire ecosystem. We have the customers, the regulatory tailwind, and a working architecture. What we need now is the architect who can lead

The role :

You'll be our Principal Architect - the person who owns the architecture end to end, leads the engineering team executing on it, and is the primary technical voice in conversations with stakeholders across product, business, and leadership.

This is hands-on by design. You'll spend the first stretch close to the build, getting the next generation of the product into production and setting the technical bar. As we scale, you'll grow the team, the platform, and the depth of your architectural ownership.

Requirements :

Technical experience we look for :

- Depth across most of these, working familiarity across all. We care more about how you reason than which tools you've used - but you should have used most of them at production scale.

- Languages and runtimes :

i. Go and / or Python at production scale.

ii. Comfort moving between typed and dynamic languages.

iii. JavaScript / TypeScript familiarity for adjacent work.

- Cloud and infrastructure :

i. AWS in production - ECS / Fargate, Aurora PostgreSQL, SQS, Lambda, KMS, IAM, CloudWatch, S3.

ii. Infrastructure-as-code (Terraform or CloudFormation).

iii. Comfort with cloud cost modelling and capacity planning.

- Data and storage :

i. PostgreSQL at depth - schema design, query performance, transactions.

ii. Redis for caching and queues.

iii. Event stores, message queues, and the design choices between them.

iv. Familiarity with MongoDB or other NoSQL stores is useful.

- Architecture :

i. Event-driven systems, API-first design, integration architecture, distributed systems, microservices and modular monoliths (and the judgement to pick the right one).

ii. Idempotency, retries, audit trails, eventual consistency.

- Domain technology (preferred) :

i. Payments systems, virtual card / VAN orchestration, settlement and reconciliation, e-invoicing (Peppol, UBL), ERP or accounting integrations, identity and KYC flows, tax-tech, or comparable money-movement and compliance systems.

- Engineering practices :

i. CI / CD, DevSecOps, automated testing, code review, observability and monitoring, secret management, dependency and container scanning.

ii. Track record of building these into the team from day one - not bolting them on later.

- AI-native engineering :

i. We expect our architects to leverage AI aggressively but responsibly.

ii. You should have practical experience using tools such as Claude Code, Cursor, Copilot, Sonar, Semgrep, Playwright, and modern CI/CD workflows to accelerate development, testing, documentation, code review, and operations.

- We are looking for builders who can create engineering leverage, not simply write more code.