Backend Engineering
Designing scalable APIs and services using Go.
I'm Phil Aturo, a Software Engineer with a growing focus on backend engineering, distributed systems, infrastructure engineering, and DevSecOps.
My engineering journey is driven by curiosity, practical problem-solving, and a desire to build software that continues to perform reliably under real-world conditions.
Rather than viewing software as isolated applications, I enjoy thinking about the systems behind them—the infrastructure, communication, security, and architecture that allow complex platforms to operate reliably at scale.
My transition into software engineering has been shaped by continuous learning and hands-on project development.
Through intensive project-based training, technical research, and building real software systems, I have developed a strong appreciation for software architecture, clean engineering practices, and long-term maintainability.
Every project I build is an opportunity to deepen my understanding of how dependable software is designed, implemented, and continuously improved.
My current work centers around designing and building systems that emphasize reliability, resilience, and maintainability. Areas of active exploration include:
Designing scalable APIs and services using Go.
Exploring coordination and network resilience.
Building foundations for deployment and scaling.
Creating internal tooling and reusable systems.
Integrating security and automation lifecycles.
Researching payment and settlement reliability.
I believe reliable software is the result of thoughtful engineering rather than accidental success. Good systems should be:
Readable systems are easier to maintain.
Dependable under changing conditions.
Protected by design from the start.
Built for long-term evolution.
Technology changes rapidly, but sound engineering principles remain valuable across every generation of software.
Many of the projects featured throughout this portfolio remain under active development.
I intentionally document the engineering journey—not only the finished results. Sharing research, implementation decisions, challenges, and lessons learned creates opportunities for continuous improvement while contributing knowledge back to the engineering community.
Software engineering is a discipline of continuous learning. I actively invest time in expanding my knowledge through:
Practical implementation and real-world projects.
Reading engineering texts and research papers.
Exploring modern deployment and operations.
Studying coordination and fault tolerance.
Experimenting with new tools and protocols.
Contributing to public engineering projects.
Learning is not separate from engineering—it is part of the engineering process.
Over the coming years, I aim to contribute to software infrastructure that enables developers, businesses, and communities to build reliable digital systems. My long-term interests include:
Building resilient global platforms.
Creating tools that improve productivity.
Improving payment and settlement systems.
Scaling systems securely and efficiently.
Contributing to the global engineering community.
Guiding teams and architectural direction.
Every project within this portfolio represents a step toward that broader vision.
While technology provides the tools, engineering is ultimately about solving meaningful problems.
I value thoughtful design, collaboration, continuous improvement, and building software that creates lasting value for the people who depend on it.
The projects showcased throughout this portfolio are more than individual applications—they represent an ongoing commitment to becoming a better engineer through curiosity, discipline, and consistent execution.
There is always more to learn, more to improve, and better systems to build.