Developer Relations Engineer

​

About Orbital

Orbital and our schema language Taxi are rethinking enterprise integration - for developers and AI agents. The old ways - gluing together endpoints with brittle spaghetti code - don’t work, regardless of who’s doing the coding, developer or agent. iPaaS platforms haven’t helped. We’re building something different.

Orbital solves this with semantic layers - instead of cranking glue-code by hand, you describe what data you need (in Taxi) and Orbital figures out how to get it. The result: integrations in milliseconds that are deterministic, secure, self-repairing, auditable, observable, and scalable.

We’re already deployed in banks and financial institutions, and we’re looking for someone to join to build awareness and help improve our product.

You’ll be working on both Orbital - our data integration platform - and Taxi, our open source language (and ecosystem) for building semantic layers.

​

What you'll actually do

Build the developer community from scratch. We have a Slack, GitHub stars, and paying customers. What we don’t have is a systematic engine turning curious developers into active users, active users into advocates, and advocates into a community.

Push the boundaries of Orbital, to make it better. We want someone with a scrappy, hackery mentality - someone who thinks “It’d be cool if…” and either builds it, or helps us figure out why we can’t, so we can.

Create content developers respect. Blog posts, tutorials, conference talks, video walkthroughs. We’re looking for engaging (preferably humorous) content that we’d watch - not enterprise whitepaper verbosity. You’ll cover Orbital specifically, but also the broader problem space: microservices integration, semantic schemas, API composition, event-driven architecture. Developers should follow you for your thinking, not just the product.

Own the docs experience. Our documentation is functional but not yet great. You’ll work with engineering to make the getting-started experience feel effortless - from docker compose up to a working integration in minutes.

Be the feedback bridge. Sit in the Slack, read the GitHub issues, attend the community calls. Bring the pain points, the feature requests, and the “why the hell does it work like this” moments back to the product team in a structured way. You’re the voice of the developer inside the building.

Represent Orbital at events. London has a massive dev community; you’ll also travel to key events in Berlin, Amsterdam, Prague, and beyond.

Figure out where our audience lives. YouTube, Dev.to, Hacker News, X, somewhere else entirely - part of the job is finding out through doing, not theorising.

What success looks like: more developers finding Orbital, trying it, and building with it - measured in community growth, sign-ups, and integrations shipped.

​

What we're looking for

You’ve shipped software. This isn’t a marketing role wearing a developer costume. You need to understand microservices, APIs, Docker, and have opinions about integration patterns. You don’t need to be a principal engineer - but you need to spin up Orbital, write a Taxi query, and build a demo without hand-holding.

You can write. Clear, concise, technically accurate writing that’s fun to read. Blog posts, docs, README files, Twitter threads - you have a voice and you use it.

You’re AI savvy. You actively work with AI tooling to help you get stuff done.

You can present. On camera, on stage, in a Slack thread. Comfortable being the face of a product, and you don’t default to corporate-speak when the camera turns on.

You’re self-directed. First DevRel hire means no playbook. You’ll set your own priorities, measure what’s working, and course-correct without waiting for permission.

You care about developer experience. You notice when an error message is unhelpful, when a tutorial skips a step, when onboarding has unnecessary friction. And you fix it or flag it - you don’t shrug.

You understand enterprise data sources. You’re comfortable building and explaining the tools that enterprises use - APIs, Kafka, RabbitMQ, data streaming. You’re probably very familiar with API architectures, or Kafka / streaming architectures, or both.

​

Nice to have

• An existing audience or track record in developer content (blog, YouTube, conference talks, open source project with real users)
• Experience building or hacking on AI systems - even just poking about on side projects - but with a real understanding of how they work under the hood
• Experience with integration platforms, API gateways, or data orchestration tools
• Experience with Kotlin / JVM ecosystem (Orbital’s backend)

​

What we offer

• Competitive salary and early-stage equity
• Remote-first (we work in UK timezones). Ability to meet up in London is nice, but not essential.
• Budget for conferences, community events, and travel
• Hardware and tooling budget

​

How to apply

Send us a note at careers@orbitalhq.com. Tell us what you’ve shipped, point us at something you’ve written or recorded, and let us know why this role caught your eye.