GitLab Solutions Architect Demo

You are requested to deliver a high-level end-to-end demo of the GitLab platform. This is a 60-minute session. The core demo should be roughly 30 minutes, but you should expect potential interruptions throughout the demo and/or Q&A that may extend the demo as long as an hour in duration. The demo audience will not expect you to be a GitLab expert, but rather will be looking at your presentation style, clarity of the GitLab value proposition, audience engagement, etc.

Please engage the panel attendees like you would engage any prospect or customer - speak to the value of the platform, tell a story, engage the customer, solve problems, etc.

"Customer" Account Information

The primary application developed by a 500 developer firm is a web-based app using Java Maven.

Note: The demo you deliver doesn't have to be a Java project - please use a language you feel most comfortable to demonstrate in, and relate it back to the customer's use-case where appropriate.

The current tools stack includes the following:

"We use Jira for agile planning and sprint setup, then the development team works in GitHub to develop the features on a branch. Each branch runs pipelines to test the code using our internal testing framework. We are considering moving toward microservices but currently utilize a monolithic application.“

“When a feature is merged into master, Jenkins kicks off a build, tags it, and deploys it to our EC2 instance on AWS. We do have some problems managing all our disparate Jenkins servers - some need to be rebooted daily, and many times the pipelines run longer than we wish. We are currently considering using EKS to help us save costs on app scaling as well as to simplify our deployments."

Demo Attendees

Demo Setup

Note: You do not have to make use of this pre-configured group if you would rather set your own up. But this will then require you to enter credit card details in order to access the shared runners (no charge made).

Demo Guidelines





By default, PostgreSQL databases are deployed alongside applications when using Auto DevOps. This functionality has been disabled by at the group level by setting the POSTGRES_ENABLED CI/CD variable to false. If this is required for your project, please re-enable it at the project level by setting POSTGRES_ENABLED to true.

Code Quality

If you intend to demo the Code Quality functionality as part of Auto DevOps, you will find that it doesn't execute by default. This is because the CODE_QUALITY_DISABLED CI/CD variable has been set to 1 at the group level (for speed). If you want to enable it for your project specifically, please set the CODE_QUALITY_DISABLED CI/CD variable to 0.


Please feel free to email the hiring manager with any questions, issues or concerns as you prepare for the demo. You will find the hiring manager’s email on the calendar invite for the demo interview.

Don’t have a account? Register today!