Lead .NET Developer (IoT sphere)

Our client is a global leader in access solutions and products. The company designs and engineers residential garage door openers, commercial door operators and gate entry systems.

The person will work as a tech lead with the group of .NET developers responsible for the platform performance, new features, and integrations.

• Work using Agile methodologies such as Scrum or Kanban to develop middleware;
• Participate in technical assessment, scoping and management of changes to the code-base on new business requirements, product enhancements and other change requests;
• Propose and discuss tech design for the new features and domains;
• Maintain domain specific software knowledge of key software application features, frameworks, or components in myQ middleware;
• Contribute to technical discussions in community of practice, design review, pull request, or other technical meeting forums;
• Collaborate with other Chamberlain domain experts, such as infrastructure, database, and front end, as the team develops features and platform enhancements;
• Ensure adherence to coding standards and other best practices to create reusable code;

• Bachelor’s Degree in Computer Science or engineering related field;
• 5+ years of job-related experience;
• Understanding of Agile methodologies;
• Experience in creating technical documentation;
• Ability to work well with others and provide clear direction to a development team, as well as mentoring skills;
• Strong analytical and problem-solving skills;
• Good written and verbal English (B2 as a must);
• Application troubleshooting skills ( CPU issues ,memory leak issues, deadlocks, sockets and so one);
• Knowledge of Kubernetes and containers;
• Knowledge of MS SQL;
• Knowledge of  no SQL DB (CosmosDB, couchbase);
• Knowledge of messaging systems (RabbitMQ);
• Experience in writing effective asynchronous and parallel code;
• Knowledge of design patterns, enterprise application patterns and cloud design patterns experience with microservices architecture;
• Experience with DDD and DDD architecture types (onion, clean, hexagon, etc.);