IT operations
Networks, identity, security, vendors, continuity, audits, data protection and the systems staff rely on. I keep today's environment running while deciding what needs to change next.
I run technology operations at Nairobi Club.
I also design and ship business software.
I'm Emmanuel. I lead IT operations, cybersecurity and systems work in Nairobi, and I stay hands-on as a software engineer. I can move from an audit finding or management paper to a network issue, data model or production bug without treating them as separate worlds.
A few systems that best show how I work: understand the operation first, get the controls right, then build something people can depend on every day.
Networks, identity, security, vendors, continuity, audits, data protection and the systems staff rely on. I keep today's environment running while deciding what needs to change next.
Internal platforms, client systems, integrations and automation. I care about permissions, failure states, audit trails and the unglamorous details that decide whether software survives contact with real operations.
That is intentional. I am most useful where infrastructure, security, software and business operations meet.
Windows Server, Active Directory, Microsoft 365, networks, endpoints, Wi-Fi, DNS and DHCP. It is the layer people rarely think about until it stops working, so I spend a lot of time making sure it does not.
Access, firewalls, endpoints, vulnerabilities, backups and recovery. I am interested in security controls that still make sense once real users, real deadlines and real operations get involved.
I build full-stack business software with TypeScript, React, Next.js, Node.js, Python, PostgreSQL and Prisma. Most of it sits close to operations: approvals, records, reporting, integrations and the workflows people use every day.
I turn technical risk into something management can actually act on: audit remediation, policies, vendor reviews, data-protection work, continuity planning and clear papers for decisions.
I map how the work really happens before I design the system around it. That includes ERP, approvals, reporting, integrations and getting teams off disconnected spreadsheets and workarounds without breaking the controls they still need.
I like owning the whole path: requirements, architecture, implementation, testing, deployment and support. If I am responsible for the result, I want to understand where it can fail and what happens after launch.
Working is the baseline. I notice the awkward form, the confusing label, the slow flow and the process that technically works but everyone hates using. If I am responsible for a system, those details are part of the job.
I like being close enough to the technology to understand the trade-offs, and close enough to the people using it to know when the design is getting in their way.
I'm open to selected software projects, consulting and the right technology leadership conversations.