Skip to content

Editorial Recruitment

Alex Wermer-Colan edited this page Nov 8, 2022 · 1 revision

The Programming Historian regularly recruits new editors for its languages.

Recruitment Process for new Editors

This process should be led by the language teams Managing Editor. The process is usually as follows:

  1. Identify a need & discuss it with your team, including timelines
  2. Adapt an old advert from the blog to meet new needs
  3. Post and disseminate
  4. Prepare a set of questions and interview a subset of applicants
  5. Select suitable candidates
  6. Invite them on an agreed term (3 years is ideal)
  7. Send editors to our Publishing Assistant for onboarding and refer them to our Onboarding docs
  8. Set up meetings with ME and other editors for additional training and team building

Interview Questions for Candidates

Interview questions for the recent English team's interviews included the following:

  • Why are you interested in this position, and what would you bring to this role?
  • What kind of editorial experience do you have?
  • How comfortable are you working in GitHub?
  • What experience do you have working on a distributed team?
  • What kinds of lessons or other work would you like to see PH take on?

Sample Calls for New Editors

New Wiki (in-progress)

Publishing Tasks

Phase 1 Submission

Phase 6 Sustainability Accessibility

Phase change templates

Communications

Social Media

Bulletin

Events

Call Packages

Administration and Documentation

Members

Internal records

Resource indexes

Lesson Production and Development

Language and Writing

Accessibility

Governance

ProgHist Ltd


Old Wiki

Training

The Ombudsperson Role

Technical Guidance

Editorial Guidance

Social Guidance

Finances

Human Resources

Project Management

Project Structure

Board of Trustees

Clone this wiki locally