At a Glance
- Tasks: Design and deliver innovative payment infrastructure as a Principal Platform Engineer.
- Company: Fast-scaling fintech focused on merchant-first solutions and engineering excellence.
- Benefits: Fully remote work, competitive salary, and opportunities for professional growth.
- Other info: Dynamic role with mentorship opportunities and a focus on security and compliance.
- Why this job: Join a cutting-edge team and shape the future of payment technology.
- Qualifications: 8-10 years in software engineering with expertise in TypeScript/Node.js or Python.
The predicted salary is between 80000 - 100000 £ per year.
Our client is a fast-scaling fintech building the next generation of payment infrastructure. They're merchant-first, engineering-led, and genuinely obsessive about outcomes over process.
They're hiring a Principal Platform Engineer to own the design and delivery of a suite of Model Context Protocol (MCP) servers - the trusted, governed gateway between AI agents and their core payments platform. You'll set technical direction and write production code, not just review it.
- Owning the architecture and delivery of MCP servers that expose platform data and capabilities to AI agents and internal developer tooling.
- Designing the transport and session model (Streamable including stateful sessions for progress streaming, subscriptions, sampling, and user elicitation flows).
- Implementing robust OAuth-based authentication and authorisation, integrated with the company's identity provider, with least-privilege, per-request data scoping.
- Designing and operating the edge and gateway layer - Cloudflare Workers and Durable Objects - for token validation, JWKS caching, routing, and session state.
- Defining standards, patterns, and reusable libraries so other teams can build additional MCP servers quickly, consistently, and securely.
- Embedding security and compliance into every layer - this is a high-trust surface over sensitive payment data.
- Driving observability, performance, and reliability across the stack, including logging, tracing, rate limiting, and graceful degradation.
- Mentoring engineers, reviewing designs and code, and acting as a technical leader across a domain that is new, fast-moving, and security-sensitive.
What they're looking for:
- 8 to 10 years in software engineering, with a track record of owning systems end to end.
- Deep server-side expertise in TypeScript/Node.js or Python - both are actively used here.
- Strong, practical understanding of the Model Context Protocol - defining tools, resources, and prompts; writing tool descriptions that drive reliable model behaviour.
- Solid grounding in LLM tool-use and agentic patterns, including how models select and invoke tools, manage context, and handle multi-step interactions.
- Hands-on experience with OAuth 2.0, OIDC, JWT validation, and identity provider integration.
- Experience deploying and operating services at the edge or in serverless environments - Cloudflare Workers, AWS Lambda, Cloud Run, or similar.
- Security-first mindset; PCI DSS awareness is a strong plus.
- Awareness of AI-specific security concerns - prompt injection, over-broad tool permissions, and safe handling of model-driven actions.
- Comfortable operating as a team of one or scaling up to lead a broader group.
- BS or MS in Computer Science or equivalent practical experience.
Benefits: Work From Home
Principal Software Engineer - DevOps in Belfast employer: Ocho
Our client is an exceptional employer, offering a fully remote work environment across the UK and Ireland, which promotes flexibility and work-life balance. With a strong focus on engineering excellence and a culture that values outcomes over processes, employees are empowered to take ownership of their projects while benefiting from mentorship and growth opportunities in a fast-paced fintech landscape. The company also prioritises security and compliance, ensuring that team members work on cutting-edge technology in a supportive and innovative atmosphere.
StudySmarter Expert Advice🤫
We think this is how you could land Principal Software Engineer - DevOps in Belfast
✨Join Local Tech Meetups
Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Ocho or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!
✨Contribute to Open Source Projects
Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Ocho.
✨Tap into Online Developer Communities
Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Ocho.
✨Explore Job Boards Specifically for Tech Roles
Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Ocho that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!
We think you need these skills to ace Principal Software Engineer - DevOps in Belfast
Some tips for your application 🫡
Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.
Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Ocho.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Ocho and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!
Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!
How to prepare for a job interview at Ocho
✨Brush Up on Your Coding Skills
For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.
✨Know Your Tools and Frameworks
Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Ocho uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.
✨Showcase Your Projects
Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.
✨Prepare for Behavioural Questions
While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.
