> For the complete documentation index, see [llms.txt](https://handbook.sixpivot.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.sixpivot.com.au/careers-and-development/recruitment-process.md). # Recruitment process We're grateful (and excited) you're thinking about working with us! Here's a high-level idea of what our recruitment process might look like for you. ### Informational/screening chat: This is a casual conversation to get to know each other better. We'll answer any and all questions about SixPivot as well as see if there is alignment for relevant experience, role expectation and salary. ### Technical component Technical interview finding your technical and consulting limits. ### Final interview This is where you meet our GM or CEO who will want to learn about you as well as share our vision and goals. ### Offer Congratulations you've made it 🎉 We think you're amazing! The nice thing about job offers from SixPivot is once you have a job offer from us, you will always have one. We regularly have people join us when they're ready e.g., after travelling, after their stocks have vested, after baby or purchasing a house. We'll decide together on a rough timeline when works for you 😃 ### Feedback We think it's important to close the loop. Our team take a good amount of time putting together individual feedback. You will be provided feedback directly from the developers who interview you. If unsuccessful at any stage of the interview process, you can reapply again in 12 months. And if our community mentoring program is running we may also invite you to participate. --- # 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.sixpivot.com.au/careers-and-development/recruitment-process.md?ask=&goal= ``` `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.