Why this portfolio exists
This site is meant to show practical engineering judgment, technical range, and the kinds of systems work I am already doing across employer environments and independent projects.
Software engineer focused on systems, infrastructure, automation, and durable delivery
Gabriel Jaramillo — software engineer building systems that stay understandable, reliable, and useful.
I build across backend, cloud, automation, and modern web systems with a strong bias toward maintainability, operational clarity, and real-world execution. This portfolio highlights employer experience, shipped projects, and the engineering patterns behind them.
Common surfaces in my work
- Linux
- AWS
- Terraform
- GitHub Actions
Perspective
I am most interested in work where engineering quality is measured not just by feature delivery, but by how understandable, testable, and maintainable the resulting system becomes.
What I optimize for
Clarity, maintainability, safe delivery, and repeatable workflows. I generally prefer durable systems over clever one-off implementations.
What I focus on
Systems-minded software engineering
Experience across legacy and greenfield systems with a bias toward maintainability, operational clarity, and dependable delivery.
Infrastructure and automation
Hands-on work with Linux environments, CI/CD, AWS, Terraform, containerized delivery, and operational workflows that reduce friction over time.
Practical execution in real environments
Comfortable moving between development, testing, documentation, debugging, and customer-facing coordination when the work requires it.
Experience snapshot
My background spans defense and federal delivery environments, Linux-heavy systems work, and independent projects built with a strong operations mindset.
Accenture Federal Services
Working in a small, high-output team across development, testing, system configuration, documentation, end-user training, and secure deployment in Red Hat 9 environments.
Northrop Grumman
Contributed to a large legacy C++ codebase, built test coverage with Google Test, led Agile events, and delivered a design improvement adopted across multiple teams.
Independent build work
Built and deployed production-oriented web systems and automation workflows spanning static sites, full-stack applications, infrastructure as code, and agent-assisted operations.
Technical strengths behind the work
Selected projects
View all projects →
LogisWare
An engineering platform and web surface that combines agentic workflows, reusable site patterns, and a scalable foundation for serving multiple client implementations.
- Next.js
- TypeScript
- AWS
- CloudFront
- Terraform
- GitHub Actions
Patient Monitoring App
A patient monitoring system built to support secure access, real-world workflows, and production-oriented deployment patterns.
- Flask
- MongoDB
- Docker
- Terraform
- AWS
- GitHub Actions
Agentic Engineering Workflow
An applied workflow system showing how I am already using AI agents in daily engineering work as a productivity multiplier across repo operations, issue handling, workflow troubleshooting, and delivery support.
- OpenClaw
- Node.js
- GitHub Apps
- Automation
- Discord
- Agentic AI
How I approach engineering work
I tend to do my best work where careful implementation, debugging discipline, and long-term maintainability matter as much as shipping features.
1. Understand the system first
I prefer reading the existing system carefully, identifying constraints, and understanding how the parts fit together before making high-impact changes.
2. Keep solutions reviewable
I value bounded changes, clear reasoning, and maintainable implementations over cleverness that makes future work harder.
3. Build for reuse and operations
Whether it is application code, infrastructure, or automation, I look for patterns that reduce friction and improve repeatability over time.
What this portfolio emphasizes
- You want to see engineering work grounded in real systems rather than only design mockups
- You care about Linux, backend, cloud, automation, or operational discipline
- You want project examples that connect technical decisions to maintainability and delivery
- You are evaluating experience across both employer environments and independent shipped work
If you are evaluating me for a software engineering role, the best next step is to review the project work and background pages for a clearer picture of how I think and build.
Contact Gabriel