This is our approach to [[tech competence assessment]]. The idea is to create a comfortable environment, where those wishing to [[join us]] can showcase the expertise they consider most relevant for the given vacancy, in a way they find most suitable. --- ## WHAT to showcase? It can be **anything that that demonstrates your relevant expertise** to the team. Our preferred method is for you to [[solve an assignment]] and to present your solution. Having evaluated hundreds of these solutions, we can promise an engaging discussion and valuable feedback. We understand that for some candidates the necessary time investment (~4 hours for the mandatory tasks) could be a strong inconvenience. We thought of two alternatives: [[share a project|share your own project]] or [[elaborate a topic|elaborate on a relevant topic]]. The key point is to prepare and showcase something that is representative enough of your expertise and relevant to the given vacancy. --- ## HOW to showcase? Once you feel read, we will schedule a **1.5 hour session for you to present your work and to discuss it** with the relevant team members. ### 1. Before the session #### 1.1 Prepare Take your time, think of the most optimal way to express your craftsmanship. Take a closer look at the vacancy, make sure that you (1) understand what expertise we are looking for and (2) have a plan for revealing that expertise via your presentation and discussion with the team. Don't hesitate to contact us if unsure about anything in the process. #### 1.2 Share Once ready to schedule a session with the team, email [email protected] with whatever you'd like the participants to review prior to your presentation. Help us prepare and make the most out of the session. You are welcome to mention significant references (sources of information or people) that you used during the preparation, what you learned in the process, what challenges you faced, etc. ### 2. During the session #### 2.1 Present (≈45 min) Share your screen and present what you have prepared. We are interested in the clarity, readability, and reusability of your code as much as in your decision-making process. We suggest the following structure for presenting software projects: - **15 min - intro & project overview**, including a high-level description, demo, and use cases - **15 min - architecture overview**, where you elaborate on decisions and articulate principles - **15 min - code review**, presenting the most interesting parts of the codebase, reflecting on code style and development approaches. #### 2.2 Discuss (≈45 min) Follow-up conversation about your work with the team. This step will naturally emerge from and may intertwine with the Presentation step. This will also be the opportunity to address your questions to the team. --- ## Aaand... WHY like this? 🙄 We felt that typical Q&A-type technical interviews and coding tests/quizzes do not provide an opportunity to properly express one's expertise and approaches. Nor do they provide sufficient input to make a good hiring decision, as such a format is not a realistic reflection of the work environment. We believe in cultivating a flexible and supportive work environment, embracing diverse individual styles and working methods instead of imposing a uniform approach across the team. The goal of our approach to [[tech competence assessment]] is to mirror such an environment. Instead of putting candidates under unnecessary stress, we want to offer them an opportunity to express their craftsmanship, ingenuity, accountability, and respect towards their temporary (or future) teammates. While shifting more responsibility onto those wishing to [[join us]], this approach aligns perfectly with our aim to attract individuals who are eager to take on additional responsibility in exchange for greater freedom.