Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.
Lovable is seeking a Technical Enablement Lead for GTM—Sales, CS, and SA. You’ll onboard Solution Architects and convert their know-how into scalable enablement systems that raise the technical floor for the entire field.
We’ll build a central knowledge hub with demo libraries, reference architectures, and AI use-case pattern libraries, translating depth into practical materials for AEs and CSMs facing CIOs and VPs of Product.
TL;DR: Technical enablement lead for all of Lovable's GTM: Sales, CS, and SA. Your job isn't only to onboard Solution Architects, It's to leverage them as the bench that raises the technical floor for the entire field. AEs need to articulate the art of the possible. CSMs need to lead AI transformation conversations without flinching. You build the systems that make that happen.
Lovable lets anyone and everyone build software with any language. From solopreneurs to Fortune 100 teams, millions of people use Lovable to transform raw ideas into real products, fast. We are at the forefront of a foundational shift in software creation, which means you have an unprecedented opportunity to change the way the digital world works. Lovable-built applications and websites are visited hundreds of millions of times a month, and our enterprise footprint is compounding fast. And we're just getting started.
We're a small, talent-dense team building a generation-defining company from Stockholm. We value extreme ownership, high velocity, and low-ego collaboration. We seek out people who care deeply, ship fast, and are eager to make a dent in the world.
Enablement Partners at Lovable are productivity engineers. The goal is to build systems that eliminate the need for enablement in the first place: automate the process, embed the knowledge in the workflow, and remove the friction before it becomes a training problem. When training is the answer, it should be because automation genuinely can't reach. And it should focus on real skill development, not teaching someone how to follow a checklist. If you think in programs and curricula, this role will be a mismatch. If you think in systems and leverage, keep reading.
Projects you'll tackle first: Audit current technical knowledge assets across GTM and map the gaps against what AEs and CSMs are losing deals over. Build the first version of the AI use-case pattern library and reference architecture set. Design the SA-as-knowledge-multiplier model: how technical depth flows from the SA org into the broader field.