Working at CreateFuture
CreateFuture is an AI-native consulting partner where people do work that matters and are supported to do it well. We work alongside organisations such as PayPal, adidas, NatWest, FanDuel and Money Saving Expert, building digital products and services that make a difference while always putting people first.
We're a team of creators. We write code, shape delivery, build go-to-market strategies, develop AI solutions and create the practices that support our people. We work side by side with our clients, challenging what's not working and helping them to build the future. Our commitment to craft, quality, and culture has helped us scale to over 600 people in just a few years.
Our UK Benefits
35 days leave (including bank holidays).
- Private medical insurance.
- Enhanced parental and adoption leave.
- Financial coaching + 5% pension match.
- 40 hours of paid learning and development.
View our full list of UK benefits.
CreateFuture is a Great Place to Work-Certified™ company and has won Best Workplaces UK multiple years in a row.
Join us on our journey. Let's create tomorrow, together, today.
About the role and team:
We're assembling a delivery team for a major AI platform programme with a client in a high-traffic, heavily regulated consumer sector. Like a lot of large engineering organisations, they have plenty of AI experiments and no shared foundation underneath them. Our job is to give them one. It needs to be a platform their product teams build on by default, with the governance and cost control a regulated business requires.
The platform has three moving parts, and you'll work across them rather than sitting in one lane.
- The inference control plane. The gateway and routing layer in front of Anthropic, AWS Bedrock, OpenAI and others, plus the failover behaviour that decides what happens when a
provider degrades at peak.
- Orchestration and capability lifecycle. The tooling that lets teams register, discover and reuse AI capabilities and agents, so the tenth team to need retrieval doesn't build it from
scratch.
- Trust, safety and governance. The access controls, audit trail and cost attribution that make the platform defensible to a risk function.
We're looking for five engineers across three levels. At Principal level, you set technical direction for the platform and hold the architecture conversations with the client's senior engineering leadership. At Senior level, you own delivery of a significant component end to end. At mid-level, you build and ship across all three layers alongside more experienced engineers
on the team.
What you'll be doing:
Technical Delivery & Implementation
- Gateway and routing: Build, run and evolve the API gateway and routing layer that connects engineering teams to multiple LLM providers, including the failover and load-shedding behaviour under provider degradation.
- Capability lifecycle: Design and build the orchestration and registration tooling behind a reusable capability marketplace, along with the API design, versioning and promotion
workflows that move a capability from experiment to production.
- Access and secrets: Implement RBAC and OIDC-based access control, and bring real discipline to API key issuance, rotation and revocation.
- Cost and latency: Build caching layers, routing economics and per-team cost attribution. Instrument adoption too, so the client can see which capabilities are earning their keep and
which should be retired.
- Governance by design: Treat auditability, guardrails and safe defaults as part of the build rather than a later hardening pass, so agents running on the platform can be evidenced to a
regulator.
- Engineering standards: Work to a high bar on testing, observability and documentation. Where behaviour is non-deterministic, treat evals, golden datasets, structured outputs and
fallback paths as quality gates.
Client Delivery & Stakeholder Management
- Working relationships: Build credibility quickly with the client's platform engineers, architects and engineering leaders, and hold your position with evidence when you think an
approach is wrong.
- Framing decisions: Explain the cost, risk and delivery trade-offs behind platform decisions in terms the client's business can act on and make pragmatic calls when technical ideals
meet a delivery date.
- Delivery ownership: Plan and prioritise your own stream, estimate your work accurately, manage shifting requirements without dropping quality, and raise risks to timelines early.
- Working in the open: Contribute to discovery, scoping and estimation sessions, and flag missing or contradictory requirements before they become rework.
- Fitting in fast: Work within the client's existing standards, tooling and ways of working where they're sound, and make the case for change where they aren't.
Documentation & Handover
- Documentation as you go: Leave architecture decision records, runbooks and API documentation that the client's own engineers can work from without you in the room.
- Knowledge transfer: Bring the client's engineers along as you build, through code review and pairing, so the platform is theirs to run at the end of the engagement.
- Exit readiness: Treat a clean handover as part of the definition of done from the first sprint, not something arranged in the final fortnight.
Core Technical Capabilities
We're looking for a hybrid profile: software engineering (40%), platform and infrastructure (40%), AI systems (20%). Depth in one, credible in the others.
- Languages: Strong production Python or Go. We mean services you've owned, operated and had to debug under pressure, rather than scripts.
- API gateways: Production experience running a gateway at scale. Kong is our preference. Envoy or Apigee are equally welcome.
- Multi-provider LLM integration: Real integration work across more than one provider (Anthropic, AWS Bedrock, OpenAI or comparable), including the routing and failover design behind it.
- Identity and access: RBAC and OIDC in anger, plus credible API key lifecycle management.
- Platform fundamentals: Cloud infrastructure on AWS, infrastructure as code with Terraform, containers, CI/CD, and observability you built rather than inherited.
- Cost and performance: Caching strategies, latency budgets and cost optimisation for inference workloads.
- Registry patterns: Familiarity with MCP or comparable service-registry and tool-discovery
patterns is a strong signal at any level.
Expectations scale with level. At mid-level we're looking for solid, reliable delivery. At senior, ownership of a component and the judgement to set its standards. At principal, the architectural authority to set direction for the whole platform and the credibility to defend it in front of a client's stakeholders.
Domain & Sector Experience
- Regulated industries: Experience delivering in iGaming, financial services or another tightly regulated sector, where audit, data privacy and compliance guardrails are non-negotiable, is
a real advantage.
- Scale: Comfort with high-throughput, latency-sensitive production systems.
- Contract and consulting delivery: A track record of landing in an unfamiliar codebase and organisation and being productive quickly. This engagement rewards people who can read a
room and get moving without a long ramp-up.
Useful credentials
Track record matters more than certification here, but the following are useful evidence of depth:
- AWS certification at associate level or above, particularly Solutions Architect or DevOps Engineer Professional.
- Terraform Associate.
- AWS Certified Machine Learning or GenAI-track certifications.
We trust people to do their best work. That means flexibility over rigid rules, impact over activity, and real investment in your growth both professionally and personally. You'll be part of a supportive, and friendly culture, surrounded by smart, curious people who care deeply about what they do.
We offer flexible working, including hybrid and remote options. Our office hubs are located in Edinburgh, Leeds, Manchester, London and Bulgaria, with occasional travel to client sites or CreateFuture offices when needed.
We trust you to manage your time balancing collaboration with client time and focused work. What matters is the impact you have, not how busy you look.
We try to keep our hiring process clear, fair and respectful of your time. We aim to get back to everyone who applies and we will be upfront about where you are in the process.
It usually looks like this:
- Call with our Talent Acquisition Team
- Role specific capability interview
Depending on the role, we might also ask you to do a short presentation, a practical or technical task or have a values focused conversation. We will explain what is involved before anything happens.
We believe diverse teams build better workplaces and better products. We want CreateFuture to be a place where people feel able to be themselves and do their best work.
If you need any adjustments or support during the application process, just. We will do what we can to help.
We look forward to your application!
