I’ve built a b2b insurance application that allows insurance companies to create template products that car dealerships can choose from and customize as per their needs. This had plenty of forms built with React and Material UI some of which required users to upload template PDFs which would be used in multistage forms where they could decide which fields needed to be filled at what stage and what type of user was responsible for it. The frontend used Redux for state management which helped with role based access control of components. On the backend, the apis were built with Django and python with each api having permissions for role based access.
I believe my experience in different domains makes me an excellent choice for the role of a founding engineer. I've worked at Ramsey Theory Group which was a company with a small engineering team that developed applications in the automotive space. I was asked to lead a team and build a b2b application that was meant for car insurance products that allowed insurance companies to create template products that car dealerships can choose from and customize as per their needs. This had plenty of forms built with React and Material UI some of which required users to upload template PDFs which would be used in multistage forms where they could decide which fields needed to be filled at what stage and what type of user was responsible for it. On the back end, I used Python/Django with Rest API and postgres for database. In terms of deployment, the product used gitlab for ci/cd, docker, kubernetes and rancher for handling various environments and deployments. As a lead engineer, I was tasked with creating the system architecture, delivering the end product and ensuring a thorough test suite maintained its standards. A typical work week usually started with discussing the requirements with my product manager and then mapping out the components that need to be built to achieve the same. Additionally, I worked with the ui/ux designed to streamline designs that would help us achieve our goals quickly. Finally, I worked on the coding aspect of the project and included the mid level and junior devs to replicate the components I built and helping with the testing to ensure the feature's robustness. I also spent time mentoring the engineers to help them achieve independence and be able to create features without my help. At Paypal, I belonged to a team that was a startup that was acquired by them (called Happy Returns). While they belonged to PayPal they had complete autonomy and functioned as a start up. I was involved as a full stack engineer building reverse logistics solutions with React, Golang, Postgres and Rest API. Though this might not be relevant to the current position, before my time as a software engineer, I worked at LinkedIn as product expert handling customer issues and went on to eventually train new LinkedIn hires on how to handle internal tools and customer products. I believe this stint helped me understand how users felt about a product and shaped my approach to writing software from a user experience's perspective.
No skills.
No languages.
No employment history.
No education history.