Cristian Malpica

Astronomy invites me to move between very different scales: a single observation, a planetary system and patterns far beyond both. I enjoy that combination of evidence, imagination and unanswered questions. Product work also requires movement between scales: understand the wider system, then return to the specific customer, workflow and decision in front of the team.

The same interface, message or process can feel obvious to one person and confusing to another. I enjoy listening to people and noticing where their interpretation differs from mine. At work, that means asking questions before proposing a solution, paying attention to the language people use and treating my first interpretation as an assumption to test against what customers and delivery teams actually say and do.

I approach it as an interested learner, not an expert. What I value is the discipline of staying curious when a subject resists simple explanations, and accepting that a useful model can still be incomplete. Product testing calls for comparable humility: state what is known and uncertain, then define in advance what evidence would change the decision.

Time outdoors restores my attention. It also makes relationships visible: soil, water, climate and species affect one another, and disruption in one place can appear somewhere else. That attention to relationships is also useful at work: I look beyond the most visible outcome and consider upstream dependencies, operational constraints, unintended effects and the people who will carry them.

Training requires pacing, recovery, attention to feedback and the judgement to adjust when conditions change. It also makes the difference between persistence and rigidity very clear. In product work, I use the same discipline to keep the long-term objective clear, break progress into manageable increments and change the route when evidence shows the current approach is not working.

Design helps me clarify the experience; code makes behaviour and constraints tangible; creativity opens alternatives before the team commits. Building small prototypes lets me expose assumptions early, communicate more precisely with technical colleagues and learn from use rather than discussion alone. That hands-on approach also shaped how I developed the pricing-control application.

Sustainability matters to me as a design and decision constraint, not as a slogan. I look for products that are useful, viable, durable and easier to maintain or adapt, while using resources responsibly across their lifecycle. In practice, that means asking who benefits, what trade-offs are being made and whether today’s solution creates an avoidable problem later.

It brings together the parts of work I value most: listening carefully, finding patterns, framing the problem, choosing priorities and helping different functions move toward a shared outcome. The result must do more than sound promising—it must create customer value, work within business and operational constraints, account for consequences across stakeholders and improve against measurable outcomes after launch. That responsibility is what makes product work meaningful to me.