Open to roles where I can own incidents and ship fixes.

I am currently looking for roles in Technical Support Engineering, Software Engineering, and Infrastructure Automation. If you need someone who can move between customer issues and code changes, let’s talk.

What I am interested in

• High-Availability SaaS: Platforms that require 99.9% uptime and durable architecture. I like environments where performance and scalability are taken seriously, with clear SLOs and a real on-call rotation.
• Infrastructure & Automation: Building the "invisible" layer that keeps companies running—CI/CD pipelines, Docker containerization, and automated server health checks. I enjoy automating the repetitive steps that slow incident response.
• Tier 2/3 Technical Support: Roles that require code-level investigation. I enjoy tricky tickets, reading the logs, and shipping the patch that prevents repeat incidents.
• AI & Data Pipelines: Supporting the infrastructure that powers AI tools and data platforms, ensuring that models are served reliably and efficiently.

What to expect when working with me

• I Don’t Just Escalate, I Fix: I reproduce the bug, isolate the root cause, and draft the fix so engineering can ship quickly.
• I Translate "Tech" to "Human": I can explain a database deadlock to a non-technical stakeholder without confusion. I bridge the gap between frustrated users and busy developers.
• I Document Everything: If a problem comes up twice, I write a guide the first time. I build knowledge bases and short runbooks that help teams resolve issues faster.
• I Automate the Repeats: If a task keeps showing up, I script it or add a check—small tooling and CI/CD improvements that speed response and reduce errors.
• I Stay Calm When It Breaks: Production outages do not panic me. I rely on logs, metrics, and a systematic debugging process to restore service quickly.

Lesson learned: the fastest resolution usually comes from a clear owner and a shared incident timeline.