data structure

Global economic downturns, opportunities dried up, amidst these troubling times I shared the same fate as many others. Laid off during the 2nd round after 3 wonderful years at Ninja Van with Driver team, I was on a work visa timer, searching for a new spot in Singapore during Fall of 2024. This blog post provide a summary of my searching and interviewing experiences for Backend Software Engineer roles after around 150 applications, 96% rejection rate, 30 technical rounds, 5 final rounds and 2 offers.

Working on the database project Keva has given me the chance to learn and experience on many new things. When learning about the replication feature. One small part of process called partial synchronization required the master node to give the slave nodes the chunks of write commands starting from a specific offset. This means the master node need a data structure to store those write command and that data must be easily copied and send to the slave node.

When developing the server for a learning project database Keva I got the chance to learn a bit more about non-blocking I/O (NIO) and their libraries in Java.

In my first internship, one of the tasks I had to do was learned about Go as well as revised on design patterns. So I mixed them together by trying to come up with my own examples for the patterns and implement them in Go.

During 2nd year at university there was a team project about using knowledge of Object-Oriented Programming to design a data system that works well with basic geometry shapes.