And we're fixing it. We routinely save people from spending thousands in unnecessary premium, choosing plans that don't cover their doctors and prescriptions, and from going without insurance for a year. We're growing quickly in a $20B market, we've raised over $2M, and our revenue recurs for 15 years.
You’ll own engineering at www.fairsquaremedicare.com, which takes a senior from knowing nothing about Medicare to feeling confident they have the best health insurance their budget allows. You’ll report directly to the CEO and own:
You're a product-minded engineer with experience managing others. You've orchestrated and built dazzling consumer web experiences and maybe even conceived of them yourself. You're not a designer but if you weren't working with one, you could put together a nice UX/UI on your own using Bootstrap. You want to talk to customers. You've had side projects. And you're good with React, graphql, and node.
Dan founded Fair Square Medicare after watching his parents struggle through the Medicare shopping process. He previously was the technical co-founder at Trim (post Series A; valued @ > $30M), Octane Lending (Growth stage, valued @ > $300M) and has held product and growth roles at Redfin, the Climate Corp, and AppDynamics. He studied Physics at Yale.
Chris is the health insurance agent Dan's parent's found after a long and painful search. They love him. He's helped thousands of seniors across the U.S. navigate the minefield of Medicare. His core value: "treat clients as if they're your family".
We are building for our own parents.
We believe that your character as a person is shown by how you treat others. Especially when everything isn't hunky dory.
You deeply love building dazzling web products. To the point that when our team grows and you become a manager (if you want to), you'll have days where you seriously consider going back to being an IC.
Your mind is a function that returns a point of view given a set of data and assumptions. Understand this function's body and explain it to the team so that they can review it and help you make sure it works.
We love to geek out about how Graphql >>> REST. And we use it because a strongly opinionated API layer helps us iterate faster toward a product our users love.