Moladin Wholesale Mobile & Internal Apps

MY CONTRIBUTION

I managed products used across two sides of the same operation. On the field side, the Android app supported Agent Sales Officers throughout their work, including vehicle inspection, listing, sales activities, and transaction-related workflows. On the operational side, internal applications supported the teams responsible for managing listings, transactions, user access, operational controls, and fraud-related workflows. My scope covered improvements across both surfaces. I worked on initiatives ranging from guided inspection experiences and internal communication features to access management, policy enforcement, and fraud prevention. I worked with a dedicated squad consisting of Android, frontend, and backend engineers, QA engineers, an Engineering Manager, and a Technical Program Manager. This gave me end-to-end exposure to a much more structured development cycle than I had experienced before.

PROBLEM

The products sat directly between field activity and operational control. Field agents needed tools that allowed them to work efficiently while inspecting, listing, and processing vehicles. Operational teams, meanwhile, needed enough structure and control to maintain data quality, manage transactions, enforce policies, and identify suspicious behavior. Improving one side without understanding the other could easily create new problems. Too much friction could slow down field operations. Too little control could introduce operational or fraud risk. The product problem therefore wasn’t simply about making workflows faster. It was finding the right amount of structure for different users operating within the same business process.

OUTCOME

During my time in the Wholesale Core Operations squad, we delivered improvements across both the Android and internal operational products, covering field workflows, operational controls, communication, access management, and fraud-related capabilities. My time with the team ended earlier than expected as the technology downturn led to organizational layoffs. Because of that, I don’t frame this period around a large transformation or long-term business outcome that I stayed long enough to observe. Its more lasting outcome was the working model I took with me.

IMPACT

Moladin gave me a reference point. It was the first environment where I experienced many pieces of product development working together at the same time: clearer squad ownership, dedicated engineering capacity, QA, regular development cycles, product analytics, instrumentation, and a stronger connection between discovery and delivery. That reference became surprisingly useful later in my career. Not every organization has the same product maturity, tooling, structure, or leadership support. Once I had experienced one working model, however, I no longer needed every environment to tell me what good product practice could look like. I had a compass.