Front-end developer
A front-end developer builds what runs in the browser. That includes the markup, the styles, and the scripts that make an interface respond. That’s been part of every job I’ve had.
I’ve spent more than twenty years designing and building interfaces with product teams, from insurance platforms to consumer products. I design the interface and build it in front-end code.
I live in Connecticut. My roots are in Louisiana.
My most useful work has combined design and engineering. I work out what a workflow needs. Then I test that answer in working software.
I’ve done that work on insurance portals, recipe sites, and child care software, and most recently on an enterprise design system used by roughly 3,500 engineers and designers.
In each job I turned designs into something engineers could build from. I gave them reusable components. I stayed on the work when real data didn’t fit the design.
Read the full résuméA product design engineer does a little of every role listed here.
A front-end developer builds what runs in the browser. That includes the markup, the styles, and the scripts that make an interface respond. That’s been part of every job I’ve had.
A UI engineer turns visual design into the components and code of an interface, often as part of a design system. That’s my current job, on a system roughly 3,500 engineers and designers use.
A UX engineer turns interaction design into working prototypes and front-end code. At Logatot that was voice input and the flows for fixing what the app misheard.
A UI designer decides an interface’s layout, type, color, and the components it is built from. For VMSpark’s admin app that meant a design system built from scratch.
A UX designer studies how people use a product and shapes its flows, structure, and behavior around their needs. At IVFCRYO interviews with the team led to one shared record for everyone involved in a shipment.
I give component APIs, defaults, documentation, and automation the same care as type and spacing. I judge them by whether teams choose them over building their own version.
Keyboard order, labels, contrast, and recoverable errors shape the design from the first sketch. When that behavior lives in shared components, every team that uses them gets it by default. I test that behavior and say where it still falls short, including in the Limitations section of each case study.
Before building I name the result that would show a change worked. After release I check it. At America’s Test Kitchen I settled design questions with Optimizely A/B tests. At Logatot I reworked the forms where Hotjar and analytics showed people getting stuck.
Empty lists, failed requests, long labels, and first-run screens are part of the experience. I resolve those details with design and engineering in working interfaces early in the project.
I grew up on Cajun food and music. My grandmother’s chicken and sausage gumbo remains the standard.
My wife and I met at our first duty station in Hohenfels, Germany. We lived in the nearby village of Seubersdorf and had our first child there.
I’ve played for more than thirty years, from college clubs across the Southeast to Bourbon Street and Frenchmen Street in New Orleans. These days I play locally.
We travel with our kids whenever we can. Iceland is still our favorite. Closer to home we look for less-visited places.
Source: https://joshuabriley.com/about/