

Laptop Stickers by Fred Benenson CC BY. Does your laptop look like this? It doesn’t have to, but we wouldn’t be surprised if it does.

Since our previous CTO, Nathan Yergler, left CC to return to full-time engineering in April, we have been preparing to recruit his replacement. The time is now! See the full job posting on our opportunities page.

This is a fun job (I was Nathan’s predecessor, from 2003-2007) that offers technical, management, and communications challenges and opportunities for growth and impact. Using technology to enhance (rather than suppress) sharing has always been an important part of the CC story. Some background for the truly interested candidate:

All software developed by CC is free software; see our source repositories and bug tracker;

We have a small (two software engineers, one system administrator) technology team focused on maintaining and improving CC’s services (implemented using Python, CiviCRM, WordPress, MediaWiki, and other technologies); additionally technology suffuses all of our work, including when policy-oriented — the technology team and especially CTO are frequently called on to provide leadership on broad issues;

See our CC Labs blog for occasional posts on the details of our technical work and thoughts on related happenings;

Watch recordings of past CC technology summits;

Read about the CC Rights Expression Language, a set of recommendations implemented across CC’s services and by many publishers.

Relative to when Creative Commons started with a vision of leveraging the Internet to scale sharing (and vice versa), there are an unimaginable number of freely licensed works to build upon, and to build services around, and 90% of the technical groundwork is laid (of course as an engineer you recognize that means 90% of the technical groundwork remains to be developed — and that’s just the beginning!). Now is an incredibly exciting time to lead the technology efforts of Creative Commons — be part of a great team, help communities yearning to share better and more effectively (e.g., see our new Learning Resources Metadata Initiative), and engage with developers around the world to help build a better future.

We’re accepting resumes through August 1. Again see the job posting for details.