Mozilla Software Engineering interview questions

The first round was a chat with a technical recruiter. The second was with a manager asking for STAR examples of behaviours. There was then a one hour take-home exercise submitted online. The final round was a set of interviews totalling two hours on technical thinking, role relationships and a review of the take-home. All of these except the recruiter chat were rigidly structured, based around questioning without further exploration or conversation. This was the full process, which took a few weeks. Communication was clear and consistent - I was not ghosted. While I was engaged in it, I felt that the process was positive in comparison to other large tech companies - no leetcode, no hostile questioning, no heavy demands on your time. However, it was lightweight and I was left wondering whether they really learnt enough about me or my skills to make a good hiring decision (especially an offer) on an important role. I didn't learn very much about the company either. I found it interesting that I was never asked anything about so many important topics: leadership, culture, DEI, people development, senior/staff-level behaviours and methods of operating. I'm sure the assessment bar is set higher, but the questions seemed to reflect a junior/mid-level interview. The discussed compensation was fairly good so I don't really understand what they're doing here - no doubt they have their own priorities, but it seems like a fairly big missed opportunity. Within a few days, I was informed that feedback was very positive but they had chosen another candidate. However, the role remains advertised, so this seems less than transparent. Having invested time in this process, I hoped to receive candid, meaningful feedback but I have not been able to obtain any. These details aside, I did really like what I saw of Mozilla as an organisation, but personally it was a mixed experience and I doubt I would consider applying again in future.