Skip to content
View mmtovarl's full-sized avatar
🎯
Focusing
🎯
Focusing
  • Croatia

Block or report mmtovarl

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
mmtovarl/README.md

Hi, I'm Arlen

Customer support specialist moving toward technical investigation work: L2/L3 support, application support, and SQL/data-driven troubleshooting.

About

I currently work as a Senior Customer Support Specialist at a B2B SaaS company building document scanning and PMS integrations for the hospitality industry. Before that I spent close to two decades running my own ventures, including building and operating a high-traffic e-commerce marketplace with hands-on API integration, database management, and web scraping work.

I'm not a software engineer and I don't want to be one. What I'm good at is taking a vague or broken customer report and turning it into a concrete, evidence-backed answer: what happened, why it happened, and what the data actually shows. This profile is where I practice and document that kind of investigative work.

What I'm working on

  • Building a portfolio of technical investigation write-ups using real tools (Postman, SQL, Kibana) against realistic scenarios
  • Working through SQL fundamentals and query-based problem solving from first principles
  • Learning to read logs and API behavior the way a support engineer needs to, not the way a developer does

Featured projects

Postman API Investigation Investigated a mock API for silent field acceptance, authentication enforcement gaps, and rate-limiting exposure. Framed as a real-world triage case: what a customer would report, what the API actually does, and what the fix should be.

SQL Investigation: PMS Booking Sync A synthetic property-management-system booking-sync scenario used to practice root cause analysis through SQL queries alone, no assumptions, no guessing, just what the data shows.

Kibana Log Analysis Time-series spike detection and anomaly investigation using log data, focused on identifying what changed and when.

SQL Cheat Sheet A working reference I built while learning: query execution order, NULL handling, JOIN types, aggregations, HAVING vs WHERE, subqueries, and style conventions.

Background

  • Independent e-commerce marketplace: founded and operated 2017-2022, including direct API integration work (TCGPlayer API) and a custom WooCommerce price-sync addon built to spec
  • Independent IT consultancy, 2003-2017: hardware, networking, and software support
  • SQLBolt (completed), Knight Lab SQL Murder Mystery (solved independently)
  • Google IT Support Professional Certificate, IBM Databases and SQL for Data Science with Python

Pinned Loading

  1. Support-Engineer-Portfolio Support-Engineer-Portfolio Public

    A portfolio scenario simulating investigation of a PMS booking/card-sync integration.