eService

Citizens, non-citizens, businesses, and organizations need one place to reach public services. eService is built as a portal over many providers: identity, service catalog, applications, notifications, and document delivery sit on a shared platform.

Public services that live only in offices or in disconnected agency sites force travel, paper, and duplicated effort. A national portal has to authenticate people reliably, route requests to the right provider, and keep application state visible.

Lead Engineer — national platform delivery.

• Worked full-stack on a national government platform using Angular, React, TypeScript, .NET / .NET Core, REST APIs, and SQL.
• Helped establish reusable frontend/backend patterns and microservices-oriented delivery across Perago public-sector systems.
• Contributed to identity-aware service flows: registration, login, service discovery, application submission, and status tracking.
• Led engineering work as part of a 10–15 person delivery organization spanning eService, eGP, and related enterprise systems.

• Many service providers behind one portal, without collapsing them into a single brittle application.
• Identity and authorization that have to work for people, businesses, and institutions.
• Keeping application tracking and document delivery trustworthy across long-running government processes.

• Angular
• React
• TypeScript
• .NET
• REST APIs
• SQL

• Shipped as a live national services portal at eservices.gov.et.

• Treat the portal as a platform: catalog, identity, applications, and provider integrations as separate concerns.
• Reuse patterns across Perago national systems rather than inventing a stack per ministry.
• Describe only what is public about the product. Internal case-management detail and private citizen data are out of scope.