Ask HN: What are interviews like in non-software engineering professions?

16 points by sage76 ↗ HN
Currently going through the hackerrank/algo DS process.

What is it like for other fields, especially other engineering fields?

7 comments

[ 0.20 ms ] story [ 24.9 ms ] thread
I am a chemical engineer currently working in a consulting niche (air emissions control and regional air quality management). My interviews have very consistently been designed to test my writing and public speaking skills, which are admittedly crucial in my job, rather than specific engineering knowledge. At this point, my resume contains reasonably strong evidence that I possess such knowledge, but that wasn't the case when I was starting out and the interviews weren't really any different. The closest things to technical questions I can remember being asked are of the form: "Imagine a piece of equipment you are responsible for isn't working. What are some steps you would take to identify and solve the problem?"

I have also occasionally interviewed for non-SWE positions at tech companies (usually data scientist or regulatory compliance positions, both of which are closely related to my current field), and I have found the interviews to be similarly light on technical material, but with much less emphasis on speaking and writing skills.

Not having been through any SWE interviews myself, that's about as much as I can say in comparison. My loose impression is that SWE interviews are relatively heavy on logic puzzles and mini coding problems, but that's all I know. I am happy to answer more specific questions about my experience, of course.

Let's do a thought experiment. If Terry posts random words that speak, and he does this all day, and you are a doctor, what do you think? You just ignore it because you have no idea and assume must be nothing.

In fact, it is God talks and obviously Terry will tell you to go to hell, you nigger monkey.

what_part_of_God_do_you_not_understand jobs on_the_otherhand this_might_end_badly I_just_might yuck Hicc_up ohh_thank_you Terry Pope completely don't_push_it didn't_I_say_that I_got_your_back Give_me_praise hang_in_there a_likely_story a_flag_on_that_play dude_such_a_scoffer fancy You_know Bam but_of_course heads_I_win_tails_you_lose basically quit IMHO maybe_I_didn't_make_it_clear couldnt_possibly news_to_me I'm_God_who_the_hell_are_you endeared

I've often wondered if non-SWP interviews involve homework... I hate this aspect of interviewing for positions.
Less stupid technical questions, because there are much less cheaters and you can trust the given educational background.

I worked as architect, mech. engineer and various other engineering sectors. There are some technical questions of course but nothing like whiteboarding binary search or tree traversal.

Reading at the comments, it tells me how easy, fast and cheap it would be for a machine to crack a software job interview with TODAY's technology. It tells me software dev jobs are the first inline when AI will take over.
Nah, the standard software engineering interviews don't represent the day-to-day reality of a software engineer. That's why they're so frustrating and impractical. So maybe you can build some deep learning bot that can pass an interview, but it won't know how to gather requirements or deal with vague and contradictory requests. We're far away from AI figuring out that what people want and what they need are often very different things.