SOLUTIONS ARCHITECTS Onboarding Bootcamp
Regular Onboarding Duties https://about.gitlab.com/handbook/general-onboarding/
Week 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:
Getting to know GitLab Support
Complete Zendesk Agent training (allow 40 minutes for completion)
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
Familiarize yourself with our Lead Qualification Process
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
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