Fix more relative URLs that throw 404 (part 2)

| Eclectic mix of company-wide [in-person gatherings]({{< ref "./in-person" >}}) (vs. congregating at a standard office) |            Yes             |                                         No |

| Hearing about watercooler chitchat and perpetual cubical drop-ins from your in-office colleagues |             No             |                                        Yes |

***Learn more through [Life at GitLab]({{< ref "culture#life-at-gitlab" >}}) and our [Out of the Office]({{< ref "./out-of-the-office" >}}) report. If this page resonates with you, visit GitLab's [Career Opportunities](/jobs/).***

***Learn more through [Life at GitLab]({{< ref "culture#life-at-gitlab" >}}) and our [Out of the Office]({{< ref "./out-of-the-office" >}}) report. If this page resonates with you, visit GitLab's [Career Opportunities](https://about.gitlab.com/jobs/).***

## Assessing the remote workplace experience

1. Acknowledge intern contributions in team meetings, issues, company calls, 1-1 meetings.

1. Send a gift or a swag bag to commemorate their contributions.

Don't forget to gather information they are willing to share such as their email address, LinkedIn profile, or handles for other social channels so you can stay in touch. Who knows...maybe a [position at GitLab](/jobs) will come available that you can hire them for!

Don't forget to gather information they are willing to share such as their email address, LinkedIn profile, or handles for other social channels so you can stay in touch. Who knows...maybe a [position at GitLab](https://about.gitlab.com/jobs) will come available that you can hire them for!

## Contribute your lessons

1. Foster community and mentorship with like time zones. E.g. If a manager gains a new direct report with a sizable time zone gap, ask others in the organization — even if they are not in the same department — who are more aligned with the time zone to include this person in their social activities.

1. Lean on documentation. Place importance on using [low-context communication]({{< ref "./effective-communication" >}}) in 1-1 documents, GitLab issues/merge requests, etc.

1. Consider using tools like [Yac](https://yac.com) and [Loom](https://www.loom.com) to convey thoughts and feedback with video and audio if the written word feels too impersonal. [Managers]({{< ref "being-a-great-remote-manager" >}}) should flex to the preferred medium and style of their direct report, and encourage open conversation to iterate on this as the relationship develops.

1. Meet in-person. When possible (e.g. at onsite [GitLab Contribute](/events/gitlab-contribute) gatherings), prioritize spending [in-person time]({{< ref "./in-person" >}}) with those who have little overlap in virtual working hours. These opportunities may arise at company retreats, events, and through serendipity in personal travel.

1. Meet in-person. When possible (e.g. at onsite [GitLab Contribute](https://about.gitlab.com/events/gitlab-contribute) gatherings), prioritize spending [in-person time]({{< ref "./in-person" >}}) with those who have little overlap in virtual working hours. These opportunities may arise at company retreats, events, and through serendipity in personal travel.

1. Celebrate [differences]({{< ref "values#quirkiness" >}}). For example, working with someone experiencing summer while you experience winter is remarkable. Lifestyle differences are an opportunity to learn and expand one's worldview, and this includes time zone differences.

You can also learn from the experiences of GitLab team members collected in [this survey from late 2021](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12740).

  - CRO: Decrease age of non-web direct deals by 10% ACHIEVED

    - Sales Ops: [New sales stages and exit criteria. Launch and Train](https://gitlab.com/gitlab-com/sales/issues/120)

    - Customer Success: Solution Architects managing PoC's for new business opps within strategic/large accounts. 50%

    - PMM: 2 ROI calculators => New [competitive ROI calculator](/calculator/roi/) published.

    - PMM: 3 case studies => 3 case studies started. New [/customers](/customers/) page launched.

    - PMM: 2 ROI calculators => New [competitive ROI calculator](https://about.gitlab.com/calculator/roi/) published.

    - PMM: 3 case studies => 3 case studies started. New [/customers](https://about.gitlab.com/customers/) page launched.

  - CRO: Keep sales efficient. [Sales efficiency ratio](/handbook/finance/#definitions) > 1.8 (IACV / sales spend) ACHIEVED

  - CMO: Keep marketing efficient. [Marketing efficiency ratio](/handbook/finance/#definitions) > 3.4 (IACV / marketing spend) => 3.43

- CEO: Understand and improve existing account growth. 200% YoY

1. Seed then nurture: [plant seeds and nurture the product to build out depth](#seed-then-nurture).

1. Speed: ship every change in the next release to maximize responsiveness and learning.

1. Life balance: we want people to stay with us for a long time, so it is important to [take time off](/handbook/paid-time-off/) and work on life balance; being [all-remote](/handbook/company/culture/#all-remote-work) is a large part of the solution.

1. Open Source Stewardship: be a good [steward of GitLab](/handbook/company/stewardship/) and [collaborate with the wider community](/community/contribute/) to [improve the product together](/handbook/engineering/development/performance-indicators/#mr-rate).

1. Open Source Stewardship: be a good [steward of GitLab](/handbook/company/stewardship/) and [collaborate with the wider community](https://about.gitlab.com/community/contribute/) to [improve the product together](/handbook/engineering/development/performance-indicators/#mr-rate).

### Seed then nurture

### Flywheel with two turbos

GitLab is a [complete DevOps platform](https://about.gitlab.com/solutions/devops-platform/), delivered as a [single application](/handbook/product/single-application/), with [contributions from the wider community](/community/contribute/).

GitLab is a [complete DevOps platform](https://about.gitlab.com/solutions/devops-platform/), delivered as a [single application](/handbook/product/single-application/), with [contributions from the wider community](https://about.gitlab.com/community/contribute/).

Compared to other DevOps platforms, GitLab leverages one or two unique turbos that boost the company:

1. [Advantages of a single application](/handbook/product/single-application/), leading to more [Stages per Organization](/handbook/product/performance-indicators/#stages-per-organization-spo)

1. [Open Source stewardship](/handbook/company/stewardship/), leading to [Wider community contributions](/community/contribute/)

1. [Open Source stewardship](/handbook/company/stewardship/), leading to [Wider community contributions](https://about.gitlab.com/community/contribute/)

The advantage of a single application manifests itself if people start using more stages of the application.

In the graph below this is visualized with [Stages per Organization (SpO), knowing that an organization using an extra stage triples conversion](https://about.gitlab.com/direction/#product-strategy).