Heitor Morandini

Ledgible is a Digital Asset Tax and Accounting Platform for companies and individuals. It generates reports to make crypto tax payments easier.

Working there, I was responsible for maintaining and evolving integrations with crypto exchanges such as Coinbase, Crypto.com, SFOX, HitBTC, and others. Always keeping it well-tested and trying to find ways to enhance performance.

These integrations are a vital platform component to gather the client's transactions faster and grant reliable data to calculate taxes, bringing a better experience and results for the user, thus adding more value to the overall product.

I maintained good communication with the support team to gather information and fix a reported bug in production ASAP.

Tarmac is an outsourcing company to which I was allocated at Napster, the music streaming service.

I was part of the team migrating the legacy code written in ASP.NET to Nest.js with TypeScript. The new code had huge test coverage, which meant a LOT of tests.

Some data wasn't available to fetch directly from the database. It was fetched via integration with older APIs, forming an upstream-downstream data flow.

I had to leave the company due to personal/health issues.

Initially, I got hired to create an Android APP (using React Native) for the associated realtors so they could organize their schedules, have more information about the client while negotiating the plot, and keep the negotiation info up-to-date without using multiple platforms. This helped convert more prospects into actual clients, as the realtor can serve a client more closely and send better information to analysts.

After finishing this first project, the company relocated me to the front-end team, as their senior had left. This team was responsible for developing a new plot "selling"/prospecting website for the company. I've guided and mentored two junior front-end devs to get the first version up and running.

After that, the CTO suggested migrating the React website to NextJS to get better search engine ratings and enhance the caching strategy using the Static Site Generation(SSG) and Incremental Static Regeneration(ISR) features. This migration made page loading times 2-10 times faster and decreased the total back-end calls to at least 50%, depending on the page, resulting in a lower overall cost and a better user experience.

Both projects were backed by a UI/UX designer to ensure we'd stick to his design and thus create an intuitive and easy navigation.

For the first couple of months, I had to create and change some SQL scripts and procedures, fix minor bugs in existing internal tools, and create a couple of automatization tools, such as an admin page to change some properties in the database to change the way that some information would be displayed in the website.

At one point, three other developers and I were tasked with creating a logistic helper platform. The core idea was to enhance suppliers' truck waiting time in the distribution center. To achieve this, we had to develop a scheduling platform with several calculations and estimations based on some delivery information and the distribution center's working availability.

Unfortunately, I couldn't see the platform go live as I had moved on to my next career opportunity. It was estimated to reduce truck waiting times by at least 20%.

SMN is a Software House, which means a lot of projects from a lot of different sectors. I started there as a back-end trainee and started learning Node. After a little while, I got some small tasks using it, getting used to the company's code pattern and understanding how it all comes together, the front-end, the back-end, and the database.

After three months, I got into a project that was starting. The company had a back-end "white label," but other than that, I started the project from scratch with the help of senior devs. It was for a health insurance company that needed a system to manage internal documents and protocols that would transit over several departments.

Even with only 3 people developing this system, a front-end, a product manager, and I, it got considerably large and complex. More than 50 people were using it, handling dozens of protocols/documents per day. To the point that it required a "Trello-like" kanban with real-time events so all the protocols could be visualized throughout the departments to track the time spent in each department and how long it took to conclude. This allowed the company to know where the bottlenecks were and fix them promptly.

After all the major features were concluded, I had time to create new things and help other developers/projects. I made a real-time error-monitoring system for the project mentioned before, assisted with the real-time processing of a project that had a chat, and worked on some minor features and bug fixes. All of which added a motion for some projects in need.