



Brighter / Cigna
Bridging the gap between design and engineering.
Brighter was a digital healthcare startup building tools to help people find, evaluate, schedule, and review dental providers.
I joined the team as a Frontend Developer, initially focusing on HTML and CSS.
Over several years, my role evolved into a hybrid of development and design — helping UI/UX teams convey major needs and decisions with engineers.
After Brighter was acquired by Cigna, my work expanded to an overhaul of the company’s search experience.
During my time at Cigna, I played a leading role in navigating responsive layout and accessibility between multiple teams.
ROLE
Design Engineering · Front-End Development · UX Collaboration · Responsive Design · Accessibility
TEAM
Designers · Engineers · Product · QA · Cigna API Team
TIMELINE
2016–2020
TOOLS
Angular · JavaScript · HTML · CSS · SCSS · Git · Lighthouse · BrowserStack · WCAG · Section 508
MY CHALLENGE:
How do you keep multiple teams in sync when a project grows in complexity and has multiple needs?


I Problem
Healthcare information is complicated, but implementation and design shouldn’t be.
Working with healthcare data — whether a robust dental network like Brighter, or millions of providers through Cigna — means teams need to stay in lock step across projects.
However, each team thinks about problems differently:
Product may want to gather the most pertinent information from users.
Design may focus on readability and reducing information overload for users.
Engineers may want to standardize and componentize across a large application.
And healthcare, much like government, is compliance driven; applications must work across devices, browsers, and users with a variety of accessibility needs.
When I started at Brighter, a Santa Monica-based startup, I quickly found myself working across disciplines and teams.
Even as I contributed to a complex code base with engineers, my specialty became about helping various perspectives meet somewhere in the middle.



II Process
01. Learn the limitations of the medium
One of my first responsibilities at Brighter was email.
Our product relied heavily on confirmations, reminders, and followups to communicate scheduling and reviews.
Unlike many applications, we needed to support older browsers and email clients like Microsoft Outlook.
Older clients introduced many limitations that simply didn't exist on other parts of the web.

I spearheaded research on email compatibility, implementing TOOLS like EMAIL ON ACID to establish a rigorous approach for testing and optimization.

When designs depended on something an older client couldn't support, I explained the limitation to our design team before it reached engineering.
Sometimes that meant our designers had to make compromises.
As I was pushing them toward using simpler, single-column layouts, they had to abandon more complex content to support older clients.
The result was a standardized set of templates that the design team could reproduce quickly.
Not only were the emails minimal and easier to read; they were compatible across many different technologies.
02. Become the bridge
As our product grew, so did the needs of design and engineering.
Increasingly, wireframes would address tablet and mobile layouts.
At the same time, engineers had begun to rely on components across our enterprise-sized solution.
How did we compromise?
A desktop design might look perfect on a large screen but become extremely complicated and difficult to translate into a mobile layout.
Similarly, a repeatable component inside other components could wreak havoc on responsive patterns without proper planning.
A button positioned at the top of a desktop layout, positioned differently on mobile one, might cause multiple breakages and delay entire sprints or deployments.
As the unofficial design-engineering liaison, I began pushing teams toward simpler, more predictable architecture.
03. TEACH THE SYSTEM
As the engineering organization grew, I found that my impact wasn't limited to the code I wrote on a day-to-day basis.
I had begun to help other engineers understand why we made certain frontend decisions.
Code reviews became an opportunity to teach better HTML and CSS practices.
Design meetings became an opportunity to discuss responsive behavior before implementation.
My background in both visual design and frontend development allowed me to speak two languages.
IV Final Thoughts
Good frontend engineering is more than translating a design into code.
At Brighter and Cigna, I learned that the hardest frontend problems aren't necessarily the ones with the most complicated code.
A design may be visually compelling but difficult to componentize.
A component may work perfectly on desktop but fall apart on mobile.
A page may look correct but make no sense to a screen reader.
A technically valid implementation may create unnecessary complexity for the engineers who have to maintain it.
My role was often to see those tensions before they became problems.
At the end of the process, I had:
Helped bridge design and engineering across a large Angular application.
Established responsive layout patterns that reduced unnecessary CSS complexity.
Helped engineers adopt more semantic, accessible HTML.
Key Takeaways
Design with implementation in mind.
Simplicity scales.
Accessibility starts with structure.
The best design-engineering work happens between disciplines.
METRICS
Millions of users on the Angular apps
$20M+ in VC funding raised before Cigna acquired the company
Hundreds of pages and reusable component libraries shipped
4 years from startup through acquisition, 2016–2020
© 2026 BEN NICHOLSON

