Skip to main content

Lovable

Partner Engineer

  • Confirmed live in the last 24 hours
  • $199k–$271k
  • Mid level
  • Full-time
  • On-site · New York City
  • 5+ yrs exp
  • Added 2 months ago

About this role

Lovable is seeking a Product Partnership Engineer to build and scale strategic product integrations with enterprise partners. You'll combine technical depth with business acumen to design, prototype, and ship high-impact integrations that drive ecosystem growth and enterprise adoption.

What you'll do

  • Manage and deepen relationships with Lovable's strategic product and enterprise partners, driving alignment and momentum
  • Assess partner architectures and APIs to identify integration opportunities and validate technical feasibility
  • Prototype and spike early integrations independently to shape requirements and reduce engineering effort
  • Scope and ship production-ready integrations that deliver measurable value to users and partners
  • Develop business cases demonstrating long-term value creation for all stakeholders
  • Collaborate cross-functionally with Engineering, Product, Marketing, and Growth to align on strategy and execution

What they're looking for

  • Technical Business Development or Solutions Engineering
  • API integration and hands-on technical prototyping
  • Cloud architecture understanding
  • Enterprise sales and stakeholder management
  • Product strategy and requirements scoping
  • Full-stack prototyping capability
  • Cross-functional collaboration
  • Technical documentation analysis
Apply with Autofill

Opens the application — the Jobs AI extension fills it for you. Set up autofill

Opens the official application on the employer’s site. No login required.

Lovable

Industry
Technology & Software
View all jobs at Lovable

Likely interview questions

  • Walk us through a complex partnership you've led—what made it successful and what technical challenges did you overcome?
  • Tell us about a time you prototyped a solution yourself to validate an integration approach. What did you learn that changed the final implementation?