I interviewed four times with different Fluxon team members and truly enjoyed the entire process. I especially appreciated how I was consistently kept in the loop and how each interviewer was warm, friendly, and engaging. Take-home design assignments can often be tedious and controversial in product design interviews, so I was grateful that Fluxon didn’t require one. Instead, I was asked to share and discuss some of my work and process in detail. This felt respectful of my time while still giving the hiring team an opportunity to understand my skills and approach; a balance I really valued. Overall, the hiring process was a positive experience where I genuinely felt cared for throughout.

The interview process consisted of four rounds and was significantly more demanding than expected. Candidates should be prepared for a high level of intensity, with a strong focus on theoretical knowledge rather than practical case studies. In some instances, case studies presented on the website appeared to be limited to Dribbble-style visuals, without deeper product context. While I appreciate rigorous evaluation, the overall tone of the interviews felt more adversarial than collaborative. Compared to other processes I’ve been through, this one stood out due to the level of stress and a general sense of mistrust. I can’t speak for all departments, but my interactions with the design team suggested signs of burnout and low morale. There was also a noticeable mismatch between the role description and the interview focus. Initially framed as a visual/UI design position, the later stages heavily emphasized UX strategy, analytics, and detailed knowledge of qualitative vs. quantitative research, metrics, and performance evaluation. Candidates should be prepared for an in-depth “exam-like” experience across all areas of UX. Another point to consider is work culture. It was mentioned that meetings are often scheduled according to client availability, even late in the evening (e.g., 10–11 PM), which may indicate limited boundaries between work and personal time. The final interview with the CEO focused on high-level product thinking (e.g., proposing improvements to Google products with a full roadmap) but did not include discussion of my background or prior experience, which felt unbalanced. Despite spending approximately four hours in total on the process, the outcome was communicated through a generic, scripted rejection. Overall feedback: The process could benefit from better alignment between the role expectations and evaluation criteria, more structured and relevant case discussions, and a more candidate-friendly experience. Key question: If the salary range is not flexible, it would be helpful to align expectations earlier in the process. Additionally, the purpose of multiple intensive rounds is unclear if the final decision is primarily based on the last interview.