A couple years ago, while searching for a new job, I was struggling with my job title as a Front-End Developer. I remember feeling that their wasn't a specific title for the type of front-end development that I was interested in.
It wasn't until prominent voices in the web community started discussing the importance of style-guides, accessibility, performance, CSS maintenance, and eventually design systems, theme specs, and component library API design that I knew there were other people like me. People who, at the end of the day, are still Front-End Developers/Engineers but enjoy working on the "front of the front-end".
Some of those early online discussions led to great articles that dissected the current state of front-end development and proposed that, as an industry, we should be writing more descriptive job postings and maybe even coming up with better job titles that are more descriptive of the job at hand instead of always falling back on the umbrella "Front-End Developer" title. A few of those articles and discussions can be found here, here, or here. The first article, The Great Divide emphasized the importance of recognizing the "divide" in front-end development and respecting and valuing both sides of it since both sides have much to offer.
It was after reading through discussions and articles similar to the links above that I realized I wanted to focus on this side of the front-end, but it wasn't until a couple years later that I started to notice people had a name for this type of front-end position and the title for this type of a Front-End Developer is called a UX Engineer.
A UX Engineer falls somewhere in between a Front-End Engineer and a UX Designer. They're still Front-End Developers, but they might be a bit more design savvy and/or they understand the importance of continuous collaboration with Designers. I'd imagine a small and productive product team looking something like this:
- UX Designer
- This role is focused on product design and research using tools like Figma, Adobe Creative Suite, Sketch, or Framer X to display and organize different views and components.
- UX Engineer
- This role is responsible for working with designers to create and prototype accessible and performant UI components. This role bridges the gap between Designers and Engineers while ensuring a delightful user and developer experience.
- Front-End Engineer
- Front-End Engineers are focused on what I call the "back of the front-end", meaning they're responsible for API calls, application architecture, state management, and other business logic-y demands on the client-side.
- Back-End Engineer
- This role can have multiple sub roles to fill demands, but to make things simple a Back-End Engineer is responsible for DevOps, managing and securing databases, handling continuous integration and more.
As noted above, the crucial responsibility for a UX Engineer is to build the bridge between Engineers and Designers. The tool they primarily use to bridge that gap is the design system, which should be composed of a library of tested and documented components, design principles, design tokens, and public (visible to your organization) documentation.
This isn't an exhaustive list but below are some of the tools and technologies a UX Engineer might use on a day-to-day basis in 2020.
- React / Vue (component-based JS framework)
- styled-components / emotion
- Figma / Sketch
- theme-ui / styled-system
- Storybook (playground / documentation generator)
- Tailwind CSS
- Write accessible and semantic HTML.
- Write maintainable and browser-friendly CSS.
- Create and maintain a theme spec that ensures consistent UI across all components.
- Create a consistent API across all components to ensure ease-of-use for consumers of design system.
- Manage component state to effectively build UX across all states of an interactive UI.
- Publish and release new versions of design system that don't cause breaking changes.
- Write visible documentation for design system for other engineers to reference and contribute to.
- Implement visual, unit, and automated accessibility tests.
- Work with designers to make sure theme spec covers all brand guidelines, including animations, colors, and typography.
- Work with designers to ensure feasibility of new UX/UI
- Work with engineers and consumers of design system to remove any pain points of design system while ensuring a quality developer experience.
- Be a vocal proponent of accessibility, performance, and inclusiveness.
- Encourage others to contribute to the design system in the form of conversations, feedback, documentation, or code.
At the end of the day, a UX Engineer is responsible for crafting a user-friendly experience for both:
- Developers - in the form of clean API design, tested and working components, and visible, well-maintained documentation to ensure rapid development from engineers using the system.
- Users - in the form of usable, accessible, and performant interfaces that can easily be used from a variety of users with various devices and internet connections. These experiences shouldn't be burdensome to the user, they should empower the user to use the webapp or website how they prefer while also allowing unique branding to be in place to allow the organization or company to set themselves apart from competition.
This post might not cover all the skills and expertise that a UX Engineer might have, but I believe it to be a solid example of what a UX Engineer might look like in 2020. Let me know what you think via email, I'm curious what other self-identified UX Engineers are working on because one day when I grow up I'm gonna be a UX Engineer! 😂