# Tech leads

<figure><img src="https://476013847-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCdGkCxKDvQdgeyQPlLua%2Fuploads%2FnxE6R9ULmMPIIbYV9Fib%2FScreenshot%202024-05-31%20at%2012.21.01.png?alt=media&#x26;token=32272b20-de6c-4bc6-9be5-7bb936002dcd" alt="" width="329"><figcaption></figcaption></figure>

While a [manager is responsible for their  team's career management as we already learnt](https://management.lunr.tech/how-we-make-decisions/leadership/managers), a **Tech Lead** as the name implies **is the leader of a department when it comes to operations**. This position is assigned to a subject matter expert that masters the department's processes and tools. It's under **their responsibility to manage the department's standard operating procedures** and also to **ensure cross-department processes are well-documented and understood on an organizational level.**

His **responsabilities is technology.** His activities are as follows:

* to provide expert opinion and direction regarding processes
* to transfers LUNR knowledge and department's knowledge to others in our tech-session.<br>

Tech leads' **focus is on processes improvement.** To do so they:

* resource allocation
* identifie and addresses process inefficiency
* establishe SOPs, Best Practices, and Playbooks
* provide the necessary tools
* maintain the documentation in the department's Confluence space
* ensure the department’s Knowledge Hub is correctly documented and up-to-date
* delegate tasks in Process Improvement project in Jira
* do task management and tracking
* do fire fighting.

{% hint style="info" %} <mark style="color:blue;">**Who should ideally become a tech lead?**</mark> \
It can be an [Individual Contributor](https://management.lunr.tech/how-we-ensure-peoples-growth/performance/paths/individual-contributors-path) Level 3 and UP, or a manager Level 1 or Level 2, Step 1 or 2. A manager at Level 2 Step 3 and above should have already grown another member of their team to be a Tech Lead, and be able to move on from being a Tech Lead themselves. You will learn more about the steps in the next chapter.
{% endhint %}


---

# 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://management.lunr.tech/how-we-make-decisions/leadership/tech-leads.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.