> 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/communication-designer.md).

# Communication designer

Define guidelines for and execute on visual and written communications across Redivis.

## Contributions

You specialize in getting the point across clearly and beautifully. You’re a systems thinker; you love complex questions and using your visual skills to create clear and engaging stories. You bring a clarity and polish to projects happening throughout Redivis, upping everyone's ability to communicate effectively.

## Outputs

* Brand materials
* Homepage mocks
* Graphics
* Handouts
* Slide decks
* Marketing campaign assets
* External forms
* UX product writing
* Visual user interfaces

## 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.

* [Visual design](/careers/design.md#visual-design)
* [Information architecture](/careers/design.md#information-architecture)
* [Writing](/careers/design.md#writing)
* [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/communication-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.