Founding CTO

๐Ÿข Finkraft ยท all Finkraft jobs
๐Ÿ“ United States
๐Ÿ“… Posted 2026-08-23 ยท via Himalayas
๐Ÿท Chief-Technology-Officer,CTO,Head-of-Engineering,Engineering-Management,Fintech-Engineering,Founding-CTO,Co-Founder-and-CTO,Technology-Leadership
Apply on original site โ†—

This is a remote position.

Finkraft .ai

Founding CTO

Founding technology leader ยท Head of Engineering | Bengaluru ยท UAE ยท Hybrid | Full-time

About Finkraft

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 technology leader to build it.

The role

You'll be our founding technology leader โ€” the person who shapes the engineering function, owns the architecture, and partners with the founder on the calls that decide what Finkraft becomes.

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 your own seat.

What you'll own
-
The architecture and engineering of the platform โ€” across e-invoicing, payments, identity, reconciliation, and the integrations that connect to banks, ASPs, and hotel/travel systems

-
The engineering team โ€” hiring, structure, levelling, and the standard everyone is held to

-
Production reliability and security for systems that handle money, tax-critical data, and enterprise customer information

-
Engineering velocity and quality โ€” shipping fast without shipping fragile, with the disciplines (testing, code review, security gates, observability) that make that real

-
Technical strategy that ladders to commercial and product outcomes โ€” and the ability to explain those trade-offs to a CFO, a salesperson, and a junior engineer with equal clarity

-
Partnership with the founder on company direction, customer conversations, and the technical narrative we take into investor and partner rooms

Your first challenge

Within your first 90 days, we expect a production-ready v1.0 of the UAE Finance Operating System, including e-invoicing orchestration, integrations, payment workflows, and a handover-ready engineering foundation.

The objective is not a demo. The objective is a platform that customers can trust.

Who you are
-
You have a decade or more in engineering, with the most recent years leading or co-leading high-stakes builds in fintech, payments, banking, ERP, e-commerce, or another domain where the system has to be right

-
You're a player-coach. You've owned production systems end to end, and you still get into the code when the situation calls for it โ€” you haven't moved so far from the work that you can't review a pull request

-
You've recruited and built a team. You can spot strong engineers, lift the bar, and create the conditions for them to do their best work

-
You've shipped at production scale on AWS (or equivalent) and have opinions โ€” defensible ones โ€” about when to use what

-
You're comfortable with ambiguity, founder-level urgency, and making calls before every piece of information has arrived

-
You think in trade-offs, not absolutes โ€” and you've built the kind of documentation and team depth that lets your w

โ† All remote jobs