Engineering is not just writing code. It is solving problems.
I am a Full Stack Software Engineer with 4+ years of experience designing, architecting, and delivering enterprise-grade software. Here is my story — and why I do what I do.
My story
I am Abenezer Sileshi Bekele, a Full Stack Software Engineer based in Addis Ababa, Ethiopia. Over the past 4+ Years, I have designed and built enterprise applications, SaaS platforms, AI-powered systems, and government-affiliated software — each one solving a real business problem, not just a coding exercise.
My work spans the full stack: from database design and system architecture to frontend performance and deployment automation. I have built platforms that handle 500+ concurrent exam sessions, AI voice agents that automate 80% of routine clinic calls, and multi-tenant SaaS platforms that serve 20+ pharmacies with zero data leaks.
I do not build CRUD applications. I solve business problems through software. I design scalable systems, care deeply about maintainability, focus on performance, and enjoy the difficult engineering challenges that come with building software that businesses depend on.
I am available for remote international engineering roles and work with teams across time zones. I communicate technical decisions clearly, lead complex projects from architecture to deployment, and build software that lasts.
At a glance
- Name
- Abenezer Sileshi Bekele
- Role
- Full Stack Software Engineer
- Location
- Addis Ababa, Ethiopia
- Experience
- 4+ Years
- Availability
- Remote, International
Security
Non-negotiable
Performance
Measured, not assumed
Maintainability
Built for the next developer
User-centered
Software serves people
My engineering philosophy
These principles guide every decision I make — from architecture to code to deployment.
Why I became an engineer
I became an engineer because I believe software is the most powerful tool we have for solving real problems at scale. I wanted to build things that matter — systems that businesses depend on, that people use every day, and that make work more efficient and more human.
How I approach problem solving
I start with the problem, not the technology. I ask: who is affected, what is broken, and what would success look like? Only then do I choose the tools. The best architecture is the one that solves the problem simply and can evolve as the problem evolves.
Why architecture matters
Architecture is the difference between a system that scales and a system that breaks. I design boundaries early, separate concerns explicitly, and make sure every module can be understood, tested, and changed independently.
How I collaborate with teams
I write code for the next developer, not for myself. I document decisions, explain trade-offs, and make sure my teammates can understand and extend what I build. Good software is a team sport.
What I enjoy building
I enjoy building systems that have real consequences — platforms where security, reliability, and performance are not optional. Enterprise software, SaaS platforms, AI-powered systems, and anything where the engineering decisions directly affect business outcomes.
My engineering philosophy
Software should be scalable, secure, maintainable, and user-centered. I write clean code, design for change, test what matters, and ship production-ready software. I do not build demos — I build systems that run in production and that businesses depend on.