At a Glance
- Tasks: Transform design systems into AI-friendly formats and enhance user onboarding experiences.
- Company: Join R/GA's innovative AI Products team, shaping the future of design technology.
- Benefits: Competitive salary, flexible work environment, and opportunities for professional growth.
- Other info: Dynamic team culture focused on innovation and long-term product health.
- Why this job: Be at the forefront of AI design collaboration and make a real impact.
- Qualifications: 5+ years in design engineering with hands-on experience in building design systems.
The predicted salary is between 63000 - 77000 £ per year.
The team AIP is R/GA AI Products, the global group that builds R/GA's own products rather than client campaigns. Its first product, BRDNA Sequencer™, launched September 2026 and teaches coding agents to build on-brand. BRDNA Sequencer makes a brand machine-readable. It takes the design system, components, patterns, voice and rules a brand keeps in Figma files and PDFs, and encodes them into structured context a coding agent can read and act on. Point an agent at a brand, hand it a creative brief, and it works in Figma and Claude using the right components, without a human checking every output against the style guide. It is not a chatbot or a template generator; it's a collaboration tool. It's a way to encode a design system and create new designs from it while working alongside the designer or marketer.
The role involves turning design systems into something an AI can build with. The tool takes Figma designs, translates them into markdown, manipulates them, and translates them back. That round trip is the whole product. Making it faithful in both directions, across any brand, is the hard part. The job needs two skill sets:
- Design systems: You have built, shipped and maintained one. You know what makes interface components and token architecture valuable and scalable for product teams.
- AI fluency: Prompt engineering is a craft you practice rather than read about. You have a feel for what context a model needs, why it fails, and how to restructure input until output is dependable.
You also own the front end of the customer experience: the onboarding and self-serve flow that gets a new team from 'we have a Figma library' to 'our agents are building on-brand.' You'll build alongside the product team.
What you'll do includes three main responsibilities:
- Polish the encoding pipeline: The core of the job, and a round trip in both directions. Figma → markdown. A brand's design system, meaning components, patterns, tokens, rules and voice, encoded into structured markdown and tokenized into a vector space agents retrieve from. Markdown → Figma. The same understanding translated back out, so what an agent produces lands as real designs rather than something approximate.
- Own onboarding and self-serve: You own the experience that carries a new team from 'we have a Figma library' to 'our agents are building on-brand assets.' Audit what exists, work out where it loses people, rebuild it.
- Design and build the product surface: You own the front end of the customer experience, designing it and shipping it. No handoff, no spec thrown between two people. You'll build production alongside full-stack product engineers.
What we're looking for:
- 5+ years in design engineering, product design, or front-end product work.
- You have built a design system and lived with it. Owned one, not consumed one.
- You have designed a full product.
- You build layered prompt systems that produce production-grade output.
- You understand how structure at one level changes behaviour three levels down.
- You think on a product's timeline, not a project's.
On agency backgrounds: R/GA is an agency. AIP is a product team that happens to live inside one. Agency work is built to ship and hand off; this work you live with. We are looking for people whose first instinct is to ask what a decision does to the product in a year.
Strong signal, not required:
- Figma as a platform rather than a canvas: Variables, the Plugin or REST API, Code Connect, library architecture across multiple consuming teams.
- Retrieval and embeddings in practice.
- Evals: you measure model output rather than eyeballing it.
- Self-serve and product-led growth.
- 0→1→10: you have been early somewhere and know what that costs.
The stack includes React / Next.js for the product surface, Supabase for data and backend, and Figma MCP to reach into design systems. Model-agnostic by design. Interoperability is a product requirement.
Your first 90 days involve robust onboarding, ensuring workflows are meaningfully less non-deterministic, with dependable output.
Lead Design Engineer employer: R/GA
R/GA is an exceptional employer that fosters a dynamic and innovative work culture, where creativity and technology converge to drive meaningful impact. As the Executive Director, Growth, you will enjoy unparalleled opportunities for professional development while collaborating with top-tier talent in a vibrant London setting. With a focus on strategic growth and a commitment to nurturing your career, R/GA empowers you to shape the future of brand experiences in a supportive and forward-thinking environment.
StudySmarter Expert Advice🤫
We think this is how you could land Lead Design Engineer
✨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 R/GA 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 R/GA.
✨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 R/GA.
✨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 R/GA 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 Lead Design Engineer
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 R/GA.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at R/GA 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 R/GA
✨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 R/GA 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.