eGP

Public procurement has to work for government entities and for the suppliers that bid into those processes. eGP is a national system, not a departmental app: many institutions, many roles, and workflows that have to remain auditable.

Paper and fragmented digital procurement slow public buying, hide process state, and make it hard for suppliers to participate consistently. A national platform has to encode those processes without becoming a different product for every institution.

Lead Engineer — national platform delivery.

• Delivered full-stack work across Angular, React, TypeScript, .NET / .NET Core, REST APIs, and SQL.
• Helped shape reusable frontend and backend patterns so procurement workflows could be extended without a rewrite per agency.
• Worked on system design and delivery as part of a 10–15 engineer leadership scope across national Perago platforms.
• Contributed to the move from legacy AngularJS toward React on government frontend systems.

• Workflow complexity: procurement is a process with roles, stages, and documents, not a CRUD form.
• National scale: many institutions sharing a platform, with isolation and audit requirements.
• Modernizing frontend architecture while the system stayed in production use.

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

• Shipped as a live national procurement platform at egp.gov.et.

• Keep procurement rules in services behind APIs so buyer and supplier surfaces stay consistent.
• Prefer reusable platform patterns over institution-specific application forks.
• Omit internal operational detail, private procurement data, and unpublished system internals from this case study.