My interview experience with Mach Industries was disappointing, particularly given how the company presents itself as an innovative defense technology startup, seemingly trying to position itself in a similar light to Anduril.

The interview was significantly different from what had been communicated beforehand. Rather than focusing on relevant engineering experience, system-level problem-solving, technical accomplishments, or real-world applications, the interview largely consisted of trivial technical definitions and on-the-spot mathematical questions.

While technical fundamentals are certainly important in engineering, the questioning felt more like an academic pop quiz than a meaningful assessment of an experienced engineer’s capabilities.

What stood out most was the attitude of the interviewers. Rather than fostering a collaborative technical discussion, several employees came across as smug, condescending, and more interested in demonstrating their own knowledge than understanding the candidate’s experience.

The atmosphere felt unnecessarily adversarial, almost as though the objective was to catch someone not knowing an answer rather than evaluate their ability to contribute to the organization.

Having worked in the defense industry and experienced the engineering environments of established contractors and newer defense technology companies, I found the contrast particularly noticeable. Mach appears eager to cultivate an image similar to Anduril’s, but my interview experience did not reflect the same level of professionalism or collaborative engineering culture I would expect from an organization with those ambitions.

There is nothing wrong with challenging technical interviews. However, there is a difference between evaluating engineering competency and using technical trivia as an opportunity to establish intellectual superiority.

Advice to Management:

• Ensure interview expectations align with what candidates are told beforehand.
• Train interviewers to assess practical engineering experience, critical thinking, and problem-solving rather than relying predominantly on memorized definitions and rapid calculations.
• Most importantly, encourage humility and professionalism.

A technically knowledgeable engineering team is valuable, but technical knowledge alone does not create a strong engineering culture.