Lovable
Lovable4 open roles

Forward Deployed Engineering Lead

$241–390kNew York, NY; San Francisco, CA; Boston, MAOn-siteSeniorFull-time

Posted 28 days ago

The role in short

Lead and build a team of Forward Deployed Engineers while personally writing production code and designing solutions for customers.

TL;DR - We’re looking for an exceptional Forward Deployed Engineering Lead to help build the future of AI-powered software creation. You’ll build and lead an exceptional FDE team, while working alongside our other FDE leaders to shape how the function operates globally. You’ll remain deeply hands-on — working directly with our most ambitious customers, writing production code, and building alongside your team.

Why Lovable?

Lovable is the software creation platform that gives people the power to act on the problems closest to them. For decades, turning an idea into software required so much capital, technical fluency, and time that many ideas never came to life. Lovable is the counterargument: a platform for all people with ideas, ambition, and problems worth solving. From solopreneurs to small business owners to teams at companies like Adidas and Zendesk, people have built over 60 million projects on Lovable since its launch in November 2024. And we’re just getting started.

We’re building a generational company from Stockholm, with growing teams in London, Boston, New York, and San Francisco. Our team is small, talent-dense, and moving quickly, with a culture rooted in extreme ownership, high velocity, and low-ego collaboration. We look for people who care deeply, ship fast, and are eager to make a dent in the world.

Lovable is one of TIME’s 100 Most Influential Companies and has been recognized on the Forbes AI 50 and CNBC Disruptor 50, reflecting our momentum as one of Europe’s fastest-growing AI companies and one of the most ambitious places to build in this next era of software.

What you’ll do

In one sentence: build the team that deploys intelligence into the real world — and deploy it alongside them.

• Build, develop, and lead an exceptional team of Forward Deployed Engineers

• Work directly with customers to understand their workflows, needs, and hardest technical problems

• Personally design, prototype, and implement solutions alongside your team

• Own and guide projects from idea → architecture → shipping → iteration

• Set the technical bar through architecture decisions, code reviews, and hands-on engineering

• Translate insights from customer deployments into foundational platform improvements

• Partner with other FDE leads to shape standards, playbooks, and how the function scales globally

• Contribute to core product strategy, technical decisions, and cultural foundations

What we’re looking for

• 12+ years across software engineering, technical architecture, and customer-facing engineering

• 2+ years of experience building, coaching, & developing engineers responsible for customer-facing delivery.

• A track record of remaining deeply hands-on as your leadership scope has grown

• Strong full-stack engineering fundamentals across modern frontend and backend development

• Strong architectural thinking and familiarity with distributed systems

• Experience owning complex technical engagements end-to-end

• Exceptional product intuition and ability to work directly with users

• Ability to move comfortably between writing code, making architectural decisions, leading engineers, and working with senior customer stakeholders

• High agency and comfort operating in high-ambiguity, high-velocity environments

Bonus if you’ve:

• Built a team or technical function from zero

• Worked on agentic AI systems or built with LLMs in production

• Led zero-to-one product development

• Worked in a founding or early-stage startup environment

• Worked across high-growth startups, big tech, consulting, or enterprise AI

Our Tech Stack

We choose tools that empower both humans and AI:

• Frontend: React, TypeScript

• Backend: Golang & Rust

• Cloud: Cloudflare, GCP, AWS, multiple LLM providers

• Tooling: GitHub Actions, OTEL, Grafana, Terraform, and more

• Always evolving with what works best

How we hire

  1. Fill out a short form and hop on a brief intro call with our recruiting team

  2. A technical leadership interview — how you build teams, set standards, and make technical decisions

  3. Show us how you approach hard technical problems

  4. Show us something you’ve built that makes you proud

  5. Conversations with the leaders you’d work most closely with, followed by a final discussion

About your application

• Please submit your application in English — it’s our company language, so you’ll be speaking lots of it if you join

• We treat all candidates equally — if you’re interested, please apply through our careers portal

Compensation:

For sales roles, this range reflects On-Target Earnings (OTE), which includes both annual base salary and target sales commissions or bonuses.

Actual compensation may vary based on factors such as the candidate’s experience, qualifications, location, and applicable market conditions. Only US ranges are shown for this role.

Compensation Range: $241,000 - $390,500 USD

Prep for this interview

5 questions likely to come up at Lovable, each matched to a line in this posting.

  1. 1LLMs, RAG and agents
    They wrote: “Worked on agentic AI systems or built with LLMs in production”

    When would you use an agent that takes actions, and how do you keep it safe?

    How to answer

    Why they ask: Agent work is growing fast in FDE postings. Senior candidates are expected to know where agents fail.

    1. Use agents for multi-step tasks with clear success checks; avoid them where one wrong action is costly
    2. Give the agent narrow tools and permissions, not broad access
    3. Require human approval for risky actions
    4. Log every step so the customer can audit it

    Tip: Start from the cost of a wrong action. Limit what the agent can do, and log everything.

  2. 2Cloud, deployment and security
    They wrote: “Cloud: Cloudflare, GCP, AWS, multiple LLM providers”

    How would you debug a deployment that works in staging but fails at the customer's site?

    How to answer

    Why they ask: Customer environments differ in ways you can't see. This tests method under pressure.

    1. Compare versions, config and environment variables
    2. Check network rules, proxies and certificates (common in enterprise)
    3. Look at resource limits and permissions
    4. Add the missing check to your install steps afterwards

    Tip: List the usual suspects and how you'd check each without full access.

  3. 3Discovery and scoping
    They wrote: “A track record of remaining deeply hands-on as your leadership scope has grown”

    How do you decide what to build first when a customer wants ten things?

    How to answer

    Why they ask: FDEs have limited weeks per customer. This tests judgment about value, effort and risk.

    1. Score each request by business value and by effort, with the customer in the room
    2. Pick one item that proves value fast and unblocks later work
    3. Write down what's out of scope so it doesn't creep back in
    4. Revisit the list after the first release, with real usage data

    Tip: Show a simple way to rank the list and name what you'd leave out on purpose.

  4. 4Coding
    They wrote: “12+ years across software engineering, technical architecture, and customer-facing engineering”

    Build a small in-memory cache. Then add expiry. Then a size limit.

    How to answer

    Why they ask: Staged exercises show how your code holds up when requirements change mid-interview, like at a customer.

    1. Start with get and set on a dictionary, plus tests
    2. Store an expiry time with each value and check it on read
    3. Track use order and evict the least recently used entry when full
    4. Say what you'd change for many threads or many machines

    Tip: Keep the first version simple and well tested so the next stage is a small change.

  5. 5Ownership and working with customers
    They wrote: “High agency and comfort operating in high-ambiguity, high-velocity environments”

    Tell me about a project where the requirements kept changing. What did you do?

    How to answer

    Why they ask: Ambiguity is the norm. They want proof you can keep moving without a clear spec.

    1. The project and why requirements kept moving
    2. What you did to pin them down (short demos, written decisions)
    3. The trade-offs you made to keep shipping
    4. The result, with a number if you have one

    Tip: Show how you reduced the change, beyond how you coped with it.

Not the one? Get the next one by email

New roles land here every day. Pick what you want to hear about.

FDE Info

Want the job, not just the posting? Learn how FDEs work.

FDE Info is our free weekly newsletter for forward deployed engineers: tools, field notes from real deployments, and how FDE teams hire and pay.

Free. One email a week. Unsubscribe in one click.

More at Lovable

Similar roles at other companies

Lovable

$241–390k · On-site

Apply