All-in-all, a rather unprofessional experience that was disappointing as the role combined my love of engineering and aviation. The initial contact and invitation for request to interview for a Test Engineer position came out-of-the blue after submitting my resume six months before the phone screening. Communication was a bit slow after their email, but I wrote it off as how HR can become busy during crunch times. Ten minutes before the SDET screening, the person who was handling my interview had an unexpected event develop. They gave the task to someone who's tone and verbal-demeanor made it clear that they obviously didn't want to talk with me. Judging by the questions they asked and the way they received my answers, the person did not seem to have a complete grasp of the software development process or what tools are utilized in an application's life-cycle. The questions were pretty reductive, see below, and I could almost hear the persons eye's rolling across the phone as I explained exciting projects and technical challenges overcome. During this conversation, I brought up that I had Developer Evangelist responsibilities at a previous position, and that I would appreciate being considered for the role that was posted after I applied. This was the first time the person's tone-of-voice changed to something positive, and they were engaged in the conversation. I followed up with a resume that was more specific to the role. A week later, I was told they are changing the requirements for the Test position, and that I didn't have enough experience for the Dev E position. This is despite achieving hundreds of millions of dollars of investment for companies that I directly prototyped applications and hardware. Plus, the public-speaking opportunities; where I've had the joy presenting. They apparently want to find a unicorn in a thriving economy.