Liongard

2020 - Present

My Role

When I joined Liongard in 2020 as a software engineer, I quickly found myself stepping into responsibilities that spanned across the engineering department. My manager at the time was stretched thin, so as I improved processes and delivered results, those responsibilities naturally shifted onto my plate.

One early challenge I took on was developing a new integration we called an “inspector.” The project was for JumpCloud, and all previous inspectors had been written in plain JavaScript. I proposed building it in TypeScript instead, laying down proper type definitions and a cleaner code structure. That decision didn’t just improve the project, it inspired the entire inspector team to migrate their work to TypeScript, raising the overall standard of code quality across the company.

Over the following years, I worked my way across nearly every major area of Liongard’s engineering efforts. I was trusted with leading a team that initially focused on integrations but soon became the go-to group for high-priority initiatives and urgent problems. Within two years, I had grown into a senior software engineer role, coordinating deployments of all sizes, guiding cross-team collaboration, and managing the critical systems behind billing and monitoring.

This journey shaped me into the kind of engineer who can dive deep into code, simplify complex systems, and step up to lead teams through company-wide initiatives. I thrive where technical excellence and leadership meet, and I bring that balance to every project I take on.

Site

Tech Stack

TypescriptTypescript
ReactReact
Node.jsNode.js
awsaws
PostgreSQLPostgreSQL
SalesforceSalesforce
CursorCursor

Problem

The company needed to transition from a limited custom billing system in ConnectWise to a Salesforce-based solution with advanced automation. This migration had to be completed quickly while ensuring that billing, provisioning, and partner management processes remained reliable and scalable.

Solution

When I was handed this project, I knew a straightforward “lift and shift” wouldn’t work. Instead, I led the design of a serverless API built on AWS Lambda to bridge our application data with Salesforce. To make sure the work aligned with business needs, I proposed and authored a document that acted as a contract between the Salesforce implementation team and our integrations team. This “contract” clearly defined use cases, mapped Salesforce fields to our centralized database, and established the data dependencies each process would rely on.

From there, I created automated workflows that allowed Salesforce to trigger high-value operational processes: provisioning and deprovisioning partner instances, enabling or disabling product features based on SKUs, and pulling usage data from across all production instances for accurate billing.

To ensure long-term maintainability, I applied test-driven development throughout the build. The result was a resilient, automated system that not only met the immediate deadline but also scaled cleanly as the company grew. What started as a time-crunch migration became a foundation for smoother operations and cross-team alignment—proof that even under pressure, creative problem-solving and clear communication can deliver lasting impact.