Inderpreet Singh

Background

About Inderpreet Singh

I wrote my first piece of code in a language called BASIC, on a DOS computer that had no GUI. I was 7 years old at the time. I immediately fell in love with computers. Technology became an escape, an enjoyment, and I have been fortunate enough to turn my passion into a profession. Today, I work as the VP of Engineering for RANADEV, a Design-Driven Dev Agency in Seattle. I also own RYAZ.IO, a dev agency in India. I have been through a very exciting journey, from a small kid struggling to learn loops in BASIC to becoming a technical leader, working with the hotshots of my industry. Under my leadership, the projects have gone on to secure millions of dollars in funding. I have also been in the front seat, seeing companies go from broke to a million dollars a year in revenue. I also created my own moderately successful agency, an agency that never took funding, always stayed in profit, and the best part is it only took 10 hours per week of my time. In the future, I want to take on Engineering Manager roles to help teams become independent, efficient, and consistent at delivering high-quality code. I have done that enough times to confidently promise results. I have been a coder for a long time before I gradually transitioned into management roles. As an undergrad, I loved managing memory in C++, automating my Linux machine with BASH scripts, optimizing code to milliseconds. But I have also loved designing experiences in HTML/CSS, and performing animations in JavaScript. When I left college, my career needed me to get focused, so I chose the JavaScript ecosystem. It worked everywhere, which made me feel I wasn't losing anything. I started with Meteor.js but soon switched to React.js and React Native. I have worked on cross platform apps using Electron.js. I was one of the few front-end engineers that could write killer CSS but, when needed, could assist a backend developer in designing a better database schema. I was focused on front-end, but I didn’t lose touch with other parts of the stack. I was useful to every member of the team. This usefulness made me uniquely suitable for senior and leadership positions. I didn’t know everything, but I knew enough about each part of the stack to be able to make cross-team decisions effectively. Somehow, I don’t find management and leadership much different from coding. I break the problems into their smaller counterparts, build strategy like I would write an algorithm, and then execute it. After a few iterations, the strategy works, and we get the results.