|
1 | 1 | ## What is a Contributor+ (C+)? |
2 | 2 | C+ are contributors who are experienced at working with Expensify and have gained the confidence of the internal Expensify team. Accordingly, they are allocated additional opportunities and responsibilities: |
3 | | - - They review proposed solutions in external GitHub issues, validate them, and make recommendations to an internal Contributor Manager Engineer (CME). |
4 | | - - Once a proposal has been accepted by a CME, the C+ will be the first person to review the pull request associated with that proposal. |
| 3 | + - They review proposed solutions in external GitHub issues, validate them, and make recommendations to an internal Contributor Manager Engineer (CME). |
| 4 | + - Once a proposal has been accepted by a CME, the C+ will be the first person to review the pull request associated with that proposal. |
5 | 5 |
|
6 | 6 | ## Why would someone want to be a C+ |
7 | | -- C+ are compensated the same price as the contributor for reviewing proposals and the associated PR. (ie. if a job is listed at $1000, that’s how much the C+ will make if they review both the proposals and PR). If regressions are found that should have* been caught after the PR has been approved, C+ payment is reduced by 50% for each regression found. |
| 7 | +- C+ are compensated the same price as the contributor for reviewing proposals and the associated PR. (ie. if a job is listed at $250, that’s how much the C+ will make if they review both the proposals and PR). If regressions are found that should have* been caught after the PR has been approved, C+ payment is reduced by 50% for each regression found. |
8 | 8 | - * Should have = C+ should have caught the bug by fully following the PR checklist. If C+ skips a step or completed the checklist incompletely, payment will be cut in half. |
9 | 9 | - C+ can also work on jobs as a contributor. |
10 | 10 | - Earning potential is variable, it depends on how much a C+ wants to work and other jobs they’re hired for. We’ve seen C+ make ~$100k/year. |
11 | 11 | - There isn’t a set number of hours a C+ needs to work in a week. Proposals and PRs reviews are expected to be addressed within 24 hours on weekdays. |
12 | | -- Dedicated #contributor-plus Slack room to discuss issues, processes and proposals. |
13 | | -- If C+ ever applies to work at Expensify, they’ve got a leg up on the competition because they're familiar with the company and processes. View job openings at https://we.are.expensify.com. |
| 12 | +- Dedicated #contributor-plus Slack room to discuss issues, processes and proposals. |
| 13 | +- Opportunity to work on projects and design docs for new features. |
| 14 | +- A contributor must be a C+ to be considered to become a Backend Contributor. |
| 15 | +- C+ are already familiar with the team, company, and processes, which may help when applying for full-time roles. One C+ has been hired full-time. View current openings at https://we.are.expensify.com |
14 | 16 |
|
15 | 17 | ## Requirements to join C+ |
16 | | -- Have had 30 PRs deployed to production without regressions. |
| 18 | +- Have had 30 PRs deployed to production. |
17 | 19 | - Follow our Code of Conduct, Contributing.md and README.md docs and processes. |
18 | 20 | - Comment and fix bugs in a timely manner. |
19 | | -- Clear communicator |
| 21 | +- Clear communicator. |
20 | 22 | - Bonus points: |
21 | 23 | - Help other contributors by commenting on their issues. |
22 | | - - Actively involved in the #expensify-open-source slack channel |
23 | | - - Adheres to the PR review guidelines |
| 24 | + - Actively involved in the #expensify-open-source slack channel. |
| 25 | + - Adheres to the PR review guidelines. |
24 | 26 |
|
25 | 27 | ## How to join? |
26 | 28 |
|
|
0 commit comments