Open to network, NOC and automation roles

I keep enterprise networks online and automate the work around every alert.

Network and Security Engineer with 4+ years in 24/7 NetSOC and NOC operations: firewalls, SD-WAN, monitoring and VoIP. I also build workflows that send each alert, email and client request to the right person and the right channel.

4+ yrsNetSOC & NOC
24/7Operations
50+Tools used
3Automation builds
netops / event-router · live demo

Featured projects

Tools I built for network teams.

Each one starts from a problem I deal with in network operations and ends in a working tool. Swipe or use the arrows to see each screen.

01Web app · Next.js on Vercel

Network Alert Monitor

Find BGP flaps, high CPU and down interfaces before a ticket is opened.

A NOC dashboard that polls six simulated routers, switches and firewalls every five seconds. It runs three alert rules on each poll and sends each alert to Slack and email, then sends a resolved message when the problem clears.

  • Each alert is sent once, so the channel isn't flooded
  • CPU alerts wait for 3 high readings in a row, so a single spike doesn't page anyone
  • 77 unit tests cover thresholds, the alert lifecycle and Slack timeouts
Next.jsTypeScriptSlack webhooksVitestVercel

Product screens

01 / 04
4 / 6 healthy1 warning · 1 critical · polling every 5s
core-rtr-01BGP flap · AS65002
core-sw-01HQ · Cisco
fw-edge-01HQ · Palo Alto
br1-rtr-01CPU 83%
br1-sw-01Branch 1
br2-rtr-01Branch 2
Fleet healthDonut, CPU rings, per-device state
# noc-alerts Slack
NA
Network Alerts4:12 PM

🔴 CRITICAL · BGP flap on core-rtr-01
Peer 10.0.0.2 (AS65002) changed state 3 times in 60s.
Site: HQ · Suggested: check the peer link and interface errors.

NA
Network Alerts4:14 PM

✅ RESOLVED · BGP flap on core-rtr-01
The session has been stable for 60s. On-call can stand down.

Slack alertsOne alert, then one resolved message
Inbox Email alert preview
[CRITICAL] BGP flap · core-rtr-01 (HQ)Peer 10.0.0.2 · 3 transitions in 60s · next step inside
4:12
[WARNING] High CPU · br1-rtr-0186% for 3 consecutive polls
4:09
[RESOLVED] Interface down · core-sw-01 Gi1/0/24Link restored after 2m 10s
3:58
[RESOLVED] High CPU · fw-edge-01Back under the 85% threshold
3:41
Email alertsOutlook-style alert emails
$ npm test

 ✓ tests/rules.test.ts      (cpu 85% no alert · 86% alerts)
 ✓ tests/alerts.test.ts     (open · dedupe · resolve)
 ✓ tests/slack.test.ts      (3s timeout · errors caught)
 ✓ tests/validate.test.ts   (signed state)
 ✓ tests/email.test.ts      (alert email format)

 Test Files  all passed
      Tests  77 passed (77)
Test suiteThreshold edges are tested
02Automation · Make.com

ISP Email Router

ISP emails get a label and a log row, and outages go to Slack.

Emails from PLDT, Globe, Converge and Sky arrive mixed in one inbox. This Make scenario reads each one, labels it by ISP and type (Outage, Maintenance, Billing, Other), and adds a row to a color-coded Google Sheet. It posts outages to #critical-alerts in Slack.

  • Keyword rules only, with no AI step, so every decision can be explained
  • Gmail labels are set by label ID, so renaming a label doesn't break the flow
  • Tested with four ISPs and four email types
Make.comGmailGoogle SheetsSlackApps Script

Product screens

01 / 04
1
Gmail · Watch emailsin:inbox (pldt OR globe OR converge OR sky)
1 bundle
2
Tools · Set ISP + typekeyword rules on subject and sender
1 bundle
3
Filter · ISP email onlyisp exists
pass
4
Gmail · Update labelsISP/PLDT + ISP-Type/Outage
1 bundle
5
Sheets · Add a rowISP Mail Log › Log
1 bundle
6
Filter → Slacktype = Outage → #critical-alerts
sent
Make scenario8 modules, run once per batch
Inbox Gmail labels applied
PLDT Enterprise · Service outage, Makati HQ circuitISP/PLDTISP-Type/Outage
4:48
Globe Business · Fiber disruption in your areaISP/GlobeISP-Type/Outage
3:10
PLDT · Scheduled network maintenanceISP/PLDTISP-Type/Maintenance
3:08
Converge · Your monthly statementISP/ConvergeISP-Type/Billing
3:06
GmailLabeled by ISP and type
ReceivedISPTypeSubject
11-10 16:48PLDTOutageService outage, Makati HQ
11-10 15:10GlobeOutageFiber disruption
11-10 15:08PLDTMaintenanceScheduled maintenance
11-10 15:06ConvergeBillingMonthly statement
11-10 15:04SkyOtherPlan upgrade offer
Google Sheets logColor-coded by type
# critical-alerts Slack
MK
Make4:48 PM

🚨 ISP OUTAGE: PLDT
Subject: PLDT Enterprise · Service outage affecting your Makati HQ circuit
Received: Nov 10, 4:48 PM

We are aware of a service outage… Ticket no.: PLDT-INC-0458

Open email in Gmail

Slack #critical-alertsOutages only
03Automation · Zapier

MSP Client Onboarding

One form submission sets up a new client in four places.

When an MSP signs a new client, someone usually copies the same details into a folder, a tracker, a welcome email and a team message. This Zap does all four as soon as the intake form is submitted, and it gives every client an ID like CL-20261108-1944.

  • Creates a Drive folder, a tracker row, a welcome email and a Slack post
  • Uses folder and channel IDs, so renaming them doesn't break the Zap
  • Fixed the phone-number and timezone errors in the sheet; 3 test clients ran end to end
ZapierGoogle FormsDriveSheetsGmailSlack

Product screens

01 / 04
New Client Onboarding Google Form
Company name
Northpoint Logistics
Contact name
Ana Reyes
Network devices
25
Plan
Standard
Contact email
ana@northpoint.example
Go-live date
2026-11-20
Intake formValidated fields
1
Google Forms · New responsetrigger
✓
2
Formatter · Client IDCL-YYYYMMDD-HHmm (Asia/Manila)
✓
3
Drive · Create folderClients/Northpoint Logistics (CL-…)
✓
4
Sheets · Add rowMSP Clients › Status = Onboarding
✓
5
Gmail · Welcome emailClient ID, plan, 5 onboarding steps
✓
6
Slack · Team post#client-onboarding
✓
The Zap6 steps
Client IDCompanyPlanStatus
CL-20261108-2015Northpoint LogisticsStandardOnboarding
CL-20261108-1958Bayside Dental ClinicBasicOnboarding
CL-20261108-1944Acme NetworksPremiumOnboarding
Client trackerFolder link and checklist on each row
# client-onboarding Slack
OB
NetOps Onboarding Bot8:15 PM

🎉 New client: Northpoint Logistics
Client ID: CL-20261108-2015 · Plan: Standard
Devices: 25 · Go-live: Nov 20

Open client folder

Slack postThe team is told right away

Automation blueprints

See each workflow, one step at a time.

Pick a workflow and press Run demo to highlight each step in order. Select a step to see what it does. This is a visual walkthrough only; it doesn't connect to any live system.

ready

Select a step

Each step shows the tool it uses and what it passes to the next step.

Run log appears here.

Platforms & technologies

Tools I use.

The platforms I use for network security, monitoring, voice and day-to-day operations, and the automation tools that connect them.

✦ marks the automation and integration tools I use to connect systems and people.

Experience

7+ years in operations.

From alert monitoring and VoIP provisioning to firewall and SD-WAN work for enterprise clients.

TTECFeb 2022 – Present
Manila

Network and Security Engineer (NetSOC)

  • Monitor network, voice and platform infrastructure for TTEC clients across cloud and on-premises environments.
  • Manage firewall and SD-WAN environments with Palo Alto Panorama, Cisco ACI, Meraki and Prisma SASE, and support disaster recovery.
  • Triage service alerts, find the root cause, and document incidents and resolutions in the ticketing system.
Palo AltoPrisma SASESplunkDatadogF5
NICE CXoneJun 2021 – Jan 2022
Manila

Technical Support Engineer

  • Administered NICE inContact recording servers and managed cloud connectivity to CXone.
  • Troubleshot recording integrations across Avaya, Cisco UCCE/UCX and Mitel, using SQL queries and service logs.
  • Generated and bound SSL certificates; worked with Cisco and Avaya engineers on CUCM and AES configurations.
NICE CXoneSQLAvayaSSL
Bold Business (FTR911)Mar 2021 – Apr 2021
Project-based

Network Operations Center Engineer

  • Monitored network health for PSAP/911 public-safety clients.
  • Identified PALI, ANI, trunk, circuit and CPE alarms and outages, and dispatched Level 2 engineers through Remedy and Netcool.
NetcoolRemedyCitrixAWS WorkSpaces
Eloyalty (TTEC Digital)Apr 2019 – Apr 2021

Level 1 Cisco VoIP Engineer · Alerts Monitoring Technician

  • Handled MACD requests: provisioned phones, user profiles, route points and voicemail in CUCM and Cisco Unity.
  • Configured UCCE agent accounts and supported call recording with Calabrio and Verint.
  • Monitored events in ScienceLogic EM7 and ran incidents in ServiceNow, escalating critical alerts to Level 2.
CUCMUCCEScienceLogicServiceNow

Contact

Let's talk about your network and your alerts.

Based in Quezon City, Philippines, and available for remote work. Email me about NOC/NetSOC roles, network operations, or automating your alert and onboarding workflows.