Bruce Gill

Enzy is a B2B sales performance platform — Angular on top of Java and Spring Boot — used by more than 200 business customers and thousands of daily users across door-to-door sales organizations, including Aptive and Sun Power.

The incident I get asked about. One customer's cluster started running hot and stayed that way. There was no obvious deploy to blame, so I worked backwards from sustained CPU to request latency to the queries underneath it, and found a single unbounded query pulling 4.3 million rows on every request. The fix reached past the query itself into infrastructure, so I took it to the infrastructure lead and we shipped it together. Service was restored.

Release ownership. I was one of three engineers trusted to own weekly releases — coordinating QA, cutting release branches, writing release notes, and shipping to production — and led team standup for two months.

What I built. A greenfield campaign builder integrating Twilio for SMS and SendGrid for email, replacing a manual outreach process: I owned the data model, the Spring Boot backend, and the Angular UI, and delivered it alongside a junior engineer. A full-stack sales funnel modeling tool built on top of the existing leaderboard queries, defining the funnel data models in SQL so customers could configure their own funnels and rep-level goals, now rolling out to all 200+ customers. And a front-to-back integration of an internal AI-generated incentive service — rep competition brackets and prize configuration — including a feedback loop that returned user-edit signal to the AI team.

I also proposed a Redis-backed caching strategy for the leaderboards, to cut the redundant database row scans behind tens of thousands of daily views while keeping the numbers real-time. Alongside all of it I mentored an intern through code review and architecture discussions.

Sprout-Kids makes children's furniture. I was one of two engineers, and between us we built and maintained every internal web application the 50-person company ran on — Python, Django, and jQuery. The clearest way to describe the stakes: when the platform was down, production stopped company-wide.

I designed and shipped the production scheduling tool that team leads used for roughly 100 orders a day, plus a floor-facing tool that sequenced work for production teams and tracked part-level defects, raising rework requests automatically. I built a bill-of-materials traceability tool that mapped 50+ core products — thousands of SKU variants — to every component part and every valid manufacturing path, and an employee self-service portal used by all 50 employees for pay and PTO.

On a team that small you own things end to end, so I did: Django models, views, and templates, straight through to the people using them. I worked directly with the CEO and with manufacturing stakeholders, and sat on a weekly cross-functional technical council that resolved production floor problems with software.