Front-end / Full-stack Engineer
Súper helps millions of Latin Americans buy their first insurance policy. We design super simple, super affordable, super easy to use insurance for people that (correctly!) don't trust the legacy insurance industry.
We're well funded, backed by highly regarded USA-based VCs. We have a cool product that people want and that respects the customer. We're a team of experienced founders and startup veterans who have done this before. This is a place that’s both a fun AND impactful place to work.
Your core responsibility will be to ship features, improve our code base, and improve our development process and standards. By "improve" we mean help us build highly robust and performant user interfaces. As a core member of a very small and tight team, you'll also be responsible for "raising the bar" when it comes to code quality, documentation, and processes. As a front-end engineer you will:
- Work along with our product, design, and engineering team to ship fast, frequent, and impactful features.
- Work closely with our Lead Designer creating scalable and functional components for our Design System.
- Focus on performance and user experience.
- Assess our current codebase to find new ways to improve our front-end library and improve DX
- Participate in the design process to jointly deliver the product quickly and with high quality.
- Follow the highest standards in web accessibility, helping us to provide the best experience to all kinds of users.
- And most importantly… enjoy changing the industry of insurance in LATAM helping thousands of people to have better lives.
After you join, the technical team will consist of:
- Nine senior elixir engineers
- Our world-class PM Raimundo Esteva
What we are looking for:
- You eat HTML and CSS for breakfast. You know how to make it bend to your will to create the best possible experiences for users.
- You know lots of design patterns (both from a user experience standpoint and from an engineering standpoint). You know when to use them—and when they are over engineering.
- You've got a perspective on the best way to build and manage a reusable component library to scalably build consistent user interfaces across a growing product surface area
- You’re familiar with both client-side and server-side rendering frameworks and know the ins and outs of both.
- Your code, documentation, comments, etc are a delight to read and you think about a future engineer's DX.
- You’re an advocate for the user and like to think about not just how to build something but whether it’s the right thing to build.
- You're an awesome coworker. We have a "no jerks" policy so... don't be one.
What we don't care about:
We don't care where you went to college or whether you have a fancy logo on your resume.
What will your first 30/60/90 days at Súper look like?
First 30 days
You're getting to know the product, the stack (Phoenix), the team and the roadmap.
We'll pick some small features that have already been specced for you to implement, either alone or paired with someone else from the team. We’re a small team, with a small product, so we hope you will get up to speed quickly. You’ll be able to commit code on day 1!
You'll give feedback and expand your technical understanding of Súper's product by participating in code reviews.
By now, you're confident picking stories/features and just getting them done. You are involved with the product process—what can we build? You're already showing leadership by raising the bar when it comes to code style, documentation and readability.
You have ownership over larger complete features, shipping them from start-to-finish and involving other people when necessary.
By the end of month 3, you're totally fluent about the product and the codebase.
Not only are you shipping new, complete features, but you're setting new guidelines—not just for code, but for the entire organization. We're still building our company culture and by the end of this point you should be shaping it as much as anyone else.
The team is continuing to grow, and you're helping onboard new hires. Old features have started to break, and you're refactoring old code given new understanding of how customers use the product and business requirements.
Interested? Please write me directly at: