Senior Low-Latency C++ Engineer — Remote

Senior Low-Latency C++ Engineer — Remote

Full-Time 81000 - 99000 £ / year (est.) Working from home possible
W

At a Glance

  • Tasks: Design and optimise performance-critical components for automated trading.
  • Company: Leading global trading firm with a focus on innovation.
  • Benefits: Top market rates, remote work, and potential for permanent role.
  • Other info: 12-month remote engagement with excellent career progression.
  • Why this job: Join a selective team and make a real impact in trading technology.
  • Qualifications: Extensive C++ experience and a passion for low-latency systems.

The predicted salary is between 81000 - 99000 £ per year.

The NDA-listed Global Trading Firm is seeking a senior, hands-on C++ engineer to own the low-latency hot path for automated trading.

You will design, implement, and optimize performance-critical components in production, working alongside traders and quants.

This is a 12-month remote engagement (UK, NL, FR) with conversion to a permanent role by mutual agreement.

You will operate in a highly selective environment benchmarked to top-of-market rates for senior low-latency engineers.

#J-18808-Ljbffr

Senior Low-Latency C++ Engineer — Remote employer: Whyhirewrong?

Join a top-tier global trading firm that values exceptional talent and offers a fully remote working environment from the UK, Netherlands, or France. With a focus on employee growth, you will have the opportunity to work on performance-critical systems alongside traders and quant researchers, while enjoying highly competitive compensation benchmarked to market rates. Our culture promotes innovation and collaboration, ensuring that your contributions are recognised and impactful in the fast-paced world of electronic trading.

W

Contact Details:

Whyhirewrong? Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Senior Low-Latency C++ Engineer — Remote

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 Whyhirewrong? 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 Whyhirewrong?.

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 Whyhirewrong?.

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 Whyhirewrong? 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 Senior Low-Latency C++ Engineer — Remote

C++
Low-Latency Programming
Performance Optimisation
Automated Trading Systems
Component Design
Production Implementation
Collaboration with Traders

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 Whyhirewrong?.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Whyhirewrong? 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 Whyhirewrong?

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 Whyhirewrong? 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.