Backend Engineer

Let's start with the role

You will join an autonomous Agile team and work closely with the Product Owner, Agile Delivery Lead, Automation Testers and other Software Engineers to create a competitive advantage for Kaizen and offer a unique online experience to our customers.

Software engineers in Kaizen are responsible for a multitude of projects, from our customer-facing websites and mobile applications to our admin and internal tools and backend services, most of them withstanding high volume / traffic.

• Create new solutions and see them through, from conception to production;
• Turn requirements into simple and sophisticated technological systems. Our large scale, highly available infrastructure is at the core of that challenge;
• Design, build, and maintain efficient, reusable, and reliable code;
• Research new technologies to find new and efficient ways to solve day to day challenges;
• Ship high-value features quickly;
• Challenge the status quo and improve the team and product.

Most of our sites and services are written in C# / ASP.NET and new services are written in .NET Core. New applications use vue.js in the front-end while older ones use server-rendered (Razor) views in combination with jQuery & Knockout.js. MS SQL Server is used for most of our storage needs, but also uses Redis and ElasticSearch when it makes sense to do so. RabbitMQ is our go-to message broker. We use Gitlab for code versioning and CI, and the Atlassian stack for tickets and documentation.

What you'll bring

• At least 2 years of experience developing production-level software using Microsoft .NET (full framework or .NET Core);
• Proficient in C# and MVC;
• Good understanding of basic web technologies, such as HTTP, REST, etc.;
• Practical understanding of algorithms and design patterns;
• Passionate about delivering high-quality code;
• Fluent in English, both oral and written.
• Strong work ethic and eagerness to take initiative with a can-do attitude.

Nice to have:

• Expertise in concurrency, multithreading, and event-driven architecture;
• Exposure to distributed applications that are secure can scale and are highly available.