Front is the leader in customer communication that brings teams together to offer tailor-made service at scale.

As an individual contributor of a team of 15 people, seven of whom were engineers, delivered backend features and conducted interviews for the team.

Designed and deployed a delivery status checking pipeline on AWS for sent emails; this feature enabled two of our largest customers (~60000+ messages sent/month) to rely on Courier to verify 100% of their emails sent via SendGrid and Mailgun versus having to design their own system and correlations to check delivery status.

Optimized the message sending pipeline in AWS to be more performant. Reduced back pressure of messages sitting in the streams for minutes to hours down to two three seconds of delay.

For three months, conducted technical and behavioral interviews least once a week to hire people with skills in React and AWS. Led to building a team of three engineers to a team of seven engineers that could tackle a wide range of feature requests.

Responsible for mentoring one engineer and ensuring the stability of the backend systems including Kubernetes and PostgresSQL. Reported directly to the VP of Engineering to decide on product roadmap, feature prioritization, and ensuring our work directly impacted sales.

Managed a team of four engineers who were across three functional teams. Responsible for their growth, helping them choose and encouraging them to use their yearly training funds, and tracking their milestones for a promotion and raise.

Conducted weekly 1:1s with each teammate to ensure they had a set time to raise concerns, ask technical questions, and ask questions related to working within start-up. The engineers felt they always had a chance to reach me and know that I was there to ensure they were successful.

Implemented SMART criteria documentation with another manager to concretely establish where an engineer can grow in a specified amount of time. Documenting achievements and progression enabled the engineers to clearly see how they were doing and if what they were doing was aligned with their motivations.

Participated in both technical and behavioral interviews for engineers. Led to hiring of two senior engineers that could work in a remote environment.

Ranging from individual contributor to feature team lead, designed, planned, and delivered multiple features for the Analytic dashboards for Winmore.

Researched and proposed our external querying language to be OData in 2015. Planned out the sequencing of which supported functions should belong in version 1.0. Set up a path to abstract OData over ElasticSearch queries with a path to apply OData on top of PostgresSQL when the team decided to remove ES from the infrastructure. Ensured that the team could transition the underlying technology without introducing bugs and tech debt while staying on a timeline to deliver the product to the general audience.

Mentored an engineer to learn how to make changes to the OData querying library and provided a large suite of unit tests to prevent regressions. Led to the engineer becoming the domain expert of OData and being able to add and change features without concern of breaking 1000s of queries occurring per hour.