> For the complete documentation index, see [llms.txt](https://management.lunr.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://management.lunr.tech/how-we-ensure-peoples-growth/compensation/ic-frameworks/ux-ui.md).

# UX/UI

The UX/UI Designers (abbreviation for User Experience/User Interface) are responsible, as the name implies, for ensuring that the design of the application meets all users' needs, ensuring their satisfaction by interacting with our company, platforms, or partner's brands.

UX/UI Designers are mainly responsible for developing user navigation maps, usability tests, creation, development, and implementation of innovative and attractive solutions, prototyping, user and process flow, and linking the communicative interaction to the Design concepts. Once the tests have been carried out, along with our partner's feedback, they also optimize the created solutions, performing the documentation of all processes. To ensure growth in this framework, the UX/UI Designers are required to make enhancement studies, create navigability standards for performance optimization focusing on security, create engagement, and guarantee customer satisfaction.

## Progression

In order to progress in our development path and Level Up or Step Up, our designers must:

* Meet the criteria of the Level & Step Chart for the [Individual Contributors Path](#user-content-fn-1)[^1]
* Meet the [KAI ](/how-we-build-processes-and-a-great-product/knowledge-management/knowledge-accountability-index.md)grade of the framework related to each level
* Demonstrate proficiency in LUNR knowledge

## Salary Grid

All mentioned salary ranges represent the monthly income in Bulgarian Lev after taxes and deductions.

| UX/UI Design                | Step  |       |       |       |
| --------------------------- | ----- | ----- | ----- | ----- |
| Level                       |       |       |       |       |
| Individual Contributor Path | 1     | 2     | 3     | 4     |
| 1                           | 3.600 | 3.750 | 3.800 | 3.950 |
| 2                           | 4.600 | 4.750 | 4.800 | 4.950 |
| 3                           | 5.600 | 5.750 | 5.800 | 5.950 |
| 4                           | 6.600 | 6.750 | 6.800 | 6.950 |
| 5                           | 7.600 | 7.750 | 7.800 | 7.950 |
| 6                           | 8.600 | 8.750 | 8.800 | 8.950 |

### [KAI ](/how-we-build-processes-and-a-great-product/knowledge-management/knowledge-accountability-index.md)of the framework

Extensive knowledge<br>

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

[^1]:


---

# 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://management.lunr.tech/how-we-ensure-peoples-growth/compensation/ic-frameworks/ux-ui.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.