Delivery Engineer

Sedna is at the forefront of revolutionising global trade, serving as the North Star for businesses navigating the complexities of international commerce. Our AI-powered platform is designed to make global trade more efficient, transparent, and sustainable. As we continue to grow and innovate, we are looking for exceptional talent to join our journey and contribute to our mission of transforming global trade.

Every Sedna product we sell is semi-custom. That is a strength commercially – and a bottleneck in delivery. Our Delivery Managers are excellent at taking a customer from signature to live, but the technical edge cases inherent in a semi-custom build – a tagging model that won't behave, an integration that won't connect, a configuration question with no standard answer – currently pull them off the critical path while they wait on other teams to help.

This role removes that bottleneck. You are the technical engine inside the Delivery team – a hands-on, broad-spectrum engineer whose job is to unblock our Delivery Managers on the pressing technical problems that today stall implementations. When a Delivery Manager hits a wall, you are the person who gets them through it: configuring, scripting, debugging integrations, untangling tagging logic, and answering the technical questions that would otherwise sit in a queue.

You sit inside Delivery, you report to the Head of Delivery, and you are measured on the same outcomes as the rest of the team.
That is deliberate: your incentives are aligned with speed to value. You win when the team ships launches faster, not when a ticket is closed somewhere else. The result is fewer external dependencies, fewer escalations, and implementations that stop stalling on technical unknowns.

• A force multiplier for eight Delivery Managers – you make the whole team faster.
• A generalist who gets hands on the build: config, tagging, auto-taggers, integrations, APIs.
• The first line of technical resolution, so problems get solved in-team.
• An engineer with a delivery mindset and delivery incentives.

• Not another Implementation Manager with an engineering title.
• Not the owner of a personal portfolio of accounts.
• Not a project manager – Delivery Managers keep owning the customer relationship and timeline.
• Not a Product or Engineering function – you live and are measured inside Delivery.

• Be the first technical resolver for the Delivery Managers. When an implementation hits a technical wall – a configuration edge case, a tagging model that won't behave, an integration that won't connect, an “is this a bug or a config?” question – you are who they come to, and you get them moving again.
• Get hands on the build directly: workflows, mailboxes, key settings, category and job tags, auto-taggers, and the scripts or API calls needed to make a semi-custom solution actually work in practice.
• Hold the escalation boundary. Decide what can be solved inside Delivery versus what is genuinely a Product or Engineering issue – and when it is the latter, package it so it is specified, reproducible and immediately actionable, minimising the back-and-forth.

• Turn recurring roadblocks into reusable assets – playbooks, templates, tooling, snippets – so the same problem never stops a Delivery Manager twice.
• Level up the team's technical skillset. As Delivery verticalises, you help diversify the skills on the team so that more can be handled in-house over time.
• Feed recurring patterns back to Product and Engineering so root causes are fixed at source rather than re-solved on every account.

• Suppor…