> 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/jobs/research-advocate-and-support-engineer.md). # Research advocate and support engineer {% hint style="info" %} Please read the hiring process below, and then apply on [our Jobs page](https://redivis.homerun.co/technical-evangelist-and-support-engineer/en)! {% endhint %} ## Overview Applying for jobs is exhausting. While we care deeply about developing a team of talented, empathetic, and curious people, we want to do everything we can to make this process as transparent and respectful of your time as possible. Outlined below are the steps in our interview process. Our commitment to you is that we'll always be transparent as to where you are, the next steps, and our timeline. Everyone's time is limited, and in general we will bias towards reducing the number of candidates moving through each step. We'll let you know as soon as we've decided not to move forward with your application, though please know how appreciative we are of you taking the time, and that we genuinely wish you success in your job search. ## Step 1: Reach out! You can find information about working at Redivis and our open positions on [our jobs page](https://jobs.redivis.com). Please press "Apply" on the job listing to submit your application. If you don't see a position for you, you're always welcome to send us an email at . ## Step 2: Initial call We'll have a short introductory video call (20–30 minutes) with Sean or Erin. This is a relaxed, conversational chat, and a chance for us to get to know each other. We'll ask about your background and interests, and you're encouraged to ask us anything you'd like to know about the company or the role. ## Step 3: Technical interview You'll meet with our CEO, Ian, for a roughly 60-minute interview. This will include a technical component, where we'll go over a number of questions and scenarios related to research data processes. This is designed to assess both your technical proficiency and how you communicate about data, both of which are equally important in this role. And of course, there will be ample time for you to ask any additional questions you may have about Redivis and this role. ## Step 4: (Offsite) Onsite This is an extended session (\~2 hours) where you'll get to meet each member of our team. We'll also work through a few hands-on tasks together, likely including: developing a piece of support content, working through a technical support request, and presenting a concept to both technical and general audiences. We're interested in how you engage with different perspectives and how you approach a wide range of problems. ## Step 5: Connect with references We'd like to connect with one or two people you've worked closely with. We're specifically interested in hearing about how you operate when things are ambiguous, and how quickly you move from idea to execution. --- # 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/jobs/research-advocate-and-support-engineer.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.