# DevEx

Typo helps you stay ahead of developer well-being with early signals derived from work patterns and AI-driven pulse check-ins. These insights allow you to proactively address engagement challenges and build a healthier, more productive team culture.

[👉 **Learn more about configuring DevEx**](/typo-help-docs/configurations/devex.md)

### Pulse Check-in

Typo triggers **AI-driven weekly check-ins** for developers. These short, conversational prompts are designed to gauge team sentiment and experience.

* Insights are published on the dashboard as soon as **two or more responses** are received
* Automatic reminders are sent to boost participation

{% hint style="success" %}
PS: These chats are 100% anonymous.
{% endhint %}

<div align="left"><figure><img src="https://lh3.googleusercontent.com/bmhEJdsQzI3GHe0BBUtZZVksMxh7ocOizfE67jYehnrMrfEdyNY_s2ZaKUgU0nRlnwQ4prqKhIKXAAdJmnWEuOLgmUOMNDZUp-5mtWTLAxZSQJXKjEECz08ogiYrROo7xSJ10Vt67O57-0z03vdryGY" alt="" width="563"><figcaption></figcaption></figure></div>

### **DevEx Insights**

Insights are published as soon as we receive two or more survey responses and are continuously updated as more responses come in. Automated reminders are sent to users who haven't completed the survey to help boost response rates.

<figure><img src="/files/yKgBwvIa5FIBGPo6RQcL" alt=""><figcaption></figcaption></figure>

You can see all the details for [DevEx Metrics here.](/typo-help-docs/engineering-metrics/devex-metrics.md)

View our [Developer Experience framework here](/typo-help-docs/engineering-metrics/devex-metrics/devexframework.md)

### Heatmap

Use the Heatmap to dive deeper into DevEx data by demographic breakdowns:

* **Designation**
* **Location**
* **Team**
* **Tenure**

This allows you to understand experience patterns across different groups and tailor your interventions accordingly.

<div align="left"><figure><img src="/files/atQ0thk8FTVzlwwXFol3" alt=""><figcaption></figcaption></figure></div>

### Burnout Alerts

Typo automatically monitors developer activity to detect signs of burnout early. Alerts are generated when work patterns show persistent intensity compared to team averages or customized thresholds.

**Signals Monitored:**

* Commits
* Pull Requests
* Code Reviews
* Comments
* Tasks
* Merges

When a developer crosses a burnout threshold:

* You’ll receive a **burnout alert** directly in your communication tool
* You can filter them from the contributors section
* It's recommended to review the **work log** to understand the workload and take action

<figure><img src="/files/6P1SKimcDDOgwKqbi801" alt=""><figcaption></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://typo.gitbook.io/typo-help-docs/platform/devex.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.