Customer-facing technical work
SaaS technical support experience
My support work combines customer context with product and front-end investigation. I have handled frontline troubleshooting, escalated technical cases, evidence preparation for engineering, reusable documentation, and HTML, CSS, and JavaScript customization across e-commerce environments.
Customer issue investigation
Clarifying expected and actual behavior, reproducing the customer journey, gathering environment details, and narrowing the affected product layer.
Frontline and escalated support
Working through customer-facing questions directly and structuring complex cases when deeper technical or engineering review is required.
Engineering handoffs
Preparing reproduction steps, scope, completed tests, technical observations, and remaining questions so another team can continue the investigation.
Documentation and implementation
Turning repeatable findings into support resources while using front-end skills to diagnose interfaces and implement appropriate customizations.
Technical capabilities
Support across product, browser, and storefront layers
Shopify and e-commerce troubleshooting
App configuration, storefront behavior, theme compatibility, variant state, campaign presentation, and merchant-facing platform constraints.
API and integration investigation
Request and response context, environment and authentication state, timestamps, error evidence, expected behavior, and escalation-ready findings.
Browser and front-end debugging
Browser DevTools, rendered DOM and computed styles, console and network evidence, responsive behavior, HTML, CSS, and JavaScript.
Escalation and technical documentation
Reproducible steps, structured case summaries, workarounds, reply material, troubleshooting checklists, and maintainable knowledge resources.
Verified environments
Platforms and support tools
My portfolio and work history reference Shopify, WordPress, BigCommerce, Yotpo UGC systems, Salesforce Service Cloud, Help Scout, live chat, browser DevTools, HTML, CSS, and JavaScript. I approach each environment through its documented behavior and the evidence available in the specific case.
Evidence-led workflow
How I troubleshoot a technical support issue
- ReproduceConfirm the customer journey, affected surface, and exact behavior.
- Gather contextRecord the browser, store, theme, app, API, account, configuration, and environment details that matter.
- IsolateCompare working and failing states and narrow the issue to the best-supported layer.
- Resolve or work aroundProvide a practical next step when support can act safely and explain its limits.
- Escalate with evidenceShare scope, reproduction, expected and actual results, completed tests, and technical findings.
- DocumentTurn reusable findings into checklists, notes, templates, or knowledge material.
Technical support case studies
Evidence hiring teams can review
These case studies explain the scenario, my role, the technology involved, the implementation or workflow decisions, and the practical value without inventing business results.
Shopify · Front-end implementation
Preorder Campaign Widgets
Variant-aware storefront widgets connect preorder pricing, savings, schedules, and fulfillment messaging to the selected product state and active campaign.
- Scenario
- Present accurate preorder context at the point of purchase.
- Role
- Front-end implementation and variant-state handling.
- Technology
- Shopify, HTML, CSS, JavaScript, theme editor.
- Value
- Campaign-driven messaging without duplicated hardcoded values.
Support operations · Knowledge system
Essential Apps Support Guide v2
A browser-based support dashboard connects investigation steps, checklists, snippets, replies, ticket references, and engineering escalation context.
- Scenario
- Organize disconnected support resources into a guided workflow.
- Role
- Workflow design, knowledge structure, and front-end implementation.
- Technology
- HTML, CSS, JavaScript, structured data files, localStorage.
- Value
- Connected investigation, customer communication, and handoff context.
Development depth: SysGuard is an independent full-stack project, not support employment. It shows how I apply architecture, permissions, testing, debugging, and agentic workflows when working closer to the code. Read the SysGuard ticketing system development case study.
Browse all technical support case studies and development projects.
Location and collaboration
Based in the Philippines and available for remote work
I’m based in Talamban, Cebu City, Cebu, Philippines and available for suitable remote Technical Support Engineer roles and relevant project work. My strongest fit is with SaaS and e-commerce teams that value clear customer communication, methodical investigation, front-end fluency, durable documentation, and evidence-rich engineering handoffs.
This page describes professional location and availability only. Opportunity fit depends on the role, responsibilities, working arrangement, and the support problems the team needs help solving.
Talamban, Cebu City
Cebu, Philippines
The marker shows the general Talamban area. It does not identify a residential address.
Open mapQuestions from hiring teams
Frequently asked questions
Are you available for remote Technical Support Engineer roles?
Yes. I’m based in the Philippines and available for suitable remote Technical Support Engineer opportunities and relevant SaaS or e-commerce support projects.
What kinds of issues do you investigate?
My verified experience includes Shopify and e-commerce behavior, API and integration context, browser and front-end issues, support escalation evidence, and technical documentation.
Which platforms have you supported?
The portfolio references Shopify, WordPress, BigCommerce, Yotpo UGC systems, Salesforce Service Cloud, Help Scout, live chat, and browser-based front-end tooling.
Where can hiring teams review your work?
Start with the technical support case studies, then review the opportunity-fit and contact page or download the current résumé.