# 30 days of engagement

The first engagement runs as a formal trial period — four weeks of paid work, up to 160 hours. It is structured and carefully monitored by Lemon.io’s Client & Developer Experience team.

**Day 1–2**

A developer is introduced to the client via email, given access to repositories, tools, and documentation, and assigned a clear first task. The client is expected to provide full context — the faster you become an individual contributor, the better.

**Day 3**

The Client & Developer Experience team conducts check-ins for both sides — a safety net to catch access issues, unclear expectations, or early friction before they become problems.

**End of Week 1**

A developer submits their first timesheet. Both sides complete a quick survey. Any “off” signals are caught and addressed immediately.

**Weeks 2–3**

You are expected to be delivering real value. The Client & Developer Experience team monitors progress through feedback forms.

**Week 4**

Both sides complete a closing survey. If the engagement continues, it rolls forward seamlessly. If not, the transition is handled cleanly with no outstanding issues.

The trial is not free — a developer are paid your full hourly rate from day one. **The payments are made monthly.**&#x20;

<figure><img src="/files/4qC3HB9hAODaoA5zB70i" alt=""><figcaption><p>Active project, developer's profile on Lemon.io.</p></figcaption></figure>

<figure><img src="/files/QNDcEWDKyKuE8JDRAWQQ" alt=""><figcaption><p>Active project description, developer's profile on Lemon.io.</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.lemon.io/for-developers/30-days-of-engagement.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
