At a Glance
- Tasks: Build innovative products and tools for high-performance AI and cloud computing.
- Company: Join a fast-growing GPU cloud and AI infrastructure company with a mission to make an impact.
- Benefits: Enjoy competitive salary, flexible working, and 25 days holiday plus public holidays.
- Other info: Be part of a collaborative culture that values transparency and personal growth.
- Why this job: Take ownership of projects and solve complex problems in a dynamic environment.
- Qualifications: Experience in Go, Kubernetes, and a passion for building reliable systems.
The predicted salary is between 56700 - 69300 £ per year.
NexGen Cloud is a fast-growing GPU cloud and AI infrastructure business. We’re the company behind Hyperstack — a self-serve, on-demand cloud platform built for high-performance AI, HPC, and compute-heavy workloads. Powered by 100% renewable energy and NVIDIA architecture, Hyperstack gives teams from AI startups to enterprise the compute they need, without the cost or complexity of legacy cloud. We move fast, solve hard problems, and build things that matter. If you want ownership, real impact, and a front-row seat to one of the most consequential infrastructure shifts of the decade — this is the place.
Our hardest problems don’t stay in one layer. A customer issue can start in a web app and end in a Kubernetes scheduler, a container runtime or a GPU driver. We need engineers who can build the products, APIs and tools our customers use, and who understand the systems underneath well enough to make them work reliably in production. This is a role for someone who takes a loosely defined problem, works out what the user actually needs, and owns the solution end to end. That means designing it, writing the code, shipping it, and debugging it when it breaks, without handing it off at the first layer boundary.
What you’ll be doing:
- Own and drive user-facing products end to end, including web apps, APIs, backend services and CLI tools, mostly in Go. You’ll ship the simplest useful version first, then improve it based on how people actually use it.
- Collaborate closely with Product, Engineering & DevOps, Infrastructure & Data Centre Operations, Security and Customer Support. You’ll turn real customer problems into practical solutions.
- Build and maintain Kubernetes-based services, controllers and platform capabilities. This includes GPU scheduling and container runtimes.
- Identify repetitive operational work and replace it with automation, so software handles it instead of people.
- Investigate production issues across application code, Kubernetes, containers, Linux, networking, drivers and hardware. Each incident should end in a lasting fix, a guardrail or better tooling.
- Design services that behave well under load and during failure. You’ll instrument them so anyone can debug them, and give them secure defaults from day one.
- Contribute ideas and take ownership beyond your core remit. That includes product decisions on workflow and interface, such as whether a problem is best solved with a CLI, an API or a web experience.
About you:
We care more about how you think and work than a perfect CV. You’ll likely bring a combination of the following:
- Essential: Strong professional experience building, debugging and operating production software in Go. Deep experience in another systems language also works, if you can show you’d become productive in Go quickly.
- Hands-on experience with Kubernetes and containers, including how workloads are scheduled, how services communicate, and how to investigate when things misbehave.
- Confidence in Linux environments: systemd, processes, signals, filesystems, permissions, networking, and CPU and memory diagnostics.
- A track record of systems, products or tools you personally designed and built.
- Solid engineering fundamentals: concurrency, API and interface design, and failure modes. You’ll also have practical experience troubleshooting production systems with logs, metrics and system-level tooling.
Nice to have:
- Familiarity with the NVIDIA GPU ecosystem, such as drivers, CUDA, nvidia-smi, GPU-enabled container runtimes or Kubernetes GPU scheduling. This isn’t essential: strong systems debugging and a genuine interest in learning this area count just as much.
- Experience with distributed and event-driven systems, such as queues, retries, idempotency and backpressure.
- Practical networking knowledge (DNS, TCP/IP, HTTP, load balancing) also helps.
- Experience building Kubernetes controllers or operators, or developer tooling used by other engineers.
- A security-minded approach to auth, secrets and attack surfaces is a plus.
What we offer:
- Competitive salary and annual discretionary bonus scheme
- Employee wellbeing benefits
- 25 days holiday, plus public holidays
- Private Medical Insurance
- Enhanced Pension Scheme
- Flexible working arrangements (remote or hybrid, depending on role and location)
- Real ownership and autonomy — the trust to take initiative and experiment
- Visible, meaningful impact as we scale
- Clear career progression in a high-growth company
- A collaborative, international culture built on trust, transparency, and ownership
- The chance to help shape NexGen Cloud’s team, culture, and future
Why apply:
We welcome applications from all backgrounds. If you enjoy solving complex infrastructure problems and want to build something meaningful at scale, we’d like to hear from you.
Product Engineer in London employer: Academic Key
Deliveroo is an exceptional employer that prioritises the well-being of its employees while fostering a culture of innovation and collaboration. With a commitment to diversity and inclusion, we offer competitive benefits tailored to each country, including generous leave allowances and support for charitable causes. As part of a rapidly growing global team, you'll have the opportunity to work on impactful projects that shape the future of customer support, all while enjoying a dynamic and supportive work environment.
StudySmarter Expert Advice🤫
We think this is how you could land Product Engineer in London
✨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 Academic Key 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 Academic Key.
✨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 Academic Key.
✨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 Academic Key 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 Product Engineer in London
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 Academic Key.
Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Academic Key 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 Academic Key
✨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 Academic Key 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.