Iโm a front end dev in London, applied for UX Engineer at Google and just started the interview process. Little bit confused about the role. Job page makes it sound like your standard FEE role but the recruiter mentioned assisting FEEs and implementing prototypes. Didnโt want to ask too much and sound stupid for not fully understanding the role I applied to. Can anyone shed any light? Sounds like I might just be implementing designs in code and handing them off to the real front end devs - if so would I still be treated and compensated like a dev? TIA
It's not a frontend eng. It's close to web dev if your domain is browser. What the recruiter said is true. It's mainly conceptual prototype building and write pre-production code. Perhaps building some internal tools. Even though they do have two lenses, design role, frontend role, If you want to pursue a true fee role in a long run, probably not going to be helpful. Pay is less for sure compared to swe. Sounds hip when they say you can do both. In a perfect world, you might become someone who does not even belong to any side in terms of depth. Trust me. I have a close friend who's doing it at google a d I myself experimented with a similar title at a similar company. Trying to go back to being a frontend eng soon
Thanks mate for this explanation, but I would request you to share more insight on 1. FEE does work on more than browsers? Can you share where else? 2. What's the difference in work for FEE and UXE
1. FEE can focus on many different aspects. just other that being a web specialist. UI component, ci tools/infra, building a feature products...list goes on. 2. It depends on a company but in my experience, simply think of the difference as whether you write a production code or not. The latter includes working with designer conceptually and build prototypes as a proof of concept. You may or may not follow eng code convention then your code quality won't be as polished over time.