Position Available Senior .NET Software Engineer

Your strength is back end business intelligence - you don't want to get involved in designing buttons on screens.

We have other teams responsible for the infrastructure (Linux, Apache, IIS, Node.JS and PHP). You'll be focussed on writing code to run on that infrastructure.

Yes, you'll be working with MySQL at times but only through entity framework, so you won't have to worry about the MySQL servers themselves.

Some of our microservices work with mongodb

SQL Server experience is desirable but definitely not essential. We work with SQL Server in some parts of the back end systems, as well as on every till.

Our caching uses Redis via Amazon's elasticache.

MySQL is used for some parts of the back end, accessed through entity framework. In particular we use Amazon Aurora.

A million transaction events per second. Businesses across the world depend on you. A world leading Electronic Point of Sale (EPOS) system that cannot fail.

Imagine yourself helping design and build this system that can handle the data from millions of supermarket checkouts all across the world. Imagine helping these retailers run their businesses smarter, thanks to the code you write. Retailers from all over the world.

Processing millions of events per second, we are building the world's largest event driven EPOS system - and you'll be part of the core team developing it.

You'll be working on our epos software applications, which includes the till software, back office and head office systems.

Experience of working in a retail IT environment will obviously be a big benefit, but absolutely not essential. Some of our best people have no retail experience whatsoever.

Everything you need to know will be taught on the job.

You consider yourself a top level C# .NET developer. There's not much you don't know about C#, and if there is, you know how to find out the answer on the internet.

Ideally you'll have already worked with C# 6.0, but if not, you know it'll only take a few days until you'll be fully comfortable with the changes.

If you have experience of .NET Core it would be an advantage, but if not don't worry, as you'll very quickly get used to it.

Every engineer deploys on his or her first day — and every day after that too.

We use Amazon Web Services and practice continuous deployment so we can quickly try out new ideas and iterate on existing product features.

Event sourcing will be a BIG part of your life working with us.

We work extensively with Event Store, a database with complex event processing - it works, and its very, very fast. It has a native .NET client which makes working with it extremely easy.

We don't expect you to have any knowledge in this area, but you will learn a lot about it working with us.

We work in an agile environment, with SCRUM meetings.

You'll work in a team that regularly creates work items from the gherkin requirements, and then everyone can get to work on the work items.

You'll need to be very comfortable with Visual Studio.

Since we're a MIcrosoft certified partner, you'll always be using the latest version.

We use domain driven design extensively in VME. If you've never worked this way before, prepare to be impressed.

DDD ensures our code uses the same terms and 'language' as our business domain experts - making life a lot easier for everyone, especially software engineers.

If you're interested, this is the best book on the subject.

Our team of domain experts are responsible for providing you and the others in your team clear requirements in gherkin syntax.

If you're not familar with Gherkin don't worry, you soon will learn to love it, as it makes your job much, much easier - giving you more time to focus on how to implement the requirements.

Command Query Responsibility Segregation, better known as CQRS, is, alongside event sourcing, another big part of our systems. Your experience of this would be a bonus but again if you've not worked with it before, you'll soon learn.

Essentially a separation of concerns, it splits the read and write models into different areas, which is especially important as a lot of our system is eventually consistent.

We didn't have a good enough picture to describe CQRS, so here's a picture of some cute puppies instead.

We use XUnit, but experience in NUnit or MS Test would also be useful.

We use Moq, but experience of any mocking framework would be useful.

We are only interested in your .NET skills. If you have a degree, great - but we'll not discount your application if you don't.

Ideally you'll be very familiar with at least version 4 of Entity Framework, although we are now moving onto Entity Framework 7 on some projects (recently renamed to Entity Framework Core 1.0)

You'll be using Code First, mainly because we use Domain Driven Design.

If you've never worked with Code first before, you'll be keen to learn. Once you've left database first behind, you won't want to go back!

You may have experience of working with AWS, Amazon's cloud, but its not a requirement for this job.

We do work heavily with AWS, using EC2 in VPCs, RDS, SQS, SNS, SES, S3, Cloudfront, DynamoDB and Route53. If these acronyms don't mean anything to you, don't worry - you'll soon be able to class 'AWS' as one of your skills as we'll teach you everything you need to know.