Huckleberry

• We are big fans of TDD and really reap the benefits of moving fast with the minimal worry of unintended side effects.

• While we spend most of our day in JS, we spend a decent amount of effort utilizing some spectacular ML to augment various aspects of our on-boarding and operations flows.

• We utilize the majority of modern React design principles to build best in the breed, sustainable, composable, and idiomatic code.

• We are focused on building world-class user experiences and are willing to put the engineering effort behind seemingly simple user conveniences that reduce friction.

• We don’t build in silos and encourage feedback from our peers. Nobody in the organization is immune to a PR review.

• Usability isn’t just for our app’s user experience. We believe that philosophy transcends down to ‘how’ we build things as well.

A primary attribute that differentiates Huckleberry from traditional insurance providers is our ability to take a customer through an end-to-end experience in exponentially less time than a traditional provider or even existing online competitors. The challenge in accomplishing our record times lies in our advanced automation solutions. To maintain our extremely high customer experience standards, we must think out of the box and automate as must as possible in the end-to-end process that happens often in parallel behind-the-scenes as a customer transitions through our on-boarding quote-flow. The technical challenge therefore is maintaining the user experience in conjunction with the technical architectural challenges that come with combining a large number of different processes behind the scenes between Huckleberry, the customer, our insurance partners, and third-party integrations.

We have built elegant solutions to distill the archaic technology partnerships to a modern, mobile-first interface. One example of where we have engineered a solution to a complicated third-party integration is how we handle slow response times from certain third-party API integrations. We offset the necessary wait time by rearranging the user flow. A specific example of this occurs when the user creates a password for their account - behind the scenes, we are actually subtracting the time to create a password from the time to hit a third-party API.