Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 8 Packages Projects Releases Wiki Activity

Handbook: Inbound candidate job applications (#36737)

Browse Source 
What do you think @zayhanlon and @ireedy?  Up to Zay
This commit is contained in:
Mike McNeil
2025-12-05 15:29:04 -06:00
committed by GitHub
parent 0231c2832c
commit 9e6ebef4e0
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
handbook/company/leadership.md
+3 -3
View File
@@ -70,7 +70,7 @@ Changes to departmental pages can be merged when the change results in a page co
<blockquote purpose="large-quote">
Biggest learning is that we federated carte blanche edit permissions a bit too early back in 2021, and it’s resulted in the need for a lot of cleanup as different people have had their hands in the content prior to introducing a framework for organizing that content.
For reference, Sid at Gitlab didn’t delegate ownership over pages away from a single individual (him) until they were close to 100 employees, whereas at Fleet we did it in the 15 employee stage, and are dealing with the consequences.
For reference, Sid at Gitlab didn’t delegate ownership over pages away from a single individual (him) until they were close to 100 employees, whereas at Fleet we did it in the 15 employee stage, and were dealing with the consequences.
It meant that until late 2023, about 1/3 of the Fleet handbook was completely wrong, duplicated, or out of date. (We’re now close to 100% accurate.)
The audience for the “Communications” page is every Fleetie.
@@ -78,7 +78,7 @@ The audience for the “Communications” page is every Fleetie.
The audience for the “Leadership” page is every manager.
The audience for individual department pages are the people working with and within that department (in that order, with “Contact us” and other generally useful information and intake channels listed first).
This pass through the handbook has also eliminated several pages in favor of getting more onto single pages. This is because there is still a lot of duplication, and it’s easier to deal with when everything is on a single page.
This pass through the handbook has also eliminated several pages in favor of getting more onto single pages. This is because there was still a lot of duplication, and it’s easier to deal with when everything is on a single page.
If you have any questions or feedback, please make a pull request.
@@ -173,7 +173,7 @@ Fleet uses [certain email templates](https://docs.google.com/document/d/1VAMWIH8
### Communicating with applicants
At Fleet, we use the contact form and email to communicate with future team members. Community members will often inquire about positions that aren't currently being hired for. The DRI for receiving applications is Fleet's VP of Customer Success, whose team uses a set of template responses and updates Fleet's HRIS with new applicants. Fleet's SLA for responding to applicants is 1 business day, though this doesn't necessarily mean that the hiring manager has bandwidth to take further action after that initial reply. In that initial reply, candidates are encouraged to apply for future positions if they don't hear back further within a few days.
At Fleet, we use the contact form and email to communicate with future team members. Community members will often inquire about positions that aren't currently being hired for. The DRI for receiving applications is Fleet's Head of People, whose team uses a set of template responses and updates Fleet's HRIS with new applicants. Fleet's SLA for responding to applicants is 1 business day, though this doesn't necessarily mean that the hiring manager has bandwidth to take further action after that initial reply. In that initial reply, candidates are encouraged to apply for future positions if they don't hear back further within a few days.
> **Recommending someone for an [open position](https://fleetdm.com/handbook/company#open-positions) at Fleet?**
>