> For the complete documentation index, see [llms.txt](https://handbook.redivis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.redivis.com/careers/design/product-designer.md).

# Product designer

Define guidelines and build visual and system level plans for user interactions with the Redivis product. 

## Contributions

You specialize in discovering and meeting user needs. You're fully invested in the way users are interacting with our product and optimize for success for everyone. You bring a focus on intentionality and empathy to projects throughout Redivis that ultimately elevates every users' experience.

## Outputs

* Research reports
* Design plans
* Wireframes
* Prototypes
* Product mocks
* System docs
* Design system component library

## Career progression

| Individual contributor (IC)                                                       | Manager                                                                              | Salary level |
| --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | ------------ |
| [Junior designer](/careers/design.md#junior-designer)                             |                                                                                      | 3            |
| [Designer](/careers/design.md#designer)                                           |                                                                                      | 4            |
| [Senior designer](/careers/design.md#senior-designer)                             |                                                                                      | 5            |
| [Lead designer](/careers/design.md#lead-designer-design-manager)                  | [Design manager](/careers/design.md#lead-designer-design-manager)                    | 6            |
| [Principal designer](/careers/design.md#principal-designer-senior-design-manager) | [Senior design manager](/careers/design.md#principal-designer-senior-design-manager) | 7            |
| [Creative director](/careers/design.md#creative-director-design-director)         | [Design director](/careers/design.md#creative-director-design-director)              | 8            |

#### Leadership and tracks

Everyone being promoted from Senior designer onward will be expected to step into a leadership role depending on what [track](/careers/growth-and-progression.md#tracks) they're on.

## Core design skills favored

All designers are evaluated on a set of [core skills](/careers/design.md#core-skills) which will vary person to person.

* [Interaction design](/careers/design.md#interaction-design)
* [Research](/careers/design.md#research)
* [Prototyping](/careers/design.md#prototyping)
* [Information architecture](/careers/design.md#information-architecture)
* [Strategy](/careers/design.md#strategy)


---

# 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.redivis.com/careers/design/product-designer.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.