The recruiter got my information from Dice, and it started from there.

Most engagements in interviews are gauging the person's interest in applying, since it doesn't make any sense to push through something when the person isn't looking or the job isn't aligned with the candidate's career goals.

I was given a HackerRank test and successfully submitted it. There were 2 questions: the first one working fine, and the second having failed on 1-2 test cases.

After this test:

• I was passed on to another recruiter to proceed with the process.
• Had a phone conversation again.
• Phone interview with a panel.
• QL flew me in for an all-expense-paid business trip to Detroit, MI.
• Face-to-face interview with the team.
• Had a city tour. I kinda liked the feeling of being in a state of the resurgence of Detroit (plus the fact it is cheaper to stay there than my current location).

Despite being enthusiastic to work, 4 days later, I got the result that I was being passed on.

I always ask for interview feedback because I usually want to see where I possibly fell short in the interview, at the least on the technical side of things. However, it seems that it is standard for US recruiters not to disclose the reason why one isn't selected. Though I respect their decision not to provide one.

I actually liked it that they asked me more about my projects, what my roles were, and some design and implementation questions rather than bookish questions. Although the last question, while seemingly a nice-to-know, the interviewer expected me to know this by heart: "What happens when you type a URL in the browser and press enter?"