Alejandro Mejia

I began my career as an Android developer by designing a system that allowed a company to count the amount of products it had. This system integrated MQTT technology with real-time responsive sensors in the mobile application. I developed the entire project using Java with an MVP architecture and an intermediate layer called "business" to facilitate communication between the presenter and data layers. In my second role as an Android developer, I joined a fire protection systems company. We had an application that worked both online and offline, and our responsibilities included scheduling and preparing technical visits for the company's technicians to inspect various fire protection equipment. During the first year of development, we used Java exclusively. In the second year, two developers, including myself, migrated all the modules to Kotlin. We worked on designing views in XML, implementing best practices, and transitioning from an MVP architecture to an MVVM architecture. We also implemented dependency injection using DaggerHilt, made REST requests with Retrofit, and handled database operations with Room. Additionally, we incorporated various technologies such as MQTT, Firebase for authentication, Crashlytics for crash reporting, and push notifications using tokens. We managed maps with Google Maps dependencies and used coroutines for asynchronous operations. In my most recent job, we adopted the MVVM architecture, Clean Code principles, and design patterns. We made REST requests using Retrofit, data persistance in databases with ROOM, implemented dependency injection with DaggerHilt, integrated various dependencies like Google Services, Firebase, and Glide for image handling. We used coroutines for asynchronous operations, conducted testing with JUnit and MockK, and made service calls to Plaid and Vezgo. Additionally, we developed interfaces for managing these services and handled video playback with ExoPlayer.