Skip to main content
Overexposed traffic lights in a city at night

@timmossholder,

Internet Brands

Duration: March 2018 - August 2019

Role: Frontend Developer (performing Senior-level duties)

The Context

I joined the Health vertical expecting to learn from experienced React developers. One month in, the senior frontend engineer left, and I became the de facto technical lead for React across the team, despite being mid-level on paper.

The team included 4 junior frontend developers, 6 senior backend engineers, and 2 PMs. None of the remaining frontend engineers knew React. I had production experience from my ForceShield contract, but I'd never led a team or architected shared infrastructure at scale.

The Challenge

React components were being duplicated across applications with inconsistent implementations. Each app reinvented the wheel, buttons, inputs, and modals, all slightly different. There was no shared design language, and onboarding new developers meant explaining the same patterns over and over.

Meanwhile, the business needed features shipped fast, and I was now responsible for both delivery and team development.

The Solution

React Component Library

I built a centralized UI component library to unify patterns across the vertical:

  • Dumb components first, stateless, reusable primitives (Button, Input, Select, Modal, etc.)
  • Smart wrappers, stateful versions when needed for specific use cases
  • Full documentation, every component documented with usage examples
  • Contribution workflow, established patterns so others could add components
  • Training program, taught 7 developers how to use and contribute to the library

Shipping Under Pressure

While building infrastructure, I also led delivery on critical projects:

  • Mobile messaging app redesign: Re-architected a desktop-only doctor messaging app for mobile-first in under one month. Collaborated closely with design on UX; paired with a junior developer throughout.
  • Doctor-to-doctor communication app: Took over a stalled project from another team. Directed 6 developers (mix of senior, mid, and junior) to deliver on deadline. Features included messaging, WYSIWYG email composition, and patient treatment tracking.
  • Electron medical dashboard: Mentored a junior developer through an entire build, call detection, phone integration, and client data queries. Used it as a teaching opportunity to build pipelines and the component library.

Hiring

With the senior role still vacant, I led the hiring process:

  • Interviewed 13 candidates (5 senior, 8 junior)
  • Hired a senior developer who became a key contributor
  • Recommended a junior candidate whom another department hired

The Impact

  • 30+ documented components in the shared library
  • 80% of Health vertical applications adopted the library
  • 7 developers trained on React and library contribution
  • 4 junior developers mentored, one promoted to Senior, another went on to work at JPL
  • Delivered mobile app redesign in under 1 month
  • Successfully shipped doctor-to-doctor app after the previous team couldn't deliver

Why I Left

I asked for a promotion to Senior after a year of performing at that level, leading teams, architecting systems, and hiring. I was told it was "too much too soon." I left voluntarily, frustrated by the gap between my responsibilities and my title.

What I Learned

This role proved I could lead without authority. But it also taught me to advocate for myself; doing senior work doesn't automatically get recognized. You have to make the case explicitly.

Tech Stack

React, Redux, AngularJS, Angular 2+, Electron, JavaScript, TypeScript, CSS, Webpack, npm, CI/CD