Organizational structure#


This page is a work-in-progress as we define the major organizational areas of 2i2c. Some links might be missing or in-the-works!

This section describes the major structure of 2i2c and how it is broken into functional groups and teams. Note that 2i2c is a young and small organization, so many areas have a small number (or nobody) dedicated to work within them. We nonetheless document these structures to understand how our work and responsibilities are divided, and to provide a roadmap for new hires and division of labor.

Fiscal sponsorship#

2i2c is a fiscally sponsored project of Code for Science and Society, a US 501(c)(3) public charity1.

Steering Council#

The Steering Council defines the mission, vision, and values of 2i2c. It also provides oversight to the Executive Director.

Membership: Listed on the 2i2c website.

Communication: The Steering Council Google group ( is the only “official” way to communicate with others on the Steering Council.

Executive Director#


Ensures that 2i2c has the right strategy, structure, resources, and alignment to accomplish its mission. Oversees the creation of 2i2c’s strategic planning and coordination, and actively engages the Steering Council and others at 2i2c in these efforts.

The Executive Director oversees each functional area, and makes tie-breaking decisions if they are at an impasse in decision-making.

Relationship to others#

The Executive Director reports to the Steering Council.

Group leads of 2i2c report to this role.

They are currently the primary interface to CS&S administration.

Membership: The current Executive Director of 2i2c is listed on the Our Team page of the website.

Functional areas#

Functional areas are organized around responsibilities, skills, and career tracks. Reporting lines are within a functional area, meaning that team members should report to somebody that has held a similar job in the past.

  • Engineering: Develop and operate our technical and cloud infrastructure, to ensure that it is reliable and scalable.

  • Product: Understand the perspective of our partner communities and guide the evolution of our infrastructure and services, in order to ensure they have a positive impact.

  • Community: Guide and support the partner communities that we serve, to help them utilize our infrastructure in a way that aligns with 2i2c’s mission.

  • Partnerships: Identify opportunities for impact, cultivate new relationships, and oversee our sustainability plan to ensure that we have sustainable and scalable impact.

  • Operations: Oversees our systems for coordination, planning, and executing our work according to our goals.

  • Administration: Carry out ongoing organizational tasks that are needed to keep 2i2c running on a daily basis.

Cross-functional teams#

Cross-functional teams consist of team members from various functional areas, and are organized around a specific goal, service, or product. Teams should generally have members with the right skills and authority to accomplish the entirety of the team’s goal. They might be temporary or semi-permanent.

Teams often share a backlog that describes their goals and work items, and may also share a project manager that oversees coordination and execution of work.

They also often have team meetings to facilitate discussion and information flow across functional areas.

There are two main teams within 2i2c, both revolving around major aspects of our Managed Hubs Service:

  • Area leads: Goal is to align on our major goals, strategy, and operations across the leaders of each functional area.

  • Product and Engineering: Goal is to design, develop, and improve the Managed JupyterHub Service technology and end-user experience.

  • Community and Partnerships: Goal is to cultivate relationships with new partnership communities, support and engage with our active partnerships, and use these relationships to feed into 2i2c’s sustainability model.


It was originally founded as a project of the International Computer Science Institute.