Founding Software Engineer

About Superpower Superpower is on a mission to change the way people engage with their health, for life. Let’s face it: If healthcare were built today, it would look completely different - personalized, preventative, performance-enhancing - with an iconic, category-defining brand and cult following. To do this, we’re building the most comprehensive and convenient healthcare system on the planet - a thoughtfully designed, all-in-one platform for easily improving your personal health. 👨‍💻 Our Website 📖 Our Manifesto About this role As a Founding Software Engineer at Superpower, you’ll be responsible for these core areas: ⭐ Engineering: You’ll need to write code - a lot of code . Your most important responsibility is to ship more of our product and maximize the number of product experiments Superpower runs. You’ll make key architectural decisions that will be the pillars of the engineering organization for years to come. You’ll make serious trade-offs to balance speed of execution with quality. You’ll decide what technical debt is worth taking on, what components should be built versus bought, and when it’s worth spending an extra week to engineer a solid foundation. You will be the de-facto developer operations engineer. You may be responsible for setting up project management processes, troubleshooting performance and reliability issues, and instrumenting the CI/CD pipeline. Product You’ll have a significant amount of ownership over the product direction. You should expect to spend time talking to customers, teasing out use cases, and making prioritization decisions on the short-term & long-term roadmap. In many cases, you’ll be building features in the absence of any formal product requirement document. You may even end up designing small items in Figma every once in a while. Support You should also expect to spend a fair amount of time in the trenches supporting customers. You’ll probably find yourself engaging with customers & partners in shared Slack channels, emails, or Twitter threads to answer product questions, triage bugs, or gather feedback. You’ll also get quite used to the friendly sound of PagerDuty alerting you when the product is down. In addition to putting out fires, you’ll also be responsible for setting up the observability stack and defining the processes around support and on-call rotations. People You’ll also be exposed to the people operations side of things – both when it comes to recruiting as well as defining the culture of the company. As a founding engineer, you will spend a ton of time sourcing, interviewing, and closing early team members. You’ll also set the tone for the company’s culture – from small decisions like “what should we order for lunch” or “what sorts of team bonding activities should we hold” to the large ones like “how do we run our interview process” or “how do we approach decision making”. As a founding engineer, you’ll be responsible for answering these questions on a daily basis – both directly and indirectly by virtue of your actions and attitude. Business Although you probably won’t be closing deals or making pitch decks, you will certainly be expected to sell the product and pitch the company’s vision. As a founding engineer, your job is to support the founders in doing whatever it takes to get the product to market. You will “always be closing” – whether that’s reaching out to former colleagues, classmates, or friends to get your foot in the door of potential customers or investors. About Us Our team You will be joining an experienced team of multi-time founders – our CEO started two prior companies worth >$500m and our founding team is ex. Amazon, Y Combinator, Goldman Sachs, Harvard Med, Inside Tracker, and One Medical. Our team is small and engineers contribute heavily to define and drive their own roadmap, and use their product sense to define and ship an MVP. Our engineers work closely with our operations team to support and automate existing workflows, other engineers to build new features and resolve deep technical questions, and with our product lead to iterate and ship new features quickly. Our company The company is well-funded by investors like Susa Ventures, Long Journey Ventures, Balaji Srinivasan, Cyan Bannister, Arielle Zuckerberg, Cameron and Tyler Winklevoss, Dr. Jordan Shlain (Founder of Private Medical, Silicon Valley’s top concierge medical company), Justin Mares, the Founder of Doordash and others. We’re based in San Francisco and have an office in SOMA. Read more about our recent launch here . Our technical stack: The Engineering team at Superpower believes in simplicity & excellence - we focus on cutting-edge tools that work for us, ** rather than against us, to innovate in product & healthcare instead of on how we write software, but we’re not afraid to dive into the details. Full Stack TypeScript (with strong ESLint rules and Jest tests) React Frontend built/served via Webpack TailwindCSS / ShadcnUI component library with Storybook Express/NodeJS Backend with Prisma ORM and Domain Driven Design/Layered Application principles Temporal Worker/Scheduling Layer AWS (EKS/ECS, ECR, S3) built & deployed using CDK, Terraform, Kubernetes, Docker, GitHub Actions Productivity tooling & processes: Linear, Figma, Notion, Slack Bonus: Experience working in healthcare / FHIR About you We’re looking for a member of the team who has the following traits: Passionate about health & longevity. Strong Technical Experience - Minimum 2-4 years (ideal: 5-10+ years) of experience working as a software engineer. You’re comfortable with, and excited by, the idea of building a product from the first line of code to production systems serving thousands of paying customers. Tool-Specific knowledge/expertise . You have strong familiarity with building & deploying web applications, writing TypeScript, implementing & testing new features, extracting & transforming data, troubleshooting errors, and building responsive UIs. Extensive AWS experience. You have worked for years with AWS, have familiarity with AWS networking (VPC), writing infrastructure as code (CDK/Terraform), and foundational/security best practices. Confident in your ability to tackle ambiguous problems, build large-scale systems, reason about performance and reliability, and crank out quality code. ⭐ Moves Fast & Works Hard Olympian Work Ethic. We work hard and support each other in doing so. You welcome the challenge and thrive under the pressure of intense deadlines and seeing your code in production the same day or week it is written. Craves ownership - If you often find yourself raising your hand to own things end-to-end, you will likely really enjoy the ownership afforded to you as a founding engineer. We expect you to step up and take on your fair share of the work without being asked, and we all do the same. Handles Ambiguity - You can take a list of requirements and asks, collaborate and ask questions to get the information you need to implement, consider the user in your implementation and product decisions, and take a feature to production without a formal spec. You may even prefer it, to move faster, and because you are confident and take pride in the quality of the work you deliver. Multi-Disciplinary - You should expect a good amount of context switching from day-to-day or even hour-to-hour. A typical day might include anything from several hours of coding, to a few customer conversations, to a technical brainstorm or architecture discussion, to an interview or two. Additionally Loves making customers happy. Loves to learn . Our interview process Here at Superpower, we’re looking for product engineers who enjoy talking to customers, iterating, & shipping quickly, and exhibit a strong sense of ownership and autonomy. Our interview process is designed to find these kinds of engineers. Moreover, we try to ask questions that are relevant to the types of products we build — mostly full stack work, with a bit of database, analysis, and customer interaction. Below is what to expect in our interview process. If you have questions, email us at kevin@superpower.com . Phone Screen (1-2 conversations) . We’ll do a quick phone screen to assess general fit. Technical Interview (Non-Coding) . We’ll talk shop with you to see if we’re on the same page about the technical requirements for the role. Technical Interview (Coding / System Design) . We’ll emulate the kind of problems we expect you to see in day-to-day work at Superpower and the environment of working together. Not Leetcode. On-Site Interview . Reference checks . We’ll ask you prior colleagues about where you thrive most. Offer! We’re very pleased to be working together!