• Can’t speak for everywhere, but in the US, if your first questions are about salary, they’re going to be left wondering if you’re even qualified for the job and if money is all you care about. Even if it is (which is fine most of the time), that’s not really the impression you should give if your goal is to be hired.

    Asking about salary later on is usually a much better idea. You know whether you actually are interested in working there, the interviewer knows if they are interested in you, and wanting money it isn’t the first impression you give.

    As for Python - leetcode style interviews are common, but almost always worthless. The only real value the company gets from something like that is to check that you actually can write code. They’re pointless beyond that, and a company doing leetcode interviews should be a red flag.

    • The problem is that so many companies are ridiculously low-balling their salaries. The US is having real economic problems for the average worker.

      If I’m interviewing for a job, I know what minimum salary I’m willing to work for. I just want to know what the range is and whether or not it can sustain my lifestyle. If the pay isn’t enough to cover my mortgage, an interview is a waste of time for both of us.

      This situation is easily avoidable by simply posting the range with the rest of the details.

      It’s like buying a car, I know what I can afford. When I go to a dealership I might be deciding between the base model or the luxury edition. But I’m not gonna waste my time, or the salesman’s time by looking at something way outside my price range. I’m gonna know what range to expect before I ever show up on the lot.