🚀 Who I Am

DevOps Engineer at NITCO Inc. with a passion for automation, clean infrastructure, and shipping reliable systems. I spend my days building CI/CD pipelines, wrangling Kubernetes clusters, and making cloud infrastructure reproducible with code.

I believe good DevOps is invisible — systems just work, deployments don't cause anxiety, and on-call isn't a nightmare. I'm here to help open source projects get closer to that goal.

"Automate the toil. Document the wisdom. Ship with confidence."

🔭 Currently Exploring & Contributing To

If you maintain a DevOps project and have issues tagged good first issue or help wanted — I'd love a mention. Details below.

🛠️ Technical Skills Matrix

Cloud & Infrastructure

Tool / Platform	Level	Notes
EC2, S3, Lambda, IAM, CloudFormation	████████░░ Advanced	Daily use · IaC provisioning
Docker	████████░░ Advanced	Multi-stage builds · image optimization
Kubernetes	███████░░░ Proficient	Helm · Ingress · HPA · rolling deploys
Terraform	███████░░░ Proficient	Reusable modules · VPC/EC2/RDS/S3
Linux	████████░░ Advanced	Shell scripting · system tuning

CI/CD & Automation

Tool	Level	Notes
Jenkins	████████░░ Advanced	Pipeline-as-code · multibranch
GitHub Actions	████████░░ Advanced	Reusable workflows · matrix builds
GitLab CI	██████░░░░ Intermediate	Pipelines · environments · caching
Ansible	██████░░░░ Intermediate	Playbooks · roles · idempotent configs
SonarQube	███████░░░ Proficient	CI gate integration · quality profiles

Monitoring & Observability

Tool	Level	Notes
Prometheus	███████░░░ Proficient	Custom metrics · alerting rules
Grafana	███████░░░ Proficient	Dashboard design · data sources
CloudWatch	███████░░░ Proficient	Alarms · Log Insights · Lambda metrics
ELK Stack	██████░░░░ Intermediate	Log aggregation · index management

Languages & Scripting

🤝 Open Source Contributions

Building my open source track record — actively looking for my first merged PRs in cloud-native and DevOps tooling. See below for the areas I'm targeting.

🎯 Looking to Contribute In These Areas

I'm actively scanning for good first issue and help wanted labels in these domains:

Kubernetes & Cloud Native

• Controllers, operators, admission webhooks
• Helm chart improvements and schema validation
• Cluster autoscaler and resource management
• RBAC, security contexts, network policies

CI/CD Tooling

• GitHub Actions — new actions, workflow optimizations
• Jenkins plugin improvements and pipeline DSL
• Pipeline templating and reusability patterns
• Secret management and secure build patterns

Infrastructure as Code

• Terraform provider bugs, module improvements
• Ansible role fixes and idempotency issues
• CloudFormation / CDK construct contributions
• Documentation and example improvements

Monitoring & Observability

• Prometheus exporter bug fixes
• Grafana dashboard templates and plugins
• Alerting rule libraries and runbooks
• Logging pipeline optimizations

Documentation & DX

• Runbook improvements and clarity fixes
• Getting started guides for complex projects
• Inline code comments and API docs
• Architecture diagrams and example configs

💡 How I Can Help Your Project

If you maintain a DevOps or cloud-native project, here's what I bring:

🔧 Technical depth — I work daily with the same tools your project targets. I can reproduce issues, write test cases, and trace bugs through real infrastructure — not just theory.

📝 Documentation-first — Every PR I open includes updated docs, comments, and a clear description of why, not just what. Reviewers shouldn't have to guess my intent.

🧪 Test coverage — I write tests alongside code. I'll add or extend test cases for every bug fix and won't ship untested changes.

🔄 Workflow familiarity — I understand contribution etiquette: feature branches, small focused PRs, rebasing cleanly, and responding to review feedback promptly.

🕐 Responsive — I check issues and PR comments daily. I won't open a PR and disappear.

📜 Contribution Promise

When I open a PR or comment on an issue in your project, I commit to:

• ✅ Reading CONTRIBUTING.md and following project conventions before touching code
• ✅ Opening an issue or commenting before starting work on anything non-trivial
• ✅ Keeping PRs small, focused, and reviewable (one thing per PR)
• ✅ Including tests and documentation updates with every code change
• ✅ Responding to review feedback within 24–48 hours
• ✅ Rebasing or resolving conflicts — never leaving a stale PR
• ✅ Accepting that maintainers have final say — my job is to help, not override

📬 Quick Connect

I'm always open to discussions about DevOps problems, open source collaboration, or just comparing notes on Kubernetes war stories.

→ Maintainers: If you have an open issue that needs a DevOps engineer who knows CI/CD, Kubernetes, or AWS — feel free to tag me. I'm actively looking to contribute.