Senior Technical Partnership Lead in Moffat

Job Description

hackajob is collaborating with Nuweb Group to connect them with exceptional professionals for this role.

A variety of soft skills and experience may be required for the following role Please ensure you check the overview below carefully.

Technical Partnership Lead

Remote-first (UK) · Senior

Who we are
Nuweb Group is a global event technology partner, helping organisers, promoters, venues, and ticketing providers scale with confidence.
We're a fast-growing force in live entertainment, partnering globally to support brands like Formula 1, Metallica, and Disney on Ice. Our mission is bold - To be the Ticketing Engine of the World.That means building the infrastructure that solves complex ticketing challenges and creates unforgettable fan experiences.
We are a global company, operating seamlessly across borders and time zones. We take pride in our ability to move quickly, innovate, and push boundaries. If you want to be part of a team that values curiosity, craft, and ambition - Welcome to NuwebGroup.
Mission

To be the senior technical face of Nuweb to our partners, the person they trust with the technical relationship, and the person who makes sure their projects land.

You will lead the technical conversation with our partners: understanding what they actually need, shaping it into requirements our business can act on, and then owning delivery through to a live, trading partner. You will be the technical credibility in the room during new business conversations, before a contract is ever signed and the person who has the difficult conversation when a timeline moves or an expectation needs resetting.

You will work across Partner Success, Commercial and Engineering, but sit inside none of them. Your loyalty is to projects landing successfully and partners staying confident, not to any one department's agenda.

What you'll do

Own the technical relationship

• Be the senior technical point of contact for our partners — the person their technical and product stakeholders come to and trust.

• Build genuine understanding of each partner's business, so technical conversations are grounded in what actually matters to them.

• Handle the difficult conversations — slipped timelines, technical constraints, expectations that need resetting — with candour and care, and leave the relationship stronger.

• Build direct working relationships with partner-side technical and project contacts.

Shape new projects and requirements

• Lead the initial technical conversations when a partner brings a new project or requirement — in your own right, without needing an engineer in the room.

• Understand and shape the requirement: what problem is being solved, what it would take, what is and isn't viable, and at what rough cost.

• Assess technical feasibility and produce a clear, well-formed brief that the business can prioritise against the roadmap.

• Hand that shaped understanding to the Managing Director and the Steering Group, so the roadmap decision is made with a clear technical and commercial picture.

Support new business

• Join sales and discovery conversations for prospective partners where technical credibility is needed, alongside Commercial and Partner Success.

• Give early, honest technical feasibility input during proposal and contracting, so that what we promise is what we can actually deliver.

• Represent Nuweb's technical capability directly to a prospective partner's technical stakeholders, ahead of signature.

• Help define realistic onboarding timelines for new business before a contract is signed.

Own technical project delivery

• Own delivery for both new partner onboarding and the ongoing stream of technical projects existing partners generate — integrations, data migrations, feature rollouts — work that doesn't stop once a partner goes live.

• Run structured delivery frameworks — milestones, owners, dependencies and risks — adapted to each project's complexity.

• Be the single point of accountability when several projects run concurrently across new and existing partners, sequencing work so nothing silently slips.

• Define and hold cutover and contingency plans for critical go-live moments, and own launch readiness — migrations, cutover, and the operational detail that decides whether a launch happens on the committed date.

• Escalate early and clearly when a project is genuinely at risk, rather than absorbing risk quietly.

Work with Engineering, without duplicating it

• Define what a partner needs, why and by when, at a project, architectural and functional level — detailed technical specification remains Engineering's own responsibility.

• Hand off clearly scoped requirements to Engineering, then own the timeline and coordination around their delivery.

• Represent technical constraints and timelines accurately to partners and to Partner Success, without over-promising on either side.

• Free our engineers to build — you carry the partner-facing technical conversation so they don't have to.

Process, repeatability and insight

• Build reusable onboarding frameworks, templates and checklists so delivery scales as the partner base grows, rather than being reinvented each time.

• Run regular status communication across Partner Success, Product and Engineering so all three share a current view of delivery.

• Feed structured delivery insight back into Product and Partner Success — what typically goes wrong, what typically works, and what that means for the roadmap.

Job-related skills and knowledge

• Genuine technical depth. A strong technical background — credible discussing APIs, integrations, data models and architecture with a partner's engineers, and able to assess feasibility yourself. You need not be writing code, but you must have been close enough to it to make the call, not merely relay it. Our technology is web based and uses Laravel and Vue.js. so you should be familiar with that tech.

• Implementation and delivery track record. Proven experience delivering technical onboarding or implementation projects for high-profile, high-stakes clients, where deadlines were fixed and failure was not an acceptable outcome.

• Requirement shaping. Able to turn a partner's ambiguous need into a clear, well-formed, trackable requirement that others can act on.

• Commercial literacy. You understand the business impact of technical decisions — what something costs and what it is worth — and you don't promise what shouldn't be promised.

• Stakeholder management across technical and commercial audiences. Able to talk credibly to a partner's engineers and to their senior business stakeholders, adjusting register without losing precision.

• Senior presence. Comfortable in the room with founders, CTOs and commercial directors.

• Live events or ticketing background preferred. Experience in ticketing, payments, sports or live entertainment is a strong advantage, given the operational pressure and time-critical nature of the work.

• Documentation and process thinking. Able to turn a messy set of requirements into a clear delivery plan others can follow.

• IT proficiency. Strong general IT literacy, with proficiency in project tracking tools (Linear/Jira or equivalent), Google Workspace and/or Microsoft Office, and collaboration tools such as Slack.

• Education and experience. A degree, diploma or certificate in a technical, IT or business discipline — or 5+ years of relevant technical implementation and delivery experience in place of formal qualifications.

Personal skills

• Exceptional at difficult conversations. Able to deliver unwelcome news to a senior stakeholder — a slipped deadline, a hard constraint — and leave the relationship stronger than before.

• Calm under pressure. Performs effectively when a live project is at risk, and stays clear-headed when timelines slip or scope shifts.

• Ownership mindset. Takes personal responsibility for a project landing, not just for completing assigned tasks — and knows when and how to pull in the right people.

• Direct communication. Comfortable escalating problems early and plainly, rather than letting risk sit quietly until it becomes a crisis.

• Cross-functional operating style. Works effectively without a fixed departmental home, building credibility with Partner Success, Product and Engineering independently.

• Organisation and prioritisation. Able to run several concurrent, high-stakes projects without losing track of any of them.

• Remote effectiveness. Self-motivated, with the communication discipline a remote-first team depends on.

Where this role sits

To keep the role clear:

• Owns: the technical partner relationship, initial technical conversations and requirement shaping, technical feasibility input, and delivery of partner technical projects.

• Reports to the Managing Director, who owns product strategy, the roadmap and prioritisation. You shape the requirement; the roadmap decision is made through our Steering Group.

• Works alongside Partner Success, who own the day-to-day customer relationship, onboarding support and ongoing service. You are their technical counterpart, not their replacement.

• Works alongside Engineering, who own the build, the detailed technical specifications and the platform. You represent their work to partners so they can focus on building.

• Does not own commercial terms — contracts, pricing and negotiation sit with our Head of Commercial Partnerships. You bring the commercial understanding, not the commercial mandate.

Other role information

• Travel: willingness to travel for partner onboarding visits, go-live support and internal meet-ups.

• Working hours: flexibility to align with partner and project deadlines, including occasional out-of-hours support around critical go-live windows.

• Location: remote-first, UK based, with flexibility to align with partner needs across time zones. xxuwjjq

• Structure: this role sits outside the Partner Success team structure and managed separately, reflecting its cross-functional remit.