AI Practice Lead in London

AI Practice Lead in London

London Full-Time 81000 - 99000 £ / year (est.) Hybrid
Z

At a Glance

  • Tasks: Lead AI engineering projects and design innovative solutions for clients.
  • Company: Join Zensar, a global leader in digital solutions and experiences.
  • Benefits: Competitive salary, inclusive culture, and opportunities for personal growth.
  • Other info: Be part of a diverse team dedicated to innovation and excellence.
  • Why this job: Shape the future of AI while working with top-tier clients and technologies.
  • Qualifications: Strong background in distributed systems and client-facing experience required.

The predicted salary is between 81000 - 99000 £ per year.

Engineering Foundation

  • Data modelling across SQL and NoSQL, and a clear view of where each one breaks.
  • Event-driven architecture in production with Kafka, RabbitMQ or equivalent.
  • Distributed systems failure modes: partial failure, retries, backpressure, timeouts, circuit breakers.
  • Caching strategy and invalidation, at a scale where getting it wrong hurts.
  • Observability: you have instrumented a system, not just read someone else's dashboard.
  • At least one cloud deeply. Not three superficially.
  • API and integration patterns against real enterprise surfaces such as ERPs, CRMs and data platforms.
  • CI/CD, containers, release engineering.
  • You have owned something in production: on-call, incidents, the whole thing.
  • Agent systems are distributed systems with a non-deterministic component in the middle.

Responsibilities

  • AI Engineering
    • Evaluation and Error Analysis: you have built an eval set for a non-deterministic system and used it to make a decision.
    • You can decompose a failure: is this a model problem, a retrieval problem, a data problem or a product problem?
    • You debug agent behaviour systematically, with traces and evidence, not by gut feel.
  • Context Engineering
    • Deliberate management of what enters the model on each turn, and why.
    • Memory strategy: what persists across steps, across sessions, and what should not.
    • Tool surface design: what the agent can reach, how it is scoped, what happens when a tool fails.
    • Cost and latency as first-class design constraints, not something discovered in the invoice.
  • Consulting and Client Leadership
    • Equal weight to the engineering. This is a client-facing role in a services business.
    • Run discovery workshops, solution reviews and delivery cadences with client teams.
    • Advise clients on standing up their own AI capability: practice structure, operating model, skills, governance, build versus buy, and adoption across their engineering org.
    • Shape and defend technical proposals, PoC plans and roadmaps. Own the story end to end.
    • Translate business problems into architectures for CXO-level stakeholders without hiding behind jargon.
    • Say no when the answer is no. Tell a client when agents are the wrong tool, and be able to explain why.
  • Delivery and Architecture
    • Own end-to-end delivery of AI-native programs, from architecture through production.
    • Design multi-agent orchestration using LangGraph, CrewAI or equivalent.
    • Integrate agent systems with enterprise systems of record, not toy datasets.
    • Build RAG where RAG is the right answer, from chunking through retrieval, re-ranking and evaluation.
    • Run agentic coding workflows with Claude Code, Cursor, Codex or equivalent, and lead projects where AI writes significant portions of the codebase while you guide, review and ship it.
    • Work with MCP and shared-context tooling. Design what agents are permitted to reach and under what controls.
    • Bring governance into the design from day one: agent identity, privilege scoping, audit, human-in-the-loop, kill switches.
    • Contribute to reusable frameworks and accelerators the wider practice can use.
  • Team and Practice
    • Build AI engineering capability across the delivery organisation through mentoring, standards and review quality.
    • Evaluate new models, frameworks and tooling before the hype catches up, and kill the ones that do not earn their place.
    • Contribute to internal knowledge bases and practice assets.

Qualifications

What We Are Not Looking For

  • Someone who lists LLMs on a resume but has only called the API in a notebook.
  • People who explain everything in terms of frameworks they have never deployed.
  • Consultants who can only narrate what others have built.
  • Engineers who cannot hold a client conversation, and client-facing people who cannot build.

How We Will Evaluate You

  • Stage 0: System design with no AI. A distributed systems problem with no LLM in it. Event flow, data model, failure handling, scale. Twenty-five minutes.
  • Stage 1: Technical screen. Walk us through a system you built. Bring an artifact: an eval set, a trace from a run that failed, a postmortem, a cost-per-task number. Something real, not slides.
  • Stage 2: Architecture discussion. A business problem, live. Design the solution and defend the trade-offs, including the decision not to use agents.
  • Stage 3: Client simulation. Present your approach to a non-technical executive audience, then advise them on how to build the capability internally.

At Zensar, we’re committed to conceptualizing, designing, engineering, marketing, and managing digital solutions and experiences for over 130 leading enterprises. We are a company driven by a bold purpose: Together, we shape experiences for better futures. Whether for our clients, our people, or the world around us, this belief powers everything we do. At the heart of our culture is ONE with Client - a set of four core values that reflect who we are and how we work: One Zensar, Nurturing, Empowering, and Client Focus. We are a community of 10,000+ innovators across 30+ global locations. Explore Life at Zensar and join us to Grow. Own. Achieve. Learn. to be the best version of yourself. We believe the best work happens when individuality is celebrated, growth is encouraged, and well-being is prioritized. We are an equal employment opportunity (EEO) and affirmative action employer, committed to creating an inclusive workplace. All qualified applicants will be considered without regard to race, creed, color, ancestry, religion, sex, national origin, citizenship, age, sexual orientation, gender identity, disability, marital status, family medical leave status, or protected veteran status.

AI Practice Lead in London employer: Zensar

At Zensar, we pride ourselves on being an exceptional employer that fosters a dynamic and collaborative work environment. As a Technical Support Engineer, you will not only enhance your technical skills but also enjoy ample opportunities for personal and professional growth, all while contributing to a culture that values creativity and innovation. Located in a vibrant area, our team thrives on the freedom to explore thoughtful solutions, ensuring that every day presents new challenges and rewards.

Z

Contact Details:

Zensar Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land AI Practice Lead in London

✨Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Zensar or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

✨Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Zensar.

✨Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Zensar.

✨Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Zensar that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace AI Practice Lead in London

Data Modelling (SQL and NoSQL)
Event-Driven Architecture
Distributed Systems
Observability
Cloud Computing
API Integration
CI/CD

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Zensar.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Zensar and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at Zensar

✨Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

✨Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Zensar uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

✨Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

✨Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.