Interview

February 5, 2024

From Junior Engineer to Senior Innovator: Phillip-Hope Ojo’s journey building NotchHR for Africa

From Junior Engineer to Senior Innovator: Phillip-Hope Ojo’s journey building NotchHR for Africa

Phillip Hope Ojo

When Phillip Hope Ojo began his journey in software engineering, he did not imagine he would one day lead the development of one of Africa’s most reliable human resource platforms. Today, as Senior Software Engineer at NotchHR, he has helped design systems that manage thousands of employees, power payrolls, and automate HR operations across ten African countries. His story is one of vision, persistence, and impact, the kind that defines Africa’s emerging tech leadership.

In this interview, Phillip Hope talks about his technical journey, the engineering behind NotchHR, and the principles that guide his leadership across teams and innovation.

Let us start from the beginning. How did your journey into software engineering begin, and what led you to NotchHR?

My journey started with curiosity and problem-solving. I have always been fascinated by how technology can solve human challenges. As a junior engineer, I focused on mastering the basics such as clean code, architecture design, and systems thinking. That foundation helped me grow quickly because I was not just learning how to code. I was learning how technology drives business outcomes.

When the opportunity at NotchHR came, I saw it as a chance to create real impact. Human resource management is a critical part of every organization, and building a system that simplifies it across multiple African markets was both a technical and cultural challenge I wanted to take on.

NotchHR is now used across ten African countries. What was your role in building the platform’s core systems?

I led the development of the Enterprise Service Bus, which became the heart of NotchHR. It ensures seamless communication between all system modules such as payroll, performance, leave, requisitions, and recruitment. Without that ESB, departments would have operated in silos.

It was a major architectural challenge. We had to make sure data could move smoothly and securely between services without slowing down performance. Once implemented, the Enterprise Service Bus allowed us to scale the platform across multiple countries with almost zero downtime and minimal performance degradation. That was a turning point for NotchHR.

You also built the approval workflow system. What inspired that, and what impact did it have?

Every HR department struggles with bottlenecks such as waiting for approvals, manual follow-ups, and inconsistent records. The Approval Workflow System was built to fix that. It automates leave requests, expense approvals, and performance evaluations.

The result was huge. HR teams could now focus on strategic work instead of chasing paper trails. The system reduced administrative overhead by more than 40 percent and made compliance tracking far more transparent. It is one of the features I am most proud of because it simplified life for real people, not just systems.

Running such a large platform across multiple regions must require serious architectural resilience. How did you achieve that?

Absolutely. Scaling across Africa comes with challenges such as inconsistent internet connectivity, diverse business rules, and different time zones. We needed a system that could adapt to all that.

I designed a resilience architecture that combines distributed systems, proactive monitoring, and fault tolerance. If one module experiences issues, it does not affect the rest of the platform. We also implemented real-time health checks and load balancing to maintain high availability.

This architecture has allowed NotchHR to maintain uptime even during peak activity or regional disruptions. It is the foundation of the platform’s reliability today.

Let us talk about licensing and revenue. How does NotchHR sustain itself as a business model?

Our model is built on flexible licensing. We operate a subscription-based system for enterprises and offer modular packages for small and medium organizations. This makes it easier for companies across Africa to adopt the platform without large upfront costs.

We also introduced regional licensing models, which I built, and that account for local currencies and compliance differences. That flexibility helped NotchHR expand faster because businesses could onboard at their own scale. It is a perfect example of engineering meeting strategy, building a product that is both technically scalable and commercially viable.

Beyond technical systems, you have also led cross-functional engineering teams. What is your leadership philosophy?

Leadership in tech is not about titles. It is about creating environments where innovation thrives. At NotchHR, I focus on mentorship, collaboration, and ownership. Every engineer is encouraged to propose solutions, not just write code.

I have led teams that worked across backend, frontend, and infrastructure. My approach is always people-first: build trust, clarify the mission, and let creativity take the lead. That is how we have consistently delivered complex projects without burnout.

I also emphasize integrating new technologies such as AI-assisted tools to improve system performance and decision-making for HR teams. Innovation is only sustainable when people feel empowered to explore new ideas.

What is the bigger picture for NotchHR and for you as an engineer?

For NotchHR, the goal is to keep driving digital transformation in African HR. We are integrating predictive analytics, smarter payroll automation, and employee engagement tools to make HR management more human and data-driven at the same time.

Personally, I want to keep solving large-scale problems that improve organizational life across the continent. Africa’s tech landscape is maturing fast, and there is a growing need for platforms that understand local realities while matching global standards.

Finally, what advice do you have for young engineers looking to follow a similar path?

Think in decades but execute in weeks. Focus on mastering the fundamentals such as code quality, architecture, and communication because that is what builds trust and longevity.

Also, stay curious. Technology changes fast, but curiosity keeps you relevant. And always connect your technical work to real business impact. That is how you grow from being a coder to becoming a true innovator.