Skip to content

On-boarding Process

  1. A candidate (intern or full-time candidate) submits a request

  2. The ResearchMeister gets the notification from the submission Gsheet and creates an Asana task under Not started with:

  3. Name (nickname) email
  4. E.g, Yuanxuan ****** <yuanxuan@*******.edu>
  5. Put the form links, the GitHub account, the LinkedIn / CV link, etc. in the Asana description (all the info that we typically need to access quickly)
  6. Google form: ?
  7. CV / LinkedIn: ?
  8. GitHub handle: ?
  9. Email: ?
  10. Telegram handle: ?
  11. Devops candidate: Yes / no
  12. Intern vs Full-time candidate: ?
  13. Quick review if the person has the skills we are looking for

  14. Assign to a shepherd

    • If interns -> Samarth/Sonaal
    • If full-time candidate -> shepherd
    • If not clear ask GP

  15. The shepherd reviews the CV to get a sense if they are decent or not

  16. It posts a quick summary of pros and cons
  17. We want to increase the quality of the collaborators, so if there is a red flag we can decide to not on-board
  18. If you are uncertain, ask more people to take a look

  19. The goal is to avoid on-boarding collaborators that will likely disappoint us

  20. If the candidate is a no go, GP sends an email of rejection

  21. The on-boarding shepherd is in charge of updating the Asana task with every interesting event

  22. We start the on-boarding process as per

  23. Update the Contributor List

  24. Copy the information from Contributor Info response sheet to the Contributor List as it is a master sheet for all the collaborators
  25. Ping GP on the Asana task for that collaborator for invitation to the repo

  26. Add Contributor email as Commenter to the KaizenFlow - Contributors gdrive

  27. When the collaborator is ready to be on-boarded, file an issue like "On-board "

  28. The content of the issue will be the following checklist (note that GitHub needs full paths to point to the documentation from an issue) ```
    • [ ] Acknowledge the pledge to put effort and time in the project here
    • [ ] Fork, star, watch the KaizenFlow repo so that GitHub promotes our repo (we gotta spread the work)
    • [ ] Read and execute set up development environment
    • [ ] Read and start internalizing KaizenFlow Python coding style guide
    • [ ] Read about your first code review
    • [ ] Peruse the map of all the documentation
    • [ ] Learn about our org process
    • [ ] Get assigned a warm-up issue
    • If you are graduating soon and you would like to get a full-time job in one of the companies in the KaizenFlow ecosystem reach out to GP at gp@kaizen-tech.io ```

  29. Admins need to keep track on the progress being made by the collaborator.

  30. We score candidates every two weeks

  31. Public gsheet
  32. Private gsheet

Off-boarding process

A list of things to do to off-board an intern / collaborator

  1. [ ] Remove from GitHub
  2. [ ] Remove from contributors@
  3. [ ] Remove from the TG channel
  4. [ ] Remove Gdocs access:
  5. KaizenFlow
  6. Process
  7. Crypto-tech