Silvio Marques Email & Phone Number

State Of Santa Catarina, Brazil

State Of Santa Catarina, Brazil

Venâncio Aires, Rio Grande Do Sul, Br

I was responsible for leading all engineering chapters of a multipurpose software product, which had 20 engineers at a given period. Over these 2 and a half years, I recruited, trained and/or managed around 40 professionals.Although the means by which I delivered results varied depending on the company's situation at each moment, something remained constant: I was one of the main culture catalysts. I encouraged continuous improvement, I encouraged the team to question things, I advocated transparency and good communication, and I had a true commitment to people's well-being and the success of the business.I directly led dozens of reliability engineering initiatives, implementing monitoring and autoscaling across multiple services. I directly conducted massive load tests (up to 1 million requests in 10 minutes, with peaks of 100 thousand per minute). I helped build a robust infrastructure to smoothly support a SaaS that received up to 1 million requests daily with 100% uptime.---

As front-end leader, with the intention of standardizing the codebase, I brought some design patterns and development methodologies to the team. I defined domain scopes and encouraged the use of good practices, such as cohesion and decoupling of modules. I also introduced performance practices like lazy loading.I advocate using native web APIs - like IntersectionObserver - rather than third-party libraries, to avoid unnecessary dependencies. I also advocated pure styling, with mostly flexbox, and maximizing browser compatibility. I optimized the project bundle, defined a zero-warnings practice, implemented error tolerance (like React.js Error Boundaries).I got the team to start unit and interface testing and, overall, made a positive impact on the DX, UI and UX. In the past, some critical parts of the front-end broke frequently, something that stopped happening after test coverage. I also had a very keen eye for inconsistencies, and made sure things were symmetrical and pixel-perfect by the time.I accelerated the technical evolution of front-end devs, by proactively researching practices and bringing them to the team. I also played a big role in showing the company's managing partners the importance of architecture and testing, and thinking before implementing things. Constantly caring about the company's future led me to the position of Head of Engineering.---

As a developer at Ensinio, I genuinely understood what it's like to work collaboratively in a development team, and especially in a small startup. I understood how to manage complex states, did pair programming and built part of a foundation of interfaces that were later used by thousands of people. The product was an all-in-one and white label platform, with multi-tenancy architecture, packed with a range of diverse features: courses and classes, video streaming, social networking, payments, and more. The fact that we were building a product that had to meet many business models and that had a great capacity for customization (colors, layout positioning, etc.), made this a challenging experience.Although I also learned a lot from my colleagues, I often helped other devs, identified non-conformities in interfaces and suggested changes. I also introduced the practice of code reviews to the team. As the app gained complexity, I noticed that many things in the initial design would not be sustainable, and I carried out massive refactorings that made the project more organized at the time, improving the development experience. This led me to a technical leadership position.---

In July 2018 I did my first freelance project: an e-commerce, made with OpenCart. Then a website for a coffee shop and flower shop. Then a website for a tech school for children. Then to a law firm. And so it was: I signed a new contract every one or two months. I built a good reputation at Workana, a freelancing platform. I did a bunch of projects with Wordpress and WooCommerce at that time, and a lot of workarounds with CSS and JavaScript. I made integrations with several external APIs, such as postal services, email marketing APIs, etc. I learned more about web hosting, DNS and databases. I also did my first projects with React.js, React Native and Node.js.I had contact with several different techs, and developed a better understanding of what suited best for each project. I've practiced a significant amount of requirements engineering at that time. A client from 2018 continued hiring my consultancy until 2023.I learned a lot about how to talk to non-technical people, how to prospect customers and solve real problems through technology.---

After learning how operating a gaming community could become a business, I decided to create one of my own. I sent dozens of emails to gaming influencers telling them about my experience so far and suggesting a business model, until I found a partner: André ("Afreim"), a content creator with 5 million followers at the time.In a nutshell, the idea was to build a community around a network of minecraft game servers, selling digital subscriptions that would give players more items compared to non-paying users.While my high school friends were kissing girls, I was probably trying to fix some "out of memory". But I had a big motivating factor at the time: helping my family financially.Somehow, I gathered a team of approximately 15 people (designers, devs, map builders, etc.), and we spent 1 year developing this product. I didn't know it at the time, but I was learning through practice all the main steps needed to deliver software. And most importantly: how to fail a business.Here I worked directly in web development, game plugin development and cloud computing. I also managed everyone, and did a little bit of everything, from network configuration on linux VMs to making funny tweets on the company profile. If we were in an office, I would clean the floor and make coffee.I was so proud of the product, and the feedback from the first few dozen players was great. But it's not so easy to be happy as a first-time dev: at the product launch event, 300 people simultaneously accessed the game's servers in a few minutes, and our infrastructure couldn't handle it.What a surprise, right? We didn't know much about reliability, and I hadn't even conducted a load test at the time. In the first few weeks of the game servers going live, we lost a lot of credibility due to frequent outages and periods of high latency. This was the "fire" for me to develop a new interest in the future: SRE.---

From that moment on, I understood that I wanted to work with technology. The experience of maintaining and evolving a software product, even in an amateur way at the time, was magical. For the first time, I saw thousands of people using - and loving - features I helped design. Here, for the first time, I made servers crash, and did things like forgetting my first extra semicolon in production. But I've also done wonderful (and scary) things, like keeping windows servers with 128GB of RAM and 60 java processes up and running, serving thousands of players every day.Here I created my first Trello boards, did my first requirements analysis, and managed my first development team: 2 other teenage devs.---

As a volunteer manager of a gaming community, I learned how to manage company expectations, ensuring that the community was attractive and safe for players. I continued working on the customer experience, answering questions about failed payments, product bugs, analyzing reported users, etc. Throughout this experience I learned the importance of documenting processes and teaching people. I learned how to conduct interviews through the various selection processes for community moderators, and began my journey in leadership and people management. I also learned about scriptwriting, producing and editing videos.The fact that I was very involved in the success of the community, and added value to the popularity of the product, led me to be invited by the partners to manage the software product itself.---

As a volunteer moderator of a gaming community, I learned how to manage expectations of customers and users of software products, and I practiced customer service on a daily basis, answering questions about the product and analyzing user behavior that was reported by the community.My performance as a moderator and written communication skills led me to the opportunity to manage other volunteers.---