Contribute to a Client Project

dOrg is set up to help members easily find high-quality work.

If you need any help at all, don’t hesitate to reach out to our Member Experience Facilitator

Joining a project

1. Find a project

The best place to search for open roles is the Help Wanted board. You can also browse the full Project Tracker or send a message on #job-board in Discord about your skills and the type of project you’re seeking.

2. Get approved to join

Reach out to the project’s Coordination Lead to find out more about the role requirements and project details. If it’s a match, the Coordination Lead will add you to the project’s syncs, chat group, budget sheet, and Airtable entry. After a few weeks of contributing, you can also request to be added as a signer to the project’s dedicated wallet.

Every client project has its internal flow of billing. Some pay on a set frequency (e.g. one a month) while others are based on milestones. Make sure to get the billing details from your project’s Coordination Lead.

3. Start contributing

  • Re-read our Development Best Practices
  • Familiarize yourself with the project’s SoW (find in Project Tracker) and other details like spec documents, repos, and project boards.
  • Attend weekly syncs. Make sure you are prepared and join a few minutes early with a stable internet connection and good audio.
  • Self-assign issues in the project board while communicating with other members to avoid overlap and ensure you are working on the highest priority tasks.
  • Log your work and time in the project's budget sheet before each payment checkpoint.
  • At each payment checkpoint, review your teammates' logs and sign-off on the transaction initiated by the Coordination Lead.
  • Participate in periodic feedback surveys and retro sessions initiated by the Coordination Lead.
  • If there’s any issue on the project, you can Flag an Issue or contact our ClientXP specialist


QA Lead

Each project must have a member with the QA Lead badge that has been designated to:

  • Own the code quality, making sure that our work product aligns with dOrg's Development Best Practices.
  • Ensure fit between the execution team and project requirements.
The precise responsibilities of the QA Lead will vary from project to project, but here are some recommended practices:
  • Make sure you understand all technical requirements, and ask if you don't.
  • Evaluate the experience level of each team member and offer mentorship if you see a need.
  • Evaluate risk and raise potential issues with other team members, the Coordination Lead, Sourcing Lead, or client as needed.
  • Review pull requests and assist in debugging.
  • Check for testing at different levels of the codebase.
  • Structure the continuous integration/deployment pipeline and application alerts.

Members can propose to issue the QA Lead badge to any member who:

  • Has a successful track record of building on dOrg projects and/or highly visible open source projects.
  • Is a confident communicator.
  • Knows the limits of their skills and how to identify expertise in others.

Coordination Lead

Each project must have a member with the Coordination Lead badge to:

  • Handle project admin and client communication.
  • Review work logs and process payments.
  • Monitor scope load and deadlines.

Members can propose to issue the Coordination Lead badge to any member who:

  • Has a successful track record helping to coordinate dOrg projects and/or highly visible open source projects.
  • Is a confident communicator.
  • Has shadowed a Coordination Lead for at least one week on an ongoing client project.