This is a template. Create your own checklist in your personal documents by going to New > Start from Template

Software Engineer Onboarding Task List

First Day

  • Attend welcome meeting.

  • Start working through the standard company onboarding tasks.

  • In Slack, add “GeekBot” to your Apps if it’s not already there. It’ll probe you to, fill out your first DailyBot status report, which appears in #_daily_ping.

  • Join daily stand-up.

  • Join Cadence OneFive Github account (admin to add you here)

  • Open Local Development Environment FAQ and keep it handy as you work through setup. This is a living document: please consult your coworkers if you get stuck, and update the doc.

  • Set up the Momentum project and add your first building in the local webapp (see README.md).

  • If you will be working on building science calculations, set up the Calc Service project and get familiar with nbdev (see README.md).

  • If you will be working on data, set up the Data Processing project and run your first DAG (see README.md).

First Week

  • Get access to our tools, and ping Chuck or François to register you for these. Always use your @c15.io email:

  • Fly.io for deployment

  • Sentry.io for production performance and error monitoring

  • Doppler for secrets management

  • Envoyer.io for deployment. Create an account using your @c15.io email account, but don’t subscribe to a plan. Ask a fellow coder to invite you to each of the relevant servers, then go to https://envoyer.io/user/profile#/invitations and accept them all.

  • Create an account on Forge (for backup and deployment configuration), setup 2FA, and ask to be added to the c15 “circle”

  • AWS Account. Your software onboarding mentor should:

  • Create a new account with your @c15.io email, share the info via dashlane

  • Log in with the temporary password, update to a new password (save it in dashlane), and set up 2FA (User Account → Security Credentials).

  • Receive a demo of the application. You can also watch recordings here (ask if there’s anything more recent).

  • Complete setup of the development environment for repositories you will be contributing to.

  • Start working on your first development ticket and create your first PR.

First Month

  • Participate in routine meetings.

  • Contribute to the code.

  • Participate in Testing Tuesdays.

  • Contribute code reviews to team members’ pull requests.