Inside Noyo Engineering: Coding the age of connected insurance
The task of building a powerful new data exchange infrastructure for the insurance industry is a big one. That’s why we rely on our talented team of engineers to embrace this huge opportunity and tackle challenges with creativity, boldness, and careful attention to detail.
Our engineers build the API technology that makes fast, seamless, and secure data exchange possible for our insurance carrier and benefits technology platform customers. Not only that, but our engineering team also gets to creatively design ways to bridge the gap between legacy technology (like file feeds or PDFs) and the Noyo way of the future.
Noyo engineer Mohsin Haider has been on the job since December 2020, so it was about time we asked him about the hiring process, his day-to-day work, and what he’s excited about in Noyo’s future.
What did your path to Noyo look like?
I knew in high school that I wanted to have a career in software. I got my computer science degree at the Illinois Institute of Technology and during college I was able to explore my career options by holding internships across a variety of disciplines: software engineering, program management, and research. My internships played a huge role in helping me learn about my professional interests before deciding on a single career path.
After college I worked as a software engineer at Relativity, a legal tech company based in Chicago. I was on a team solving interesting challenges with the backend and infrastructure, and during my time there I learned a lot about what goes into developing best-in-class enterprise SaaS.
I heard about Noyo for the first time from our investors at Homebrew. They shared the announcement about our Series A funding and I was instantly interested after reading more about Noyo's approach. I had always wanted to work at a venture-backed startup, so when the opportunity arose to join the crew, the decision was simple!
What was the interview process like?
There was an initial phone screen, then I completed a follow-up technical phone interview with an engineer. Afterwards, I did a take-home challenge that involved implementing a similar system to what an engineer would work on in their day-to-day at Noyo; this was a refreshing change from the traditional algorithmic coding interview. After a few more technical interviews, I was able to meet our founders, Dennis and Shannon, and ask them my burning questions!
What’s a challenging problem you’re working on right now?
I’ve been working on increasing the capacity and efficiency of our integrations with health insurance carriers. We are building new integrations all the time, and our APIs are processing more and more volume by the day, so it’s paramount for us to support our own growth with scalable solutions.
When you think about the future of health insurance, what do you see?
I believe we’re in the early stages of software taking over every industry, including health insurance and healthcare more broadly. Whether it’s Noyo taking on benefits administration, or other companies tackling the provider, payer, and patient experience, there’s an incredible amount of progress being made toward a unified, tech-enabled ecosystem. Noyo is doing something similar to Stripe and Plaid, where we’ve identified a painful, recurring problem in the industry and built a compelling solution for it. Noyo will inevitably become the go-to solution for developers who need to integrate with health insurance carriers.
What are the top three reasons you joined Noyo?
I wanted to work with a founding team that could get me excited about their business, galvanize their teams, continuously recruit great people, and excite potential investors. When I spoke to Shannon and Dennis, I knew they could do that. I would say that was the biggest reason!
I saw the potential for Noyo to become a large player in the health insurance industry. Noyo has some interesting growth levers at its disposal, and I know that growth tends to come with a lot of exciting engineering challenges for someone like me to solve.
Last but not least, I saw a lot of potential for personal growth at Noyo. At a startup, in contrast to a larger company, you’re building zero-to-one solutions that have never existed before. I knew I would get to play an instrumental role in building those solutions and shaping our technical direction.
What’s your favorite Slack channel?
I check #watercooler pretty frequently. The last thing I posted was an article about a man who confused a small town in Maine for San Francisco and ended up becoming a local legend. You should read it!
Noyo is a remote-first team hiring anywhere in the United States. Our engineering team is growing! Explore our open positions here.