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.
No adjusters, no negotiating, no deductibles. What you see is what you get.
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 chill people that have done this before. We work with some of the best elixir engineers on earth. It's a cool 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 to keep our internal APIs simple and meaningful, well documented, and powerful. 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.
After you join, the technical team will consist of:
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.
We pay tip-top of market for Mexico, and competive everywhere.
Honestly, is there a benefit that really matters to you? Just tell us. The answer is probably "yes" as long as you're getting stuff done. That being said:
Interested? Please write me directly at firstname.lastname@example.org