Onboarding Schedule

Week 1

The new hire should:

• Run through the general Banno onboarding process.
• Run through the Prism onboarding guide.
• Read the New Mac Setup guide.
• Check out the general onboarding guides, including the glossary.
• Check out the list of the engineering & infrastructure teams and the list of operations & support teams.
• Get VPN access and set up Okta.
• Request access to the Banno Github organization through JHNow as soon as possible, as many tools require Github profile sign-on.
• Maybe: Request access to the JHADigitalCore organization if they need to work on apps hosted there. Check with team to see if this is necessary.
• Log in to Artifactory and then submit a jhNow ticket (under “Cloud Infrastructure” -> “Identity/Access”) to request access to Artifactory. Include the name of a fellow team member to mimic the permissions of.
• Create a Cloud Infrastructure jhNow ticket (choose “Identity/Access”) to get access to the Banno Development Group so kubectl works. Ensure the description specifies the group name and a team member to mimic the permissions of.
• Submit a ticket for ArgoCD access.
• Get a working dev environment on their machine. Cloning and successfully running npx binci test of a repo (e.g. node-consumer-login-proxy) is a good benchmark.
• Setup your editor
• Read the NodeJS teams - How We Work guide

The EM or an existing team member should:

• After they are added to the Github organization, add the new hire’s Github user to Nodejs and one of our teams: Prism, Terminus, Atom.
• If they need to work on the JHADigitalCore organization, add them to the prism or terminus group.
• Add the new hire to the Slack @prism, @terminus, or @atom user group and invite them to our private channel.
• Invite them to the Jira prism, terminus, or atom team.
• Add them to the Google prism, terminus, or atom group. Some teams might have a separate production level google group that the new team member will need added to after an initial period: atom-prod.
• Invite them to Retrium. (See the “Invite your team” section in the left sidebar.)
• Add them to the necessary incident.io team. They can be added to the team without being added to the FF schedule.
• Add them to the necessary launchdarkly team.
• For senior or staff engineers, ask Jessica Kenney to add the new hire to the Symantec VIP manager with Certificate Management access. The new hire will get an email invite; they will have to register a new credential (which can be generated with the Symantec VIP mobile app) when logging in the first time.
• Introduce the team member to the Digital team in Slack (see example).

The EM should:

• Add the new hire to calendar events for our standups, retro, and knowledge dumps.
• Find an existing team member to serve as “ambassador” (see below).

The ambassador should:

• Set up an introductory meeting with the new hire. The goal is to introduce how Banno and NodeJS teams fit into the JHA ecosystem, and point them to this wiki and these onboarding docs.
• Identify some initial work suitable for the new hire. This may include lower priority customer issues, or tech debt, or something where the new hire can team up with another person.
• Help the new hire get set up for work.

Week 2

The new hire should work on the assigned issue.

The ambassador should:

• Provide a quick demonstration of the Banno platform: Online, Mobile, and the backoffice.
• Go over our processes with the new hire, including:
  • Explain our firefighting process.
  • Explain our development conventions.
  • Explain our review / release / deploy process.
• Answer any general questions about JHA/Banno/Prism as needed.

Week 3

The ambassador should answer any remaining questions the new hire has.