I interviewed with Lyft for a front end SWE role and got no leetcode questions. I ran through a bunch of 45-minute "make-this-thing-in-React" panels, and passed all with flying colors. That's only one example, but the type of questions I find unusually challenging (dynamic programming) -- the only time I was asked those, was at Google.
Google doesn't hire front end software engineers specifically. They hire general-purpose leetcoding machines (e.g, people that can can crank out DP problems), then assign those people to work on front end tasks.
For a data point, when I applied and interviewed for a frontend-focused position at Google ~1 year ago, I had the option of one of my interviews being a front-end specific interview that would focus on FE rather than algorithms.
That interview track contains the DP-type problems. So now, not only do you have to show your DS&A algorithms skills, you need to showcase your front-end skills. If you interview as a backend engineer, you'll get more algorithmic questions, but overall question set will cover less breath and a similar level of depth.
I thought it was common for frontend interviews to not focus as much on CS stuff/things people typically associate with FAANG-style interviews. Facebook does this for example[0]
