6 ms·
> Rapidly translating UIs into code is a core skill for UX engineers Maybe I'm confusing the terms, but in our company UX engineers main job is to "figure out"
by deepsun 4y ago
> Rapidly translating UIs into code is a core skill for UX engineers
Maybe I'm confusing the terms, but in our company UX engineers main job is to "figure out" the user flow. It's kinda UI but with mostly boxes (colors, fonts, animations will be added by designers/coders later).
It's closer to product management than programming actually.
- seanmcdirmid 4y agoAre they confusing titles UX designers with UX (software) engineers? I mean, I guess, then its just a matter of everyone calling the role something different. My wife is a UXD, but she has never been called an engineer before.
- pelagic_sky 4y agoFAANGs have UX Engineers whos main goal is to typically prototype ideas. The code they write is not always submitted to source. So a UXD works with a UXE to make ideas happen quickly to vet them out.
- tristanb 4y agoInteresting, do those roles pay well? I’ve never heard of a role that would fit me at a FAANG and didn’t think it existed but that’s exactly what I do.
- deepsun 4y agoAs SWE I'd pay for UX the most of the team. If they did a good job, then coding it is simple. Like 50% of typical SWE work are to figure out the UX.
- seanmcdirmid 4y agoI was a UX prototyper at Microsoft myself, that’s how I met my wife who was working as a UX designer in the same studio. We didn’t have a name for it, my official title was just SWE. I haven’t heard of UXE being a real title at the current FAANG I work for, but I no longer work in a design studio.
- pelagic_sky 4y agoPerhaps you are. Replace Engineer with developer and you have some one who is basically a Front-end Dev. But the scale here is, are you front of the front? Or back of the front? Or all of the front. I think with UX Engineers you are all of the front. Which makes you a weapon.
- hot_gril 4y agoIdk, those two terms are as different to me as URL vs URI. Searching it will yield a long explanation about the differences, but IRL people will use them interchangeably.
- 411111111111111 4y agoIt might seem that way to you, as a url is a subset of uri. I've never actually been in a company that has UX engineers though. It's usually UX or UX designers which work with figma or similar tools and delegate the coding to non-specific software/frontend engineers
- pcthrowaway 4y agoI think it's not a strict subset, there are URIs that aren't URLs (like ISBN numbers), but there are also URLs that aren't exactly URIs, like http://example-blog.com/latest http://example-blog.com/latest But in practice, sure, the 2 are pretty much used interchangeably edit: Perhaps I'm wrong, all resources I can find classify all URLs as a type of URI.
- 411111111111111 4y agoMaybe my understanding of URIs is flawed then, but from your example it looks like an URI for blog articles sorted by publishing date. List<type> was a valid resource type as far as I remember.
- sneak 4y agoPeople do this a lot, but those of us who actually do the work instead of sit and talk in meetings about the work know that there is a huge difference between writing React components (UI) and designing flows in Figma (UX). It's just outsiders who say UI/UX as if they are the same thing.
- Retric 4y agoYet I’ve seen people use the opposite definitions professionally. IMO it’s not the kind of thing that’s worth trying to get people to change.