Process transparency & learning-in-public (Substack-style content)
Hot chocolate (I don't drink coffee!)
Can you share a moment when a system you built genuinely changed how people worked or made decisions?
At Mashreq Bank, I worked on a decision engine called OMDM that powered business rules for credit policy decisions. After spending months deeply understanding the system—writing rule logic, analyzing data flows, and observing how approvals were triggered—the organization decided to migrate to a new platform. I was the only person on my team assigned to handle the migration, even though I had no prior experience with the new tool.
I collaborated closely with the Qatar business team, attended demos, asked detailed technical questions, and broke the migration into manageable components. I rebuilt rule logic, validated data mappings, and resolved recurring errors that had previously disrupted daily processing. Over three months, I completed the transition and stabilized the system so credit decisions could continue without delays or inconsistencies.
What made this meaningful wasn’t just completing a technical migration—it was knowing that the policies I rebuilt directly influenced real financial decisions. The team regained confidence in the system, workflows became more structured, and I realized I wasn’t just maintaining a tool—I was shaping how decisions were executed.
What's a small but mighty tool (software or otherwise) you swear by?
“Interview Master” is a small but mighty tool I swear by. I set a goal to solve at least one SQL problem every day, and it’s been over a month of consistency—some days I even solve three or four. It’s interactive and simulates a real interview experience, prompting me to explain my thought process before and after solving the problem. It keeps me sharp, accountable, and constantly improving in a practical way.
What's something you're currently learning, or unlearning, as you grow in your career?
I’m committed to learning something every single day—even if it’s just 20 focused minutes. Currently, I’m strengthening my SQL Server knowledge and working toward certifications to deepen my technical foundation.
At the same time, I’m unlearning the idea that I have to solve everything on my own. Earlier, I believed independence meant strength. Now I understand that collaboration leads to stronger, more resilient solutions—and better leadership.
You measure success by impact rather than output—how do you personally know when something you've built is "working"?
Early in my career at Accenture, I manually pulled data from servers every day, transferred it into Excel, and worked through store failure reports. It was repetitive and time-consuming, but it showed me how much effort the team spent on manual tasks. Instead of accepting it as routine, I built a UiPath automation to extract and structure the data automatically.
What began as a way to simplify my own workflow quickly became a solution adopted by the team. A process that once took hours daily became streamlined and consistent, allowing the team to focus on analysis instead of data collection.
I knew the system was truly working not just because it ran without errors—but because people relied on it. When the team began trusting it as part of their daily rhythm, that’s when I understood what impact really means.
How do you like to reset after solving a particularly knotty technical problem?
After solving a tough technical problem, I like to celebrate in small ways—usually with dessert or a comforting bowl of ramen. It’s my way of pausing, acknowledging the effort, and giving my mind a break.
I also love to dance. Sometimes I’ll just put on music and move freely—letting go with expressive gestures and high energy. Dancing helps me shift out of analytical mode and back into creativity. That reset keeps me balanced and helps me return to work refreshed, focused, and motivated.
Across enterprise and academic environments, what kinds of problems do you find most satisfying to own end-to-end?
I’m most energized by problems that sit at the intersection of data, systems, and decision-making. Whether it’s building automations in enterprise environments or creating dashboards in academic settings, I enjoy owning the full lifecycle—from understanding requirements to deployment and iteration.
End-to-end ownership is satisfying because I can see the tangible impact of my work. I love transforming complex, scattered processes into structured systems that people trust and depend on.
What does being a member of Rewriting the Code mean to you?
Being part of Rewriting the Code means growth, connection, and belonging. It’s a space where I can share my journey, learn from other ambitious women, and explore opportunities I might not have discovered on my own.
RTC reminds me that I’m not navigating this path alone. It constantly inspires me to think bigger, stay curious, and continue evolving—not just as a technologist, but as a leader.
YOU Might Also Like
View More Stories
Meet Lucille
Computer Science & Psychology , University of Wisconsin
I am rewriting the experience for women in tech.