C# Developer Azure Cloud -- 2
Budget: €35 – €70 EUR
ekey biometric systems is a pioneer in the field of fingerprint based access solutions in Europe and founded in 2002. ekey currently employs over 100 people at its 5 locations in Austria, Germany, Liechtenstein/Switzerland, Italy and Slovenia and exports its products to more than 70 countries. The export share is about 80%. Other important sales markets are France, Poland, USA, Russia and China.
https://www.ekey.net/en
We are looking for C# Microsoft Azure backend developers on experts level. We often corporate with freelancers and nearshore partners, but we don’t outsource complete working packages or projects. Basically we follow the principle that we add external developers into our Scrum-Teams like native members. The developers join the Scrum meetings remotely by Microsoft Teams. The backlog, PBIs, Sprint Planning and so on are handled by Azure DevOps. We decided to go such a way, because we had in the past a lot of troubles with software quality, test depth, ignored refactoring needs and so on by outsourcing of complete projects. With this approach we made good experience in the past.
Follow the link to understand what we are doing.
https://www.youtube.com/watch?v=OHYK0VBo5vM
Our main pain point in this situation is the language. All documents linked to the project (Wiki page, software architecture docs, backlog, story maps,…) are in German. This means we will hire only developers who speaks/writes fluently German. Otherwise a real boost of development velocity will not be given.
I also added a shortened version of the vacancy notices.
https://www.ekey.net/en
We are looking for C# Microsoft Azure backend developers on experts level. We often corporate with freelancers and nearshore partners, but we don’t outsource complete working packages or projects. Basically we follow the principle that we add external developers into our Scrum-Teams like native members. The developers join the Scrum meetings remotely by Microsoft Teams. The backlog, PBIs, Sprint Planning and so on are handled by Azure DevOps. We decided to go such a way, because we had in the past a lot of troubles with software quality, test depth, ignored refactoring needs and so on by outsourcing of complete projects. With this approach we made good experience in the past.
Follow the link to understand what we are doing.
https://www.youtube.com/watch?v=OHYK0VBo5vM
Our main pain point in this situation is the language. All documents linked to the project (Wiki page, software architecture docs, backlog, story maps,…) are in German. This means we will hire only developers who speaks/writes fluently German. Otherwise a real boost of development velocity will not be given.
I also added a shortened version of the vacancy notices.