Asynchronous communication - OpenCraft endeavours to make as many of our processes as asynchronous as possible so that no one has to work outside their preferred hours. Our sprint planning process is asynchronous), and while you may occasionally need to meet with a teammate or client outside your preferred time window, it's not the norm.

Generally, discussions happen first asynchronously; if there is really something that can't be efficiently sorted out asynchronously, have a chat or schedule a meeting.

Company retreats - We meet yearly in person at the Open edX Conference (in non-Covid times!), and use the opportunity to meet everyone, along with the rest of the community, and do a team retreat.

Flexible hours - We are all working remotely, from all continents (except Antarctica, at least so far - applicants welcome!). We use remote-friendly and timezone-agnostic workflows based on asynchronous principles and good documentation practice

Light meetings - We have minimal meetings, as all our communication is centered around asynchronous processes - including sprint planning!

Open source - The code we write is almost exclusively open source, and we contribute it upstream – furthering online education through the OpenedX project.

Autonomy - We have built a mostly flat organization, composed of 30 senior developers with a handful of support staff. You will be working with highly competent individuals who take responsibility for their work, and the same will be expected of you.

We belong to self-organized teams, so management doesn’t interfere with our day-to-day responsibilities and leadership is situational. You will lead some projects and join others. You will have a great deal of discretion in the work that you do.

Open communication - Our open-first philosophy keeps us honest and pushes us to bettering ourselves and our community. We believe in contributing back, and finding better ways to collaborate and work. We share the knowledge that we’ve gained instead of hoarding it.

Work with the founder - We have a flat hierarchy, and the founder is actively involved in team and direct discussions, as well as projects any team member can participate to.

Agile development - We use an agile workflow (scrum) based on two-week sprints, but these are coordinated and planned asynchronously.

Time tracking - When you sit down to work for OpenCraft, start to log immediately. The time spent thinking about what you're actually going to work on, preparing your environment by spawning a devstack, etc. is part of the work (sometime called metawork). It also involves going through mail, chat and forums to check in case something relevant came up. Whatever ticket you start working first is where you should log this time.