Senior .Net Product Engineer

London
10 months ago
Applications closed

Related Jobs

View all jobs

Data Engineering Product Owner, Technology, Data Bricks, Microsoft

Senior Data Engineer - Azure & Snowflake

Senior Data Governance Analyst

Senior Data Engineer

Senior Data Engineer

Senior Data Engineer (Big Data/ Hadoop/ Spark) (Banking)

Role: Senior .Net Product Engineer (FinTech)

Office Location: London

Working Model: Fully remote working model with quarterly socials/team events.

Salary: £60-75k plus benefits

Do you hate being bored?

Does being shoved into a silo for the rest of your career fill you with dread?

Do you want your hard work to make a real difference in a company?

If your answers to these questions is a very loud ‘YES!’, then here’s the role for you!

One of my favourite sayings is ‘the people make the place’ and that couldn’t be truer of this company.

It’s rare to find such a good blend of cool, interesting work and really wonderful people- the CTO is one of the most caring, effective, and genuine people you could hope to meet, and to add credence to this statement is the fact that the people who have worked for him before having sung his praises to me.

In this role, you’ll go into a tiny company of just shy of 10 people who are mostly software engineers of varying levels of seniority (but mostly on the more senior end, currently). You’ll be using a real mix of tech, including:

C#

.Net 8+

TypeScript

MariaDB (will likely move to a different NoSQL DB at some point)

GCP (you can have used other Cloud providers like AWS or Azure)

PHP (their legacy code is PHP- you’ll have to interact with it, but it is being deprecated)

Docker

Naturally, whilst it’s important that you’ve got the skills above to do the role, the most crucial thing they are looking for is attitude. You can teach skills; you can’t teach someone to have a good attitude!

They look for self-starters who take the initiative, who are curious and ask questions, who are upbeat, and want to muck in with whatever task is up next. If you’ve ever found yourself saying ‘that’s not my job’, it’s likely you’ll not be right for this role.

You’ll get involved in a wide variety of projects, in a nimble, fun, and engaging role, surrounded by intelligent, collaborative, and supportive people that will use your existing skills to their full extent, give you the chance to widen your knowledge base significantly, and have a great time doing it!

They might get an office in Nottingham to go into once per week, in the future, so living in a commutable distance from Nottingham would be beneficial.

If this sounds right up your street, please apply now or get in touch to find out more!

We welcome diverse applicants and are dedicated to treating all applicants with dignity and respect, regardless of background

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

How Many Data Engineering Tools Do You Need to Know to Get a Data Engineering Job?

If you’re aiming for a career in data engineering, it can feel like you’re staring at a never-ending list of tools and technologies — SQL, Python, Spark, Kafka, Airflow, dbt, Snowflake, Redshift, Terraform, Kubernetes, and the list goes on. Scroll job boards and LinkedIn, and it’s easy to conclude that unless you have experience with every modern tool in the data stack, you won’t even get a callback. Here’s the honest truth most data engineering hiring managers will quietly agree with: 👉 They don’t hire you because you know every tool — they hire you because you can solve real data problems with the tools you know. Tools matter. But only in service of outcomes. Jobs are won by candidates who know why a technology is used, when to use it, and how to explain their decisions. So how many data engineering tools do you actually need to know to get a job? For most job seekers, the answer is far fewer than you think — but you do need them in the right combination and order. This article breaks down what employers really expect, which tools are core, which are role-specific, and how to focus your learning so you look capable and employable rather than overwhelmed.

What Hiring Managers Look for First in Data Engineering Job Applications (UK Guide)

If you’re applying for data engineering jobs in the UK, the first thing to understand is this: Hiring managers don’t read every word of your CV. They scan it. They look for signals of relevance, credibility, delivery and collaboration — and if they don’t see the right signals quickly, your application may never get a second look. In data engineering, hiring managers are especially focused on whether you can build and operate reliable, scalable data systems, handle real-world data challenges and work effectively with analytics, BI, data science and engineering teams. This guide breaks down exactly what they look at first in your application — and how to shape your CV, portfolio and cover letter so you stand out.

The Skills Gap in Data Engineering Jobs: What Universities Aren’t Teaching

Data engineering has quietly become one of the most critical roles in the modern technology stack. While data science and AI often receive the spotlight, data engineers are the professionals who design, build and maintain the systems that make data usable at scale. Across the UK, demand for data engineers continues to rise. Organisations in finance, retail, healthcare, government, media and technology all report difficulty hiring candidates with the right skills. Salaries remain strong, and experienced professionals are in short supply. Yet despite this demand, many graduates with degrees in computer science, data science or related disciplines struggle to secure data engineering roles. The reason is not academic ability. It is a persistent skills gap between university education and real-world data engineering work. This article explores that gap in depth: what universities teach well, what they consistently miss, why the gap exists, what employers actually want, and how jobseekers can bridge the divide to build successful careers in data engineering.