At a Glance
- Tasks: Lead AI projects, solve real business problems, and build innovative solutions.
- Company: Fast-growing AI engineering company with a focus on client collaboration.
- Benefits: Remote-first work, significant autonomy, and exposure to challenging AI problems.
- Other info: Opportunity to work directly with clients and see your creations in action.
- Why this job: Make a real impact by turning ideas into functional AI systems for businesses.
- Qualifications: Strong software engineering background and experience in building projects.
The predicted salary is between 59400 - 72600 £ per year.
Forward Deployed Engineer | AI
You can write good software.
But can you walk into a business, understand a problem that nobody has properly defined yet, work out where AI can genuinely make a difference, and then build the thing?
Because that’s what this role is really about.
You’ll join a fast-growing AI engineering company that embeds small technical teams directly inside its clients.
You won’t spend months working from a perfectly written product specification.
Instead, you’ll sit close to founders, operators and senior stakeholders, understand how their business actually works, identify where technology can create leverage, and turn ambiguous problems into production AI systems.
You’ll own the outcome from beginning to end.
What will you actually be doing?
You’ll act as the technical lead on client projects.
That means you could be
- Sitting with a founder trying to understand why a critical internal workflow takes three days.
- Working out whether AI is actually the right answer.
- Designing the architecture for a new system.
- Building integrations, evaluations and deployment infrastructure.
- Shipping an initial version quickly.
- Watching how real users interact with it.
- Iterating until it genuinely solves the problem.
You’ll be expected to move comfortably between engineering and communication.
One minute you might be deep in the codebase.
The next, you’ll be explaining to a non-technical stakeholder what you’ve built, why you’ve built it that way, and what needs to happen next.
You won’t simply receive tickets.
You’ll help decide what the tickets should be.
This could suit you if…
You’re an engineer who likes building things more than talking about building things.
You’re already experimenting with frontier AI models and tooling because you’re genuinely curious about what they can do.
You understand that models are powerful, but you also understand their limitations.
You probably have side projects, prototypes, products or experiments sitting in your Git Hub that nobody asked you to build.
You enjoy starting with a blank page.
You’re comfortable making decisions without having every requirement defined for you.
And importantly, you can talk to people.
You don’t need a Product Manager translating every conversation between you and the client.
You’re happy sitting in a room with founders or senior operators, asking intelligent questions and turning what you hear into something that works.
Your background
You’ll need a strong grounding in software engineering and be comfortable operating across the full development lifecycle.
You might already be an AI Engineer, Software Engineer, Founding Engineer, Solutions Engineer or Forward Deployed Engineer.
Your exact title matters less than what you’ve actually built.
Having created something yourself is a major advantage.
That could be
- A startup.
- A software product.
- An AI model or application.
- A consultancy.
- An open-source project.
- A side project with real users.
What matters is that you know what it feels like to take something from an idea to something people actually use.
Why join?
Because you’ll get exposure to a range of genuinely difficult AI problems rather than spending years maintaining one narrow product area.
You’ll work directly with clients.
You’ll have significant autonomy.
You’ll ship quickly.
And you’ll see the systems you build being used in real businesses, rather than disappearing into an endless backlog.
This is a remote-first position, although you’ll need to be comfortable travelling into London for client meetings and on-site work when required.
If you want a role where you’re given a tightly defined specification and told exactly what to build, this probably isn’t it.
If you want to be the person who figures out what should be built in the first place, then builds it, this could be a very good fit.
Apply now and tell us about the most interesting thing you’ve built.
Forward Deployed Engineer in London employer: Findrs
Findrs is an exceptional employer that fosters a collaborative and innovative work culture, perfect for those looking to make a significant impact in the field of AI engineering. With a strong focus on employee growth and development, we offer unique opportunities to shape both technical and product directions while working in a hybrid environment that promotes work-life balance. Join us to be part of a forward-thinking team dedicated to redefining software testing and driving meaningful business outcomes.
StudySmarter Expert Advice🤫
We think this is how you could land Forward Deployed Engineer 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 Findrs 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 Findrs.
✨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 Findrs.
✨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 Findrs 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 Forward Deployed Engineer in London
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 Findrs.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Findrs 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 Findrs
✨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 Findrs 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.