> 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/company/how-we-work.md). # How we work We are [process-driven](/company/values.md#build-processes) in our work because it allows us to be better empowered in what we do and to contribute most effectively. When you join Redivis, we'll be excited to share with you all of our internal documentation. However, we believe it's important to be able to understand at a high level how we work together as you envision a career at Redivis. ## Feedback Feedback is essential in order for us all to improve in our careers and to best empathize with and support each other. You can expect bi-weekly feedback sessions with your direct manager, as well as semi-annual performance reviews, where you will both be able to gather and give detailed, thoughtful feedback to/from your peers and manager targeted around improving ourselves and our processes. ## Career growth We strive for everyone at Redivis to grow in their career, and support [equally-compensated pathways](/careers/growth-and-progression.md#tracks) as either an individual contributor or manager. Importantly, we believe that transparency is *critical* in supporting career growth. You can read more about our approach to career progressions, performance reviews, and much more in the [careers section](/careers/growth-and-progression.md). To make sure that we are always thinking about and supporting each other's growth goals, we practice semi-annual growth reviews, where you will work with your manager to take a deep dive into your growth goals and define your areas of expertise and opportunities for further improvement. ## Company transparency When you join Redivis, you should expect substantial transparency — we openly share information with our employees about our financial status, growth prospects, and general company goals. If you ever want to take a look, it's all there — and we encourage you to do so! It's also important for us to have concrete dates on the calendar to prioritize a defined, open, and frank discussion about what's happened in the past and what the future holds for Redivis. You can expect a quarterly meeting where we'll present this information in full and open it up to a company-wide discussion. ## Company structure We are a small company, and we all wear multiple hats. However, we find it incredibly useful to think about our work in terms of specific departments. This allows us to be explicit about which of our hats we are currently wearing, and who is responsible for any given task. #### **Operations** * People * Finance * Hiring * Legal * Software and infrastructure #### Business * Sales * Partnerships * Account management * Marketing * Metrics #### Community * Communications * Conferences, meetups, and working groups * Documentation * User support * Customer onboarding #### **Design** * User research * Product design * Communications design #### **Engineering** * Frontend * Backend * Security * DevOps #### **Product** * Project management * QA --- # 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: ``` GET https://handbook.redivis.com/company/how-we-work.md?ask= ``` 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.