Remote: Yes
Willing to relocate: No
Technologies: Python, FastAPI, TypeScript, Node, React, Next.js, Tailwind, Go, Java, Spring Boot, AWS, Terraform
Résumé/CV: https://docs.google.com/document/d/1WLzFsXfIlFZDn0o-V04Giipp...
Email: [email protected]
Software engineer with more than 10 years of experience, working remotely for US startups for the past 5 years. I've owned projects end to end with a product mindset that has allowed me to design impactful solutions that brought great value. Here are some of my achievements: At Moskit CRM, I helped the team scale the product and increase its MRR by more than 15 times in less than 3 years. At Jobble, I proposed and led the implementation of an EDA that improved payment reliability and reduced the time spent on payment reconciliation by over 90%. It also improved the efficiency of the engineering team, as the same EDA was used to implement other features. At COVU, I developed a new ETL system that enabled the company to perform complex data analyses that were not possible before, improving the decision-making process.
There are so many softwares, languages and frameworks that have the so called "core". This is something that I struggle for a while because to me it's not that clear what should be considered the core. When do we need to create a core package? Do we even need a core package? What should it contain? What do you guys think?