Customer Comes First
Feedback from our customers is key in transforming the insurance space.
A person considering a new job offer should be able to understand which benefits package will best meet their needs. A family working on their finances should know how much they will need to budget for their child’s braces. Someone heading to the doctor should be able to confirm their visit will be covered right on their phone.
The past several years have seen a welcome rise of consumer-focused software that puts these connected experiences within reach. Now more than ever, consumers are getting the support they need to engage with their health insurance by having access to the right information in the right context. We continue to see acceleration toward integrating insurance experiences into the consumer’s everyday life as new software, products, and services hit the market.
Behind the scenes, however, there is an enormous challenge: insurance companies and software companies must exchange a great deal of sensitive data, and traditional ways of managing this process are time-consuming, expensive, and error-prone. At Noyo, we’re bonded by the mission to solve this problem, making it possible to provision and interact with critical, sensitive data – securely and at scale.
Depending on the team, engineers have frequent opportunities to participate in conversations directly with clients (if they are interested in doing so). Communication with customers occurs on a weekly or sometimes daily basis via meetings (primarily Zoom) as well as synchronous Slack channels. When working with benefits platform customers, engineers receive feedback about API design, work with our product team to gather requirements from customers, and provide guidance for customers as they integrate with the Noyo API. When working with our insurance carrier partners, we are often designing and developing solutions in parallel. That means coming up with solutions alongside our carrier partners, building a comprehensive understanding of their systems, and providing guidance for how best to work with Noyo.
As we scale, we will continue to build out our customer success team, but we believe that engineers should never be too far away from the end customer.
Engineers are involved in the entire product development process from ideation to design, launch, and beyond.
We believe in a close relationship between product and engineering. Within our larger engineering team, we are organized into smaller product/engineering teams that are comprised of a product manager along with a number of engineers (and sometimes a UI/UX designer as needed). These smaller teams mean that engineers and product work very closely with each other throughout the whole product development lifecycle. Engineers are involved in the process from the point of ideation through product design, technical design, scoping, phasing, and launch.
We don’t have a separate QA team – engineers and product managers work together to build a testing and rollout plan for each launch. That plan often includes a combination of unit and integration testing along with phased launches, feature flags, and proactive alerting to reduce risk during deployment and give us easy ways to roll back if necessary.
Following a launch, features and products continue to be owned by the same team. The team is responsible for monitoring the health of that product, establishing and tracking relevant success metrics, and rolling out fixes and improvements over time.
Team is Diverse
Building a diverse and inclusive team is top of mind for us as we continue to grow.
We are proud to be a diverse company with a female CEO and co-founder. We believe that the strongest teams have many different backgrounds, interests, and perspectives, so we work hard to eliminate bias from our recruiting and hiring practices. Our company strategy for fostering an inclusive culture also includes compensation transparency, learning and development opportunities, and an employee working group dedicated to justice and equity.
Engineers on our team span across different age groups and experience levels; some have worked at startups before and others have only been at large, publicly traded companies; some are parents and some aren’t; and some are far along in their careers where others are just starting out.
We know that great talent can come from anywhere, so we aren’t looking for brand-name universities or certain companies on your resume. Instead, we make sure to source candidates from all walks of life and give each person an interview process that sets them up for success (no surprise whiteboarding here!). We are constantly evolving and improving our approach to sourcing, recruiting, and hiring to ensure that we are building a team where anyone can belong.
Flexible Work Arrangements
Outside of core working hours, we trust you to manage your time.
Noyo is a distributed/remote company. We are hiring for all roles across the United States, though we do have offices in San Francisco and Durham. Going into the office is optional for everyone; we won’t ask anyone to relocate, and you can work remotely even if you live in a city with an office. On the engineering team, we are spread out from coast to coast, with someone in every time zone in between. There’s no significant concentration of engineers in any particular location – we truly operate as a remote team.
In order to facilitate collaboration across time zones we have core working hours: 9am-2pm PST and 12pm-5pm EST. These hours are when meetings should be scheduled to ensure all team members can join and the hours during which team members are expected to be generally available via Slack or other communication methods. For the average engineer there are typically around 5 hours of recurring meetings per week (mostly standups and sprint ceremonies). Outside of these hours, team members are trusted to get their work done in a manner that works best with their schedule and working preferences.
Approximately 20% of the engineering team are parents, we’ve had numerous team members have children while at Noyo and take advantage of our 12 weeks of parental leave. Throughout COVID we have also supported employees working on different schedules to accommodate childcare responsibilities or take care of personal responsibilities. At the end of the day, our team works from a position of trust – we trust that our team members are responsible and capable of getting their work done without micromanaging.
EQ > IQ
We believe in transparency – starting with our interview process.
We’re looking for team members who are kind, empathetic, and able to communicate and receive constructive feedback. That’s why we structure our interview process to screen for EQ. We want to put candidates in the best possible position to succeed. When you interview with us, you’ll know who you’re speaking with ahead of time and what you should be prepared to talk about with each interviewer. From the phone screen to the onsite, we want to make sure we respect your time and are transparent at every step. For example, we structure the technical portion of the onsite in a way that mimics what it would be like if you got the job. You’ll be prepped ahead of time on the coding piece (which is structured as a pairing exercise) so you can choose to write some code ahead of time, or not, depending on your preference.
Individuals at Noyo are quick to help one another, whether it’s with the onboarding process or brainstorming on a tough problem. We’re also very respectful and mindful of the language we use during code reviews and follow specific code review guidelines. At the end of the day, we operate from a place of trust and want to help you do your best.
Safe Environment to Fail
Our number one priority is to focus on solving the problem at hand.
It’s inevitable that mistakes will happen, but we never place the blame on any one person. Rather, if an incident does occur, we remain calm and identify as a team how we can mitigate it. Once we’ve rolled things back to a safe point and limited any of the risk, then we can address the root fix. Our post-mortems are always blameless and we keep a running document of the timeline as things are happening so we have a reference.
We operate from the principle that if one person was able to cause a problem, then it’s a failure of the system. There should be enough checks that it doesn’t come down to one person doing something wrong, and if that’s the case, then we need to reexamine the processes we have in place. This helps us build stronger safeguards against future failures and ensures we can continue to take risks and innovate.
We’re modernizing the infrastructure for group benefits from start to finish.
Traditionally, the health insurance industry is prone to errors, wasting more than $17B annually. With requirements like having to fax in forms, it’s also hard to know how safe your data is. Unlike others in the space who are operating on FTP files and fixed width mainframe formats, at Noyo we use a modern, API-driven cloud based infrastructure. Our cutting-edge technology allows transactions to process faster and groups to onboard more easily. It also makes data syncing between our customers and insurance carriers fast and easy.
While Python is our domain language of development, the coding challenge in the interview is still set up in a way that people with non-Python backgrounds can complete it. Our infrastructure is orchestrated using Kubernetes and we use Docker for deploying, but we’re open from a tech standpoint. If you’re interested in a certain language or part of the stack, but don’t have experience in it, that's not a blocker at all. We look for folks who are open to growing and learning new frameworks. In fact, individual teams are empowered to advocate for decisions around which tech to adopt, especially as we continue to grow.
Committed to Personal Growth
We’re intentional about helping team members grow within the company.
What differentiates us from many other early-stage startups is the strong emphasis we place on seeking to continually better ourselves. Since the beginning, we’ve been focused on making sure the engineering team has structure around our internal leveling processes. We have structure and expectations in place for every role that are clearly communicated and used to make sure we’re offering equitable compensation. As a company, we also have bi-annual professional development sessions, which includes a combination of 360 feedback, self-reflection, and manager review. It’s safe to say we have an internal growth mindset and want managers to advocate for their direct reports and help them develop the skills they need to be successful.
As an engineer on the team, you’ll get a lot of exposure to other parts of the business. You can expect to collaborate closely with the product and operations teams and gain insight into how the business is being run and how we think about things strategically. If this sounds like a good fit, we’d love to hear from you!