We are a fast-growing, FinTech company looking for a talented and enthusiastic individual to join our team. We are expanding, making this a perfect position if you would like to have a significant impact on our company’s growth and develop your role and career as the business evolves. You will join a team where your ideas will be welcomed and valued.
You'll work at the boundary between the Insignis platform and the wider sector — partner banks, distribution and white-label partners, introducer and agent firms — and alongside our production engineering teams. Your job is to compress the time from "there's a problem or an idea worth pursuing" to "there's a system handling real money or real users," and to do it so that the teams who'll own it long-term can absorb it without inheriting a liability. You'll spend your time roughly equally between building and being in the room with the people who have the problem.
Role responsibilities
- Embed directly with partners and internal product teams to understand the actual problem — often before it's written down as requirements — and translate it into something buildable.
- Rapidly prototype: integrations against partner APIs, white labelled apps, new deposit-product flows, partner-onboarding tooling, internal capability. At this stage you optimise for speed of learning over architectural purity, and you're explicit about that being a deliberate choice.
- Take the prototypes that prove out into early production — enough robustness, observability, and compliance posture to handle live flows — in close partnership with the production engineers who will own them.
- Own the handoff. Instrument it, document it, de-risk it. A prototype that production can't absorb is a failure, not a success.
- Work inside Insignis's regulatory and operational guardrails —Consumer Duty, FCA SYSC, DORA operational resilience, UK GDPR — and know which constraints bind at prototype stage versus hardening. Pull compliance and ISMS in early, not as a gate at the end.
- Feed learnings back into the platform: what's repeatedly missing, what should become a reusable capability, where the next-generation architecture should go.
Our stack — Azure-native (AKS), Kafka and event-driven architecture, Kong, .NET/C# on the backend, Vue.js on the front end, Auth0 and Entra ID for identity, Salesforce. We've deployed Claude and Claude Code org-wide and expect Solutions Engineers to be force-multiplied by AI-assisted development, not bystanders to it.
You'll thrive here if
- You're energised by ambiguity and by sitting alongside the person with the problem rather than waiting for a ticket.
- You can write production-grade .NET/C# or TypeScript, and are equally happy gluing things together fast in Python.
- You have judgment about when "good enough" genuinely is — and when it categorically isn't, because regulated money is involved.
- You can hold an external partner relationship and an internal engineering relationship at once, without drifting into pure account management or lone-wolf building.
- You ship.
Requirements
- Strong general-purpose engineering in at least one core stack (.NET/C#, TypeScript/Vue), with Python for rapid work.
- A track record of taking something from zero to running in production, ideally in or near a regulated or financial domain.
- Comfort with distributed/event-driven systems, APIs, cloud (Azure ideal; AWS/GCP transferable), containers, and CI/CD.
- Excellent communication; credible and trustworthy in front of partner stakeholders.
Nice to have — FCA-regulated fintech, payments, BaaS or open-banking experience; partner-integration or white-label platform work; familiarity with Consumer Duty, or DORA; DDD, Kafka, Kubernetes.
Benefits of the job
- Competitive compensation
- 25 days holiday (exc. Bank holidays)
- Pension contributions
- Private medical insurance
- Employee health and wellness discounts
- Cycle to Work Scheme
- Monthly team lunches
Working pattern
- Hybrid working pattern in London office, 3 days in the office (Tuesday to Thursday), 2 days remote.
