> For the complete documentation index, see [llms.txt](https://handbook.opencoreventures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.opencoreventures.com/company-ops/people-ops/onboarding.md).

# Employee onboarding

This page covers onboarding once a worker type has been chosen. To decide which Deel structure and agreements apply to a given hire (US employee, non-US employee, US contractor, non-US contractor), start with [worker types](/company-ops/people-ops/recruiting.md#hiring-process).

**US employees (EOR).** Once the offer letter is signed, create the contract and onboard the new hire into your company's EOR account in Deel. New employees complete the EOR onboarding process and sign the employment agreement before their start date. Most hires take a minimum of one week to onboard — confirm timing with the EOR before committing to a start date. For step-by-step setup, see the [Deel Founder Guide](https://docs.google.com/document/d/1P_EhGRiZHJNFW0E7-6Xt4jLa-SQEe4TGYq6S2Pd-vK8/edit?tab=t.0#heading=h.lq6pm997maqd).

**Non-US employees and all contractors (COR).** These are engaged as Contractors of Record in Deel. See the [Deel Founder Guide](https://docs.google.com/document/d/1P_EhGRiZHJNFW0E7-6Xt4jLa-SQEe4TGYq6S2Pd-vK8/edit?tab=t.0#heading=h.ckcbh09v4ebx) for COR onboarding steps, and the section below for the additional documents contractors must sign.

Background checks are run by the EOR after all documents are uploaded, except for new hires in Germany, France, Israel, and Ireland, who go through a separate background check provider.

## Onboarding contractors

Both US and non-US contractors are engaged as Contractors of Record (COR / non-invoicing) through Deel. In addition to the COR agreement:

* **US contractors** sign the standard consulting agreement (Drive > ToolKit > Legal Forms), which includes an IP clause.
* **Non-US contractors** must be provided a separate PIIA (Proprietary Information and Inventions Assignment) to sign and store in the contractor's HR folder. The PIIA is sent via the company ATS used for hiring. See instructions [here](https://docs.google.com/document/d/1Kgfd32rs54QsF7bC0juMJP4QXC-K8vMV-lml79npf0s/edit?tab=t.0#heading=h.eznapmgfmg50).

The standalone PIIA provides critical protections beyond the standard language in EOR agreements and is an important element of diligence for future investors.

## Employee equipment purchases

All work should be performed on a company-issued laptop or computer equipment. Companies should provide necessary equipment to their team members. Companies should establish their own equipment purchase policies and price range guidelines including considerations for job functions.&#x20;

Generally, employees or their managers can purchase the equipment on their corporate credit card or follow the company’s typical expense reimbursement processes. Contractors should provide their own equipment.

### Laptop recommendations

Apple Macbooks are the standard laptop for most employees.

1. [Macbook 14-inch, 512 GB](https://www.apple.com/shop/buy-mac/macbook-pro/14-inch-space-gray-apple-m2-pro-with-10-core-cpu-and-16-core-gpu-512gb) for non-engineering roles
2. [Macbook 16-inch, 1TB](https://www.apple.com/shop/buy-mac/macbook-pro/16-inch-space-gray-apple-m2-pro-with-12-core-cpu-and-19-core-gpu-1tb) for engineering roles

There are some cases that Macbooks might not be the right fit for the company or new hire. In these cases, please purchase the company preferred laptop from the brand that best fits the needs of the company.

### Purchasing laptops for employees

When possible, purchase equipment for new hires before their start date to ensure they are fully equipped on day one. The equipment can be expensed prior to their start date.

1. Confirm the delivery address with the new hire .
2. Use the company expense account credit card to make the purchase on the [respective Apple website](https://www.apple.com/choose-country-region/) of the delivery country.

### Employee reimbursement for laptop purchase

Where there are limitations in local ability to purchase laptops, the new hire should purchase the laptop themselves and be reimbursed through the company’s payroll.

**Limitations include:**

1. Foreign credit cards are not accepted by the website
2. Delivery not available

## Leasing equipment to contractors&#x20;

{% hint style="info" %}
Use the provided [Template Agreement](https://docs.google.com/document/d/1TlpEqfZeyfFkYAvYFDquaX0DPtsp67Qd4OFHG71yj40/edit) for leasing equipment to contractors.&#x20;
{% endhint %}

Best practice provides that contractors should use their own equipment for work. OCV companies are not obligated to provision equipment to contractors. However, the company may, at the discretion of the CTO / CEO, lease a contractor the necessary equipment required to effectively perform their work for $1 USD. This includes laptops and other essential hardware.&#x20;

In these situations, it may be necessary to advance funds to the contractors to purchase the equipment in their country. The company retains ownership of the equipment when the contractor is no longer working with the company.

## Tracking laptops as fixed assets

Laptop purchases are to be tracked by the hiring manager who can modify the [fixed asset tracker](https://docs.google.com/spreadsheets/d/1HiZkM6JUPhUjYp_VXlpNMiWpZv7uZYnQE_02k59SqtI/edit?gid=0#gid=0) template and save to the company’s drive for ongoing company equipment tracking.

## Systems onboarding

You will onboard new hires to their workspace email, password manager system, internal messaging system (e.g. Slack, GChat, Discord), and any additional systems (e.g. GitHub, Jira, AWS) specific to the company and/or team that the new hiring is joining.&#x20;

Only company founders (CEO & CTO) should be added to the `#ocv-company` Slack channel. A separate channel should be created for any additional team members to facilitate communication with their founder(s).

## Remote work resources

\[Company] is an all-remote company with employees not localized to a single office.For employees new to all-remote work, the following guides may be helpful:

* <https://about.gitlab.com/company/culture/all-remote/guide/>
* <https://about.gitlab.com/company/culture/all-remote/getting-started/>
* <https://about.gitlab.com/company/culture/all-remote/onboarding/#the-importance-of-onboarding>
* <https://about.gitlab.com/handbook/leadership/building-trust/>

## Performance Evaluation

### Engineering <a href="#block-a01dea8c5c234b1eadb24a71cf3f0d3f" id="block-a01dea8c5c234b1eadb24a71cf3f0d3f"></a>

#### Ramp-up time <a href="#block-3bc03c63ed3a46e4a0771a826a649369" id="block-3bc03c63ed3a46e4a0771a826a649369"></a>

1. 3-month ramp-up time if unfamiliar with the product.
2. Expect an additional 3 months if unfamiliar with the language and/or framework.

#### Performance Indicators <a href="#block-9d421839add34120a2f59ab9b7768a25" id="block-9d421839add34120a2f59ab9b7768a25"></a>

There’s no single ideal metric for measuring engineering performance but measuring merge request, or pull request, (MR/PR) rate is the best metric to start with.

**MR Rate**

[MR Rate](https://about.gitlab.com/handbook/engineering/development/performance-indicators/#mr-rate) measures impact by tracking how many changes an engineer is able to merge into the production code base. Start by setting a baseline of 20 MRs per month per engineer for early-stage companies. Evaluate all engineers against the baseline metric and avoid comparing engineers to each other. Productive engineers will meet the baseline, unproductive engineers will not.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://handbook.opencoreventures.com/company-ops/people-ops/onboarding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
