Adrian Urgelles

Level 3 Technical SupportBug triage · Escalations · DataLehi, Utah

Scroll to explore

About

I find the bugs that matter, prove they're real, and hand engineering something they can fix.

Based in
Lehi, Utah
Right now
L3 Support Specialist, Solo
Experience
Nearly 5 years in solar software support
Looking for
IT and Level 2/3 support roles

I've spent almost five years supporting a solar proposal platform, working my way from frontline support to the Level 3 team. Today I'm the checkpoint between support and development: every bug and feedback card that reaches L3 gets reproduced, validated and written up before it goes to the product and core dev teams.

I like turning messy data into something people can read. That's what led me to help build our team's internal reporting site, and it's why I keep a toolkit of APIs, Postman, SQL and Python close by when an issue needs a closer look.

120unvalidated bug cards cleared in about two months
25–40escalated cards validated every week
20+support teammates trained
10→3hours to build the stakeholder Top 10 deck

Featured Work

Data projects ↓
Internal web app/L3 team project

The Top 10 Site

Every cycle, stakeholders meet to review the ten issues that matter most. Building that deck by hand from ClickUp took me about ten hours the first time. Our L3 team built a web app that pulls the data, scores it and builds the presentation, and the same job now takes about three.

Co-built with the L3 team using AI-assisted development and hand-edited code. It's an internal tool, so the charts below use sample data.

What I built

  • Instant card search. Lookups return almost immediately, faster than searching in ClickUp itself.
  • Two-way ClickUp sync. Set up webhooks so the site can write back to ClickUp, not just read from it.
  • Live statuses. A status change in ClickUp shows up on the site the moment it happens.
  • Bug and feedback list views. Took them over and made sure every list pulls correctly.
  • CSV exports. Any view can be pulled into a spreadsheet in a couple of clicks.
Hours to build the Top 10 deck
Real numbers
Average days in each status, by severity
Sample data
Waiting to validateIn L3 reviewWith development

Also on the site, built across the team

Severity calculator that writes back to ClickUpPresentation builderCharts and data vizWorkload dashboardsTime and time-off trackingCard age and time-in-status metricsCustom viewsArchive list

Data Projects

More on the way
Dashboard

Coming soon

Reports and dashboards I've built in Google Sheets.

Analysis

Coming soon

Trends pulled from support and bug data, cleaned up and charted.

Exports

Coming soon

CSV work that turns raw exports into something a team can act on.

How I Work an Escalation

(01)

Reproduce

Every card starts with trying to break it myself. If I can't make it happen, development can't fix it, so I work out the exact steps, account and data it takes.

(02)

Validate

Is it current, is it real, and does it matter? I check the API responses in Postman, dig into the data and rule out user error before anything moves forward.

(03)

Escalate

Confirmed issues go to the product and core development teams with a clear write-up and a severity score, so they can pick it up without coming back with questions.

(04)

Teach

The fastest escalation is one that arrives ready. I train L1 and L2 support on what a dev-ready card looks like, and I've been training new teammates since my first month.

Experience

Solo

Solar software proposal service · 2022 to now

L3 Support Specialist

2026 – Now
  • Validate 25 to 40 escalated bug and feedback cards a week from L1 and L2 support before they reach the product and core dev teams.
  • Cleared a 120-card backlog of unvalidated bugs in about two months, the first time L3 had worked through it.
  • Handle about five extra escalations a day that come in through Slack.
  • Run trainings on the validation criteria that make an escalation ready for development.

L2 Technical Support

2024 – 2026
  • Validated customer issues escalated from L1 tickets and documented confirmed bugs and feedback as ClickUp cards for L3 review.

Senior Support Specialist

2022 – 2024
  • Started training new team members about a month after joining, and have trained more than 20 people since.

When I joined L3, there were 120 bug cards nobody had validated. About two months later, there were none.

Unvalidated bug backlog
Start and end are real; weekly shape is illustrative

Toolkit

Support

  • Escalation management
  • Bug triage and reproduction
  • Quality assurance
  • Technical training

APIs

  • REST APIs
  • Postman
  • JSON
  • Webhooks

Code and data

  • SQL
  • Python
  • JavaScript (basic)
  • CSV and data cleanup

Reporting

  • Data analysis
  • Data visualization
  • Dashboards
  • ClickUp (expert)