2022 - Hiring for Developer Division Teams in Prague, Czech Republic
As of 2022/7/5, we do NOT have open positions in Developer Division teams in Prague, Czech Republic.
Positions already filled:
C++ compiler team- apply forSWEorSenior SWE(with 6+ full-time experience)Hiring started on 2022/5/18 - seeLinkedIn post- position closed on 2022/7/5
ASP.NET Core Blazor team- apply forSWEorSenior SWE(with 6+ full-time experience)Hiring started on 2022/5/18 - looking for multiple positions - seeLinkedIn post- position closed on 2022/7/5
.NET Engineering Services team- apply forSWEorSenior SWE(with 6+ full-time experience)To learn about the team charter, see 2 blog posts:post from 2019andpost from 2020Hiring started on 2022/5/8- remaining position closed on 2022/7/5
ARM64 ecosystem team- apply forSWEorSenior SWE(with 6+ full-time experience)Hiring started on 2022/5/18 - looking for multiple positions - seeLinkedIn post- position filled on 2022/6/28
.NET Runtime team- apply forSWEorSenior SWE(with 6+ full-time experience)Hiring started on 2022/5/18 - looking for multiple positions - seeLinkedIn post- position filled on 2022/6/28
.NET Performance team- apply forSWEorSenior SWE(with 6+ full-time experience)- position filled on 2022/6/9Hiring started on 2022/5/18 - seeLinkedIn post
F# Tooling team- seefull job description- positions filled on 2022/6/9Hiring started on 2022/3/11
.NET Networking team- onTwitterorLinkedIn- position filled on 2022/6/9Seethis postto learn what the team does, and where it is heading.Hiring started on 2022/5/8How to apply?-- reach out directly to team manager@ziki_cz(Twitter DM is prefered, see my profile for other contact info)Start discussion with answers to these 2 questions - to see if it makes sense to apply to the job post:What is your related library-level, system-level or networking-related experience from work or hobby projects?Describe some interesting technical challenge (ideally related to the job). An investigation, bug fix or feature, etc. Something you are proud of.
Details:Library-level = producing libraries used by multiple projects, ideally by multiple companies.System-level = anything low-level, close to OS APIs, drivers, HW interaction, or some non-trivial backend (e.g. difficult multi-threading, scale).Networking = libraries / APIs / protocols operating on network to communicate between computers. Server-side, or client-sie, or both.