Richard Ajala

I’m a product manager who focuses on what makes people feel like a product was built for them. I believe differences are a strength, and product work should consistently translate needs, context, and constraints into clear experiences.

At Tillster, I lead catering and group ordering across a restaurant technology platform serving 100+ QSR and fast-casual brands. I worked with data science on OrderReady AI confidence and fallbacks, used Mixpanel plus operator interviews to diagnose checkout drop-offs, and helped shape wording and flows so corporate customers could lock in orders and complete payment before pickup. I also built roadmap work in Jira/Confluence (user stories, sprint breakdowns) and drove integrations like the Grubhub catering PRD—mapping edge cases so catering orders flow through the same system as regular delivery.

Previously at Mosaic, I redesigned the solar loan application flow for mobile by pulling drop-off data from Looker and validating the experience in person. I worked with underwriting and compliance to split prequalification into a SwiftLink flow and then ran A/B tests across multiple states, with follow-on improvements from call-center feedback via automated reminders. I also supported competitive product positioning through win/loss analysis, updated onboarding/pitch materials for transparency and personal support, and partnered on an Aurora Solar integration to refresh specs automatically when inputs change—reducing rework for contractors.

Earlier, I designed the PowerSwitch deferred-payment product around a key customer risk, using Figma wireframes and compliance-reviewed disclosure wording, then improved onboarding clarity with launch reminders after testing showed customers forgot details. I also built parts of the homeowner portal using Amplitude support insights and implemented monitoring integrations (Enphase, SolarEdge, SMA). My foundation includes technical execution—API tooling at Woflow and Python/SQL automation plus dashboards as a Technical Analyst at Citi—so I can bridge user needs, experimentation, and engineering decisions.