🚨 This documentation is out of date.
View our New Documentation!
Open Collective Docs
Go back to Open Collective
  • Welcome
  • About
    • Introduction
    • Documentation
    • Terminology
    • Company
    • Pricing
    • Team
    • The Open Collective Way
      • Mission and Values
      • Community Guidelines
    • Hiring
    • Investors
    • Contributing
    • Refund Policy
    • Contact Us
  • Product
    • Features
    • Roadmap
    • Comparison
    • User Profile
    • Dashboard
      • Preview Features
    • Currencies
    • Log-in System
    • Privacy Policy
    • Moderation
    • Security
    • Ledger
      • Individual Transactions
      • Transaction Pairs, Groups & Perspectives
      • Viewing Transactions
      • Exporting Transactions
      • Fiscal Host Ledger Perspective
      • Contributions in the Ledger
      • Added Funds in the Ledger
      • Expenses in the Ledger
      • Ledger Changelog
    • Notifications
    • Two-factor Authentication
    • Activity Log
  • Collectives
    • Collectives FAQ
    • Creating a Collective
    • Quick Start Guide
    • Collective Settings
      • Customize Collective
      • Team
      • Collective Goals & Tiers
      • Expense Policy
      • Data Export
      • Security
      • Integrations
      • Zero Collective Balance
      • Closing a Collective
    • Add Fiscal Host
    • Change Fiscal Host
    • Open Source Collectives
      • Setting up GitHub Sponsors
    • Transparent Budget
    • Expenses
    • Updates & Comms
    • Custom Email
    • Moderation
    • Conversations
    • Events
    • Projects
    • Funding Options
    • Buttons & Banners
    • Connected Collectives
    • Contribution flow
  • Financial Contributors
    • Financial Contributors FAQ
    • Guest contributions
    • Payments
    • Platform Tips
    • Website Badge
    • Receipts
    • Collective to Collective
    • Organizations
      • Organization FAQ
      • Funds
      • Bulk Transfers
      • Gift Cards
      • Sustainer Resources
  • Expenses & Getting Paid
    • Expenses FAQ
    • Submitting Expenses
      • Inviting a third-party to submit an Expense
    • Expense Comments
    • Edit or Download an Expense
    • Receiving payment through Payoneer or Wise
    • Tax Information
  • Fiscal Hosts
    • Fiscal Hosts FAQ
    • Becoming a Fiscal Host
    • Creating a Fiscal Host
    • Organisation Settings
      • Info
      • Customize Profile Page
      • Connect external accounts
      • Accounting Categories
      • Security
      • Manage updates
      • Policies
    • Fiscal Host Dashboard
      • Expenses
      • Financial contributions
      • Pending applications
      • Hosted Collectives
      • Vendors
      • Transaction Report
        • Reports
    • Receiving Money
      • Bank Transfers
      • Credit Card
      • Add Funds Manually
      • Expected Funds
    • Payouts
      • Virtual Card Settings
      • Payouts with PayPal
      • Payouts with Wise
      • Two-factor authentication for payouts
      • Refunds
    • Host Fees
    • Local Tax Support
    • Agreement Templates
  • Independent Collectives
    • About Independent Collectives
    • Create an Independent Collective
      • Migrate from Self-Hosted to Independent Collective
      • Migrate from a Fiscal Host to Independent Collective
    • Independent Collective Setup
    • Independent Collective Management
      • Money coming in: Contributions
      • Money going out: Expenses
    • Close an Independent Collective
  • Contributing
    • Design
      • Design Workflow
      • Design Contribution Guidelines
    • Development
      • Contribution Guide
      • Best Practice Guidelines
      • Bounties
      • Architecture
      • API
        • Members
        • Collectives
        • Events
      • README Integration
      • PayPal
      • TransferWise
      • Post-Donation Redirect
      • Manual Reporting
      • GitHub Permissions
      • Internationalization (i18n) system
      • Testing with Cypress
      • Testing features
        • Conversations
      • Collective's locations
      • Virtual Cards
    • Documentation
      • Resources for documentarians
      • Style guide
      • Suggesting changes
    • Translation
  • Developers
    • OAuth
    • Personal Tokens
Powered by GitBook

Helpful Links

  • Website
  • Blog
  • Contact
  • Slack

Ⓒ Open Collective 2024

On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. About

Hiring

PreviousCommunity GuidelinesNextInvestors

Last updated 1 year ago

Was this helpful?

Interested in working at Open Collective? Check out our .

Every hiring process is different, and non-engineering/product positions often have a significantly different flow, but to get an insight into a past set of hiring processes, read on below.

~

Example Hiring process

Updated February 9th 2022

Screening 📺

General

Interested candidates are invited anytime to apply and write us a thoughtful message at any time. Simply dropping a CV is not enough, we want to see an appreciation of what we do and alignment with our values.

Once a week, we will look at current candidates and invite selected ones to the next stage. We, unfortunately, can't invite everyone, so if you don't make it to this stage and are still interested, please wait and contact us again in around ~3 months.

Product

Additionally, we want to see a history of working in a product capacity, perhaps on platforms like ours.

Engineering

To screen candidates, we also want to see a first contribution to our codebase as a PR in one of our GitHub projects. This can be anything but it needs to be mergeable. We suggest sticking to minimal complexity (a few minutes) to simple complexity (a few hours). This can be compensated through our Bounty program, with cash or gift card. If merged but there was no Bounty, we're happy to compensate at similar levels ($200 for simple complexity issues or $40 / hour)

From Screening to Test 👏

To formally meet and answer your questions, we'll schedule a short video call with the hiring manager. We'll assess your fit and try to figure out any blockers. To ensure a fit within the team we’ll schedule another call with one of the colleagues that you’ll be working alongside.

We regularly review new candidates and will invite selected ones to the next stage. We, unfortunately, can't invite everyone, so if you don't make it to this stage and are still interested, please wait and contact us again in around ~3 months.

Engineering

To formally meet and answer your questions, we'll schedule a short video call with our CTO. We'll assess your fit and try to figure out any blockers.

Test ⌛

For selected candidates, we would like you to complete a medium complexity task that you would typically perform as part of your role (~4 hours completion time):

You can make reasonable requests for information about our business in order to complete the assignment. You can collaborate with other team members. This will be compensated at the market rate/hour. This will be presented to and reviewed by both the hiring manager and a team member.

This test may be a pairing exercise, a product review, a solution design or some other task depending upon the role you are applying for.

From Test to Trial 🤔

Engineering

You'll have a call again with our CTO, we'll mutually assess if your test was a success. If it does, we'll start scheduling the next stage.

Trial 🤓

The final step is an invitation to spend a few days (2 to 5 days) working with the team. Thid will be on some sort of small project, or on various issues, pairing with others, and participating to daily calls. It is similarly compensated.

Concurrently, you will have a video call with one or more members of our leadership team and/or CEO.

Offer 🙌🎊

Lastly, if the trial is success, we will ask to continue working with you. (Celebrate!)

hiring page here