SOLUTIONS ARCHITECTS 30-45 Day Onboarding
Regular Onboarding Duties
Day 1 1Password
Day 2 People Ops Information
[ ] New team member: provide scan of photo ID to People Ops (used for verification, such as I9 verification, and business travel purposes)
[ ] New team member: Access BambooHR, set a secure password and fill out any missing details of your profile; specifically your address, phone number(s), banking information, ethnicity and emergency contact information. Make sure to add the country code to phone numbers (i.e. all numbers should start with +).
[ ] Read the Team Handbook (https://about.gitlab.com/handbook/)
[ ] Read the security best practices (https://about.gitlab.com/handbook/security/), and please ask questions to make sure it is all clear to you.**
[ ] Enable 2FA on your GitLab email account (this should have been an option to do when you first received the invitation to the account).
[ ] If you authenticated your GitLab.com account with Google, GitHub, etc. you should either disconnect them or make sure they use two-factor authentication.
[ ] Enable two-factor authentication on your GitLab.com account.
[ ] Make sure your notifications for GitLab.com aren't sent to a personal email. Send them to your @gitlab.com email.
[ ] Once you are registered on 1Password, post a comment below to ask the manager to add you to the 1Password groups required for your role .
[ ] Set up Calendly and add your Calendly link to your Slack profile.
Take a look at the "Reference Customers" Google doc to familiarize yourself with which customer information should be kept confidential within the company. You can find it by logging into your Google Drive account and searching for "Reference Customers".
Other onboarding tasks (Beamy, schedule coffee break calls, add yourself to the team page, etc.)
Week 1-2 Technical Onboarding
Download Git https://docs.gitlab.com/ce/gitlab-basics/start-using-git.html Stage 1: Become familiar with git and GitLab basics
Cover the Beginner and Intermediate sections (and a few Advanced) in the GitLab University (https://university.gitlab.com/): Under the topic of Git
user training, just do a quick read over the file names so you start remembering where to find them.
Perform each of the following Installation Methods (https://about.gitlab.com/installation/) on your preferred test environment you chose above:
[ ] Starting and stopping services (https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/maintenance/README.md#starting-and-stopping)
[ ] Who's who in Product (https://about.gitlab.com/handbook/product/)
[ ] Study the Sales Handbook page (https://about.gitlab.com/handbook/sales/)
[ ] Familiarize yourself with our Lead Qualification Process (https://about.gitlab.com/handbook/marketing/lead-generation/content/#leadQual)
[ ] Idea to Production Demo (https://about.gitlab.com/handbook/product/i2p-demo/)
In the Sales Folder, familiarize yourself with: Our Sales Agenda (https://docs.google.com/document/d/1l1ecVjKAJY67Zk28CYFiepHAFzvMNu9yDUYVSQmlTmU/edit) Competition (https://about.gitlab.com/comparison/)
Understanding the Competition (Competition (https://about.gitlab.com/comparison/))
Migrations from other Version Control Systems
Integrating with GitLab
Ways to Integrate
If you want to integrate with GitLab there are three possible paths you can take:
[ ] Utilizing webhooks - If you want to reflect information from GitLab or initiate an action based on a specific activity that occurred on GitLab you can utilize the existing infrastructure of our webhooks. To read about setting up webhooks on GitLab visit this page.
[ ] API integration - If you're seeking a richer integration with GitLab, the next best option is to utilize our ever expanding API. The API contains pretty much anything you'll need, however if there's an API call that is missing we'd be happy to explore it and develop it.
[ ] Project Services - Project services give you the option to build your product into GitLab itself. This is the most advanced and complex method of integration but is by far the richest. It requires you to add your integration to GitLab's code base as a standard contribution. You can see the list of project services available, and look into this example. If you're thinking of creating a project service, the steps to follow are similar to any contribution to the GitLab codebase.
[ ] Authentication via LDAP/OAuth (https://docs.gitlab.com/ee/integration/oauth_provider.html)
Solutions Architect Pre sales activities
Solutions Architect Post sales activities
[ ] Health Checks (https://docs.google.com/document/d/1aHA3W2FsHUApnz2XVtJoyhpcGYy6bgOHoRi4ArXnF0o/edit)
Demo Scenarios You will be required to demo to team all demo scenarios specific to customer/prospect requirements in mock style showing business value (https://docs.google.com/document/d/1kSVUNM4u6KI8M9FxoyiUbHEHAHIi34iiY25NhMxLucc/edit)
[ ] Sales role play (demo scenarios)
[ ] Comparison of Gitlab editions (key differentiators and business drivers)
[ ] Ecosystem and how Gitlab interacts/compete with other tools
[ ] Presentation on Idea to Production
[ ] Interactive demo paired with another SA