Born and raised in a small town in Kerala, being a class topper came with both blessings and burdens. There were approving smiles from teachers, thoughtful gifts from parents, and congratulations from friends—sometimes tinged with quiet jealousy. Those were the blessings. The burden was the pressure that followed: relatives predicting a great future, teachers confidently declaring that this child would become a renowned scientist or achieve something equally grand. I carried both the praise and the weight for years. Now, on the eve of a new year, I can say this—I am blessed. And as a steadfast believer in God, I feel I have been guided by Him through every step of this journey.
In the town where I grew up, the future of a well-behaved child often seemed predetermined: doctor or engineer. I chose the path of engineering and, following the common trend among toppers, opted for Computer Science. Reflecting on it now, with faith as my guide, I see that each choice and every step was quietly directed by God’s plan.
Once I chose this path, I committed myself fully. I was certain about one thing: I wanted to build a strong career and work for a good company—not just for personal success, but to honor the sacrifices my parents had made. I studied Computer Science and Engineering at MEA Engineering College, Perinthalmanna, and graduated as a college topper. For me, academics were never just about marks—they were a way to move forward, earn opportunities, and shape a meaningful future. Every exam, every result felt tied to that larger goal.
Throughout college, I focused on consistency and performance. I believed that if I worked hard enough, the results would naturally follow. I cleared multiple campus recruitment processes and felt that I was finally moving toward the future I had carefully envisioned—or rather, the future that everyone around me expected me to reach.
Despite clearing several recruitments, joining letters were delayed, and timelines became uncertain. If you’re not familiar, Indian IT companies can be unpredictable: they send an offer letter, ask you to wait for the joining letter, and sometimes it never arrives—or arrives very late. I didn’t want to remain idle, caught in uncertainty. Instead, I began looking for a temporary role—something that would keep me engaged, help me learn, and give me a sense of responsibility.
That decision became a turning point in my journey.
At that point, my friend Sithara, already working at a modestly known company called ERPGulf, suggested I apply there. I did, without much thought—after all, I only wanted a stopgap role, right?. Soon, I was called by Farook, a senior who was assembling a research-focused team. He asked me to do some live coding, which I managed to do, and shortly after, he offered me the position of Research Engineer. Just a week after graduation, I found myself stepping into my first professional role. Looking back, I owe a lot to Sithara, who pushed me into those untested waters.
I joined as a Research Engineer, and very quickly realized that this role would challenge me in ways college never did. There were no predefined answers, no textbooks to rely on, and no marks to tell you how well you were doing. There was only responsibility — and the expectation that you would figure things out. Being a quick learner, I adapted fast, and this job helped me grow even more than I had imagined. Throughout this phase, Farook’s guidance played a crucial role. He didn’t just assign tasks; he encouraged thinking, patience, and ownership, even when the answers were not obvious.
One of the first major projects I was introduced to was ZATCA, Saudi Arabia’s e-invoicing initiative. Until then, I had never imagined working on systems connected to national regulations or government mandates. It felt intimidating from the start.
The learning curve was steep. There were rules that could not be bent, requirements that changed frequently, and little room for assumptions. I made mistakes — often small, sometimes embarrassing. Things broke, validations failed, and I learned very quickly that guessing was not an option. During these moments, our team's support helped me stay grounded, reminding me that mistakes were part of learning, not a signal to stop.
That phase taught me patience
As part of the research team, I spent a lot of time reading, experimenting, testing, and reworking ideas. Much of what we built did not work on the first attempt — or even the second. But each failure forced deeper understanding.
I began researching how invoices were structured, how different systems interpreted the same data, and how ERPNext and Frappe could be adapted to meet strict external requirements. Slowly, confusion turned into clarity — not because I became smarter, but because I became more careful. Our company consistently pushed me to go deeper, question assumptions, and focus on long-term solutions rather than quick fixes.
Without any formal transition, my role began to expand. I started reviewing flows, handling edge cases, answering questions, and being involved in decision-making. At some point, I realized that people were depending on me — not just to implement, but to guide.
I found myself leading the ZATCA project, taking ownership of planning, execution, and long-term direction. What started as research slowly turned into responsibility.
We moved beyond Saudi Arabia and began working on ZIMRA (Zimbabwe) and LHDN (Malaysia) e-invoicing projects. Each country came with its own interpretations, constraints, and expectations. There was no reusable shortcut — every system demanded fresh thinking. Among these, LHDN Malaysia was particularly defining. It required balancing compliance with practicality and building solutions that businesses could realistically adopt.
Around this time, I was also given an opportunity I never expected — to speak at a Frappe webinar on LHDN Malaysian e-invoicing. What initially made me nervous was the number of people attending. Seeing such a large audience was overwhelming at first. But once I started speaking, something changed. The nervousness slowly faded, and the session turned into a friendly conversation rather than a formal presentation. I found myself becoming more confident, more comfortable, and genuinely enjoying the interaction. The questions, discussions, and shared experiences from people across different regions made it feel less like a webinar and more like a collective learning space. That experience stayed with me — not as a performance, but as a reminder that confidence often comes only after we take the first step.
During this time, I also had the chance to interact with hundreds of clients across the world. These interactions were eye-opening — understanding their challenges, answering their questions, and building solutions that actually worked. Beyond clients, I made many international friends, people I now consider part of my extended ERPGulf family.
Over time, I formally took on the role of Product Manager for multiple e-invoicing initiatives — including ZATCA, LHDN, and ZIMRA.
This shift changed how I approached work. It was no longer just about building what was asked, but about asking the right questions, anticipating challenges, and simplifying complexity wherever possible. One of the most significant outcomes of this phase was ZATCA Version 3.0 — shaped by real-world feedback, regulatory changes, and lessons learned the hard way. It wasn’t about adding more — it was about doing better.
What made this journey meaningful was not just the work, but its impact.
Because our solutions are open-source, they are used by hundreds of businesses across different countries. Occasionally, messages come in — simple notes of gratitude, success stories, or quiet appreciation. Those moments remind me why the effort matters.
ERPGulf also gave me something I value deeply — flexibility, trust, and the ability to grow without losing connection to family and friends.
Today, my journey at ERPGulf continues, with UAE and Oman e-invoicing on the horizon. Each new country feels less intimidating now — not because the work is easier, but because the foundation is stronger.
As this new year begins, I also find myself completing two years and three months at ERPGulf. That number may not sound dramatic, but when I look back, it carries more weight than I expected.
In this time, I’ve grown — not just in skills or titles, but in confidence, patience, and perspective. I’ve learned how to take responsibility, how to handle uncertainty, and how to stay steady even when things don’t go as planned.
I’m grateful — for the people who trusted me early, for the space to learn through mistakes, and for the opportunity to work on projects that quietly matter to businesses across the world. Most importantly, I’m grateful that this journey has allowed me to be closer to my parents — to be present, supportive, and more involved in their lives as they have always been in mine.
In 2025, I felt the quiet joy of seeing thousands of people—from small towns and distant cities across Saudi Arabia, Malaysia, Zimbabwe, and elsewhere—using code I had written during late nights. In 2026, I want to carry that same sense of fulfillment forward. Open-source, more than anything, brings this connection. A thumbs-up emoji, a heart, or a simple thank-you message—from someone I may never meet in a place I may never visit—can make my day. I don’t need a New Year’s resolution; I will simply continue my work… and wait for those emojis.