Devops Engineer in Amsterdam

• You will develop new tools and maintain the existing systems that make up the development infrastructure at Guerrilla.
• You will create innovative new ways to utilize our build farm and other distributed processes, improving our continuous integration builds and the tools that support them.
• You will improve our C++ tool-chains (Clang and Visual Studio), implement static analysis tools, improve our distributed build tools and organize our code base and documentation.
• You will design and implement new version control system tools (based on Perforce) so code and content can be more easily shared, both within the team and between the team and outside partners.

• You are an experienced C++ or Python programmer with an interest in both languages;
• You are passionate about programming and the tools that support it;
• You have worked as a tools developer or a devops engineer, preferably in the video games industry;
• You're comfortable working with a very large existing code-base and tool set;
• You enjoy working in an innovative, highly dynamic game development environment.

• You have experience with continuous integration or automated testing;
• You have experience with client-server programming and distributed processes;
• You have past experience with large, scalable systems and high performance computing;
• You have experience with native C# GUI applications;
• You have experience with front end web development;
• You have past experience in a similar position in the video games industry.

We review countless applications. Follow these golden rules when completing your application; 

Do:

• Upload a code sample in the form of a .zip archive containing:
• A number of at least 10 files that demonstrate your coding abilities;
• A readme document explaining what is in the file and what these files are expected to portray;
• A project that you are proud to share and are able to demonstrate verbally; 
• An example that shows an adequate amount of:  - Structure; - Complexity; - Efficiency; - Coding style and standards.

Don't: 

• Share complete projects that takes us alot of time to browse through to find the ‘example’ code; 
• Share links to online services such as github, bitbucket, dropbox, google drive, etc