empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 17:05:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

RIP "👩‍🏭 Roles (job descriptions)" (#10333)

Browse Source 
["👩‍🏭 Roles (job
descriptions)"](https://docs.google.com/document/d/1wS5jFfrZtO4xMH-3U_S8pE59gNXOTR3rS1WWD8pkq9E/edit#heading=h.9o3hx5rchpit)
is now fleetdm.com/handbook/company#open-positions


Relates to https://github.com/fleetdm/confidential/pull/2132

.
This commit is contained in:
Mike McNeil 2023-03-07 03:27:15 -06:00 committed by GitHub
parent 37e4ad8c16
commit 7fdf15a29f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 36 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

61
handbook/business-operations/README.md
View File

@ -289,32 +289,43 @@ When the final signature is added to an envelope in DocuSign, it is marked as co
### Creating a new position
Every new position being created goes through this process before interviewing, accepting applicants, or extending offers.
1. Add the proposed position to ["Fleeties"](https://docs.google.com/spreadsheets/d/1OSLn-ZCbGSjPusHPiR5dwQhheH1K8-xqyZdsOe9y7qc/edit#gid=0) as a new row, with a blank start date. Be sure to include job title, manager, and department.
2. Add a job description to the ["Roles."](https://docs.google.com/document/d/1wS5jFfrZtO4xMH-3U_S8pE59gNXOTR3rS1WWD8pkq9E/edit#heading=h.5z24knw25190) Include only "Responsibilities" and "Experience." (You will insert these into the existing job description template.)
3. Create a private "#hiring-xxxxxx-2022" Slack channel (where "xxxxxx" is the job title) and invite the CEO (Mike McNeil).
- Mike McNeil is the DRI for all `#hiring-xxxxx-2022` Slack channels.
4. In that channel, post a message proposing the position:
- At-mention CEO (@mikermcneil).
- Include a link to the job description in "Roles."
- Include a link to the Fleeties document.
5. Mike McNeil will:
- Confirm the "Roles" document has the job description, consisting only of "Responsibilities" and "Experience," and that both look accurate, grammatically correct, and otherwise ready to post in a public job description.
- Confirm the "Fleeties" document has a manager, job title, and department, and that the start date is not entered yet (so we can tell the position is proposed but not planned, yet).
- Using Pave, determine an anticipated salary and equity range, then add that research to "Compensation decisions" as a new heading.
- Share a direct link to the new heading in "Compensation decisions" with the CEO.
6. The CEO will then:
- Determine whether this fits into the budget and equity plan.
- Decide whether Fleet will open this position at this time.
- Set tentative compensation in the budget and equity plan.
- Set a tentative start date in the Fleeties doc to indicate this position is now part of the hiring plan.
- Reply in the `#hiring-xxxxx-2022` Slack channel, at-mentioning the original proposer, to let them know the new position is approved.
After getting CEO approval, create a position in Breezy.
#### Creating a new position
1. A new handbook subpage is created on the "Company" page and a link to the subpage is added to the "Open positions" section on the "Company" page.
2. The job description is copy/pasted in the new subpage.
3. When an applicant has completed an application, there is a Zapier automation that will post to `g-business-operations`.
4. The applicant information is then forwarded to the applicable `#hiring-xxxxx-202x` Slack channel` and the hiring manager is @mentioned.
> If you think this job posting may need to stay temporarily classified (¶¶) and not shared company-wide or publicly yet, for any reason, then stop here and send a Slack DM with your proposal to the CEO instead of modifying "🧑‍🚀 Fleeties" (which is visible company-wide) or submitting a draft pull request to "Open positions" (which is public).
1. **Propose headcount:** Add the proposed position to ["🧑‍🚀 Fleeties"](https://docs.google.com/spreadsheets/d/1OSLn-ZCbGSjPusHPiR5dwQhheH1K8-xqyZdsOe9y7qc/edit#gid=0) in an empty row (but using one of the existing IDs. Unsure? Ask for help.) Be sure to include job title, manager, and department. For now, leave the start date blank.
2. **Propose job description:** Locate one of the existing job descriptions inside the `handbook/company/` folder and duplicate it into a new handbook subpage. Use the same style of filename, but based on the new job title. (This filename will determine the URL where candidates can apply.)
a. Keep the structure of the document identical. Change only the job title, "Responsibilities", and "Experience".
b. In the same pull request, add a link to your new job to the bottom of ["📖 Company#Open positions"](https://fleetdm.com/handbook/company#open-positions) in the handbook.
5. new job description for by duplicating a new Markdown file based on one of the other open job listings (or past listings, from the commit history). Then edit the "Open positions" section of the "Company" handbook page to add a new bullet at the bottom of the existing bullet point list. State the proposed job title, include the appropriate departmental emoji, and then wrap it in a link and point it at the "living" subpage for the new job description. Use the "living" fleetdm.com URL; not the GitHub URL. (This is where the new page _will eventually exist_, once this pull request is merged. For now, if you were to visit this URL, you'd just see a 404 error. So how can you determine this URL? To understand the pattern, visit other job description pages from the [live handbook](https://fleetdm.com/handbook/company#open-positions), and examine their URLs in your browser.)
6. **Get it approved and merged:** When you submit your proposed job description, the CEO will be automatically tagged for review and get a notification. He will consider where this role fits into Fleet's strategy and decide whether Fleet will open this position at this time. He will review the data carefully to try and catch any simple mistakes, then tentatively budget cash and equity compensation and document this compensation research. He will set a tentative start date (which also indicates this position is no longer just "proposed"; it's now part of the hiring plan.) Then the CEO will reply promptly in the `#hiring-xxxxx-YYYY` Slack channel, at-mentioning the original proposer and letting them know their position is approved. (Unless it isn't.)
> #### Steps for Mike
> - Confirm the new row in "Fleeties" has a manager, job title, and department, that it doesn't have any corrupted spreadsheet formulas or formatting, and that the start date is still blank (so that it is clear to everyone that this position has been proposed, but that it is not confirmed and planned, yet).
> - Confirm the job description consists only of changes to "Responsibilities" and "Experience," with an appropriate filename, and that the content looks accurate, is grammatically correct, and is otherwise ready to post in a public job description on fleetdm.com. Then approve and merge the pull request.
> - Ballpark, budget, and document compensation research for the role
> - Scroll to the very bottom of ["¶¶ 💌 Compensation decisions (offer math)"](https://docs.google.com/document/d/1NQ-IjcOTbyFluCWqsFLMfP4SvnopoXDcX0civ-STS5c/edit#heading=h.slomq4whmyas) and add a new heading for the role, pattern-matching off of the names of other nearby role headings.
> - Use [Pave](https://pave.com) to determine anticipated compensation in terms of base salary, variable compensation, and equity, then write those ballpark compensation numbers under the new heading in "Compensation decisions". (Write equity as a percentage. And when ballparking salary, err on the side of the role costing more.)
> - Then create written documentation of your research for future reference. Take a screenshot of the relevant Pave screens and paste those screenshots under the new heading.
> - Update the row in ["¶¶ 🥧 Equity plan"](https://docs.google.com/spreadsheets/d/1_GJlqnWWIQBiZFOoyl9YbTr72bg5qdSSp4O3kuKm1Jc/edit#gid=0) using the benchmarked compensation and share count.
> - Note: Most columns of the equity plan are updated automatically when Fleeties is, based on the unique identifier of each row, like `🧑‍🚀890`. (Advisors have their own flavor of unique IDs, such as `🦉755`.)
> - Enter the salary: If the role has variable compensation, use the role's OTE (on-target earning estimate) as the budgeted salary amount, and leave a note in the "Notes (¶¶)" cell clarifying the role's bonus or commission structure.
> - Enter the equity as a number of shares, watching the percentage that is automatically calculated in the next cell. Keep guessing different numbers of shares until you get the derived percentage looking like what you want to see.
> - Create a private "#hiring-xxxxxx-YYYY" Slack channel (where "xxxxxx" is the job title and YYYY is the current year).
> - Invite the hiring manager. (Mike McNeil is the DRI for all `#hiring-xxxxx-2022` Slack channels, but the hiring manager is also included.)
> - In the channel, post a message at-mentioning the hiring manager to let them know that their proposed position has been reviewed and approved, and now the job description and application form are live on the website. Include a direct link to their live job description on fleetdm.com. (This is the URL where candidates can go to read about the job and apply. For example: `fleetdm.com/handbook/company/product-designer`)
### Receiving job applications
Every job description page ends with a "call to action", including a link that candidates can click to apply for the job. Fleet replies to all candidates within **1 business day** and always provides either a **rejection** or **decisive next steps**; even if the next step is just a promise. For example:
> "We are still working our way through applications and _still_ have not been able to review yours yet. We think we will be able to review and give you an update about your application update by Thursday at the latest. I'll let you know as soon as I have news. I'll assume we're both still in the running if I don't hear from you, so please let me know if anything comes up."
When a candidate clicks applies for a job at Fleet, they are taken to a generic Typeform. When they submit their job application, the Typeform triggers a Zapier automation that will posts the submission to `g-business-operations` in Slack. The candidate's job application answers are then forwarded to the applicable `#hiring-xxxxx-202x` Slack channel and the hiring manager is @mentioned.
### Recruiting
#### Checking legal restrictions on hiring