Code and architecture diligence - your team will provide access for key engineering contacts at GitLab to code repositories, products, and development/test environments. The early technical diligence conducted before the term sheet is signed will be an abbreviated form of the diligence noted below. We will:
Perform a code review
Analyze the technology stack and how it fits in the GitLab tech stack. Evaluate efforts and approaches for integration including milestones.
Conduct a license review analyzing the licenses of the repositories owned by the target as well as of any open source packages which are in use to see which ones are acceptable per company policy
Conduct a security review. Analyze what security vulnerabilities are known to exist in the product(s) and the process for determining this (static/dynamic security scanning, independent penetration testing, etc.).
Provide the results of any third-party security testing results.
Analyze any commercial software/services that are required for the product(s) to operate.
Evaluate development practices and standards
Analyze test suite coverage, framework, and automation
Employee evaluations - each engineer will undergo two rounds of interviews comprised of:
Technical assessment - a live coding session, solving a technical exercise or review a merge request with live followup session.
Evaluate potential team structure post-acquisition
In case of acquisitions with over 10 engineers the employee evaluation stage will happen in phased approach for 5 employees at a time.
In case where there aren't sufficient open recs matching the acquired team, the acquisition team can put a request to the executive team to approve new recs required.
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license