Partner Solutions Engineer, EMEA
Job description
About the role
The position serves as a developer advocate and technical expert for partners, running certification, workshops, and hackathons while supporting proof-of-concept and deal acceleration. Fluency in German and/or French with professional English is essential for this partner-facing, hybrid position based in London or Berlin with required in-office days.
Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.
Key facts
Requirements
A strong web development background in frontend development, cloud infrastructure, networking, and modern application development is required.
Coordination across multiple partners and time zones is essential, alongside the ability to build lasting relationships with practice leads, delivery teams, and executives.
The role is an in-person hybrid position requiring 3 days per week in Vercel's London or Berlin office.
Speaking German and/or French is essential, with spoken fluency in at least one alongside professional English.
Experience working with or within agencies, systems integrators, or consulting firms is required to understand how they staff, deliver, and grow a technology practice.
Developer relations experience, including training sessions, talks, and producing technical content, is required.
A results-driven mindset is required for working in a fast-paced environment.
Comfort with remote, globally distributed cross-functional teams is required.
Strong communication skills and experience building and maintaining strong relationships with stakeholders are required.
Experience driving adoption of web technology or previous pre-sales experience is required.
Availability to travel and be based in EMEA with 20% travel is required.
Nice to have
Building and shipping AI-powered or agentic applications with the AI SDK is beneficial.
Fluency in both German and French is beneficial.
Running certification, training, or enablement programs at scale is beneficial.
Experience with composable architectures such as headless CMS, commerce, search, and analytics common in partner-delivered projects is beneficial.
Skills & tools
Expertise in Next.js and modern web frameworks.
Experience with agentic workflows and AI SDKs for building AI applications.
Practical notes
Travel within EMEA and 20% travel are required.
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
The role focuses on partner enablement and pre-sales within EMEA, especially the DACH region.
Core responsibilities include running certification programs, workshops, and hackathons.
The position requires a strong frontend and cloud infrastructure background.
The role involves close collaboration with sales, sales engineering, and executive stakeholders across partner organizations.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.