Programming Internships

It depends on your specific talents and interests as a programmer. Our primary focus is on building our open source game engine, which includes graphics rendering, audio playback, and a scripting language.

We do most of our programming in C++ and Python, with some C and Bash. We also use HTML, CSS, and ReStructuredText.

Yes, as long as you're willing to learn something new. Most of our interns had never used C++ before this.

All our work takes place on Ubuntu. We use the Clang compiler for C and C++. Our technology stack and tools are all 100% open source software. You can find a complete list of technologies here.

Programming interns must have private, administrator access to a computer with the following minimum specifications.

• Ubuntu 20.04 or later, or alternatively another Debian-based Linux. We can help with setup.
• RAM: 4GB minimum, 8GB or more recommended.
• Processor: 2GHz speed or better.
• Hard Drive: 250GB free space minimum (or 200GB minimum after Linux installation.)
• Display: 1024x768 minimum.
• Reliable high-speed internet connection.
• Webcam.
• Microphone.

No. We have many reasons for using Linux as our development environment, compatibility being a big one. It is also a vital industry skill to be able to use Linux. In short, it is mandatory.

We have carefully selected each of our technologies, based on multiple criteria. While we are not closed to suggestions, be aware that we've already considered most popular technological options.

There are a lot of fantastic books and online courses to teach you the basics of programming, and thousands of open source projects with which to get your feet wet! Once you have the basics down, come talk to us.

Yes. We have a full Git repository system, with pre- and post-commit code review tools and linters via a platform called Phabricator.

Yes. Our code projects use CMake and Makefiles to allow building with one command.

Yes. Every time code is committed for the mandatory pre-commit review, it is automatically built by Jenkins.

Yes. Our task list has an integrated bug database, and that in turn links to all the code review tools. It's a beautiful thing.

Yes, as much as is sane. There is no such thing as "perfect code," but it has to be stable and work well before we add to it.

Yes. We employ Agile Scrum to plan our work, monitor our progress, and adapt to changes.

Yes. We have a wiki that hosts as our specs, which means that we can continually revise as we learn. Our specs are living documents - as we garner the necessary information to make informed decisions, we update and expand.

Yes, in that everyone works from home.

Yes. We carefully selected the best that open-source software has to offer for development, including Git, Phabricator, Jenkins, and Mattermost.

Yes. First, we have a carefully curated test system. Jenkins automatically runs many tests on code sent for pre-commit review. Further tests can be run manually by developers. In addition, our games go through rigorous testing before final release.

Yes. You will complete a short coding challenge, which you have a week to complete at your own pace — it takes about two hours — and with your favorite tools and languages, so you can show us your current skills. You will also do live coding in the final interview. (Don't worry; we know how to account for both nerves and inexperience.)

We do not use "fizz-buzz" or whiteboarding challenges. Our coding challenges are practical and original to us. We also NEVER use code from the interview process in any of our projects.

Yes. We use our own code in production, and test each other's code as part of the review process!