They might look at your open source application but only about 30 seconds at the readme only, so include screenshots and maybe they might look at that. They are probably just looking at the number of stars, forks, and any other number not related to the software.
In the case of web development or JavaScript almost every time they will throw a shotgun blast of newb syntax questions at you. Sometimes the questions are general and other times the interviewer is fishing for something of comfort to a personal code style. If they ask for any opinion or open-ended question respond with something critical or unpopular to see how the interviewer reacts. Failure to do so will endanger your ability to do anything creative or challenging.
As a bored and thoroughly under impressed candidate I really wished companies, who claim to be looking for senior developers, asked for the impossible to see what kind of answers they get. By impossible I really mean standard interview questions everywhere else. Examples:
* How do you achieve complete page load in less than a second?
* How do you achieve accessibility AA criteria without ARIA?
* How do you create custom components without a framework?
* Describe a means of broadcasting information to users in real time without polling a server.
* How do you persist/restore state without compromising page load time?
* How would you achieve real time status updates to/from users without negatively impacting usability or accessibility?
I understand when a big company uses LeetCode problems to scale out the process (e.g. new hires in Bangalore and new hire in SF go through the same process). In these companies, usually candidate don't interview for a specific team, they just get an interview to join FANG, then they get matched to a team at the end of the process. However, for startups, they should know what they need, and what kind of skills/person that they are looking for. I wish this trend change (hiring professional interviewees, instead of hiring professional developers).
The caveat? Well for one my first few jobs have been extremely low paying and that’s not hyperbole at all. Even now I don’t make very good money, relatively speaking, for the field. I’ve worked at very small companies, government agencies and large corporations, exclusively non tech. The work is boring and droll, a lot of sitting around and waiting for bureaucratic processes. But never any leetcode questions.
I’m sure there are other people with better experiences who have not gone through the leetcode process as well.
It's worth pointing out that there are some questions on LeetCode that are absolutely fair game in the interview process. Questions along the lines of can you implement the logic of a rate limiter, can you implement some authorization logic, how would you deduplicate some data in a system, given some request headers can you implement X logic, etc. are all questions that can be closely tied to some LeetCode questions but are also regular day-to-day work. However these are questions where you don't have to memorize "tricks" to solve them in the amount of time you're given.
That being said FAANG companies are known to ask the typical "LeetCode" type of questions, so if you're applying to those companies expect such interview questions.
no leetcode.
I liked explaining work I did more than trivia type stuff.
Got the job.
Granted this was a very non silicon valley, midwestern small company so i really don't think they were interested in a whiteboard / trivia type interview.
However, many consulting companies, esp smaller ones, will look at project work and may ask you to do some coding, but won't care about your algorithm skills.