SS Savieo SebastianProduction Support Engineer
Resume V05 ↓

Enterprise SaaS • Production Support • Linux • Integrations • Incident Response

Available across Canada • Permanent Resident

I own complex production issues from first signal to verified recovery.

I am a Technical Support and Production Support Engineer with 6+ years across enterprise SaaS, healthcare technology, embedded systems and Python automation. I investigate Linux services, logs, databases, APIs, integrations, networks and workflow queues — then translate the evidence into clear action for customers and engineering teams.

View case studies ↗ Resume V05 PDF Contact me
Shopify Tier 2 Intelerad PACS / RIS Linux + SQL + Python 24/7 incident response
01EvidenceWhat I have investigated 02ExperienceWhere I applied it 03CasesHow I troubleshoot
6+Years across support and engineering
20+Enterprise hospital environments
250+Monitoring alerts handled monthly
100+Python automation workflows built

Production evidence

What I have actually investigated.

A practical support profile built from live enterprise systems — not keyword-only familiarity.

01 / 06

Linux & service health

From service state to post-recovery validation.

I reviewed process state, PID behaviour, application and system logs, scheduled activity, storage pressure, memory symptoms and service dependencies before deciding whether a restart, configuration change or escalation was appropriate.

  • SSH, systemctl, service/init scripts and PID analysis
  • journalctl, grep, zgrep, awk, sed, tail and structured log correlation
  • cron review, memory pressure, disk capacity, inodes and I/O investigation
  • Controlled restart and end-to-end validation rather than “restart and hope”
SSH · systemctl · journalctl · ps · grep · awk · cron · iotop
02 / 06

Database diagnostics

Capacity, connections, state and performance evidence.

I used PostgreSQL and Sybase tooling to quantify database growth, inspect workflow records and queues, investigate slow response, review connection pressure and distinguish database symptoms from storage or application issues.

  • PostgreSQL and Sybase query diagnostics
  • Database/device usage, growth limits and capacity remediation
  • Connection counts, long-running activity and transaction awareness
  • Replication and application workflow-state investigation
PostgreSQL · Sybase · SQL · transactions · queues · replication
03 / 06

Interfaces & workflow

Tracing clinical and application workflows end to end.

I supported PACS/RIS environments where a single customer symptom could involve DICOM association, image ingestion, routing, HL7 messages, modality worklists, prefetch, reporting states, audit events or destination availability.

  • DICOM association, C-STORE/C-MOVE symptoms and AE configuration
  • AutoRoute/AutoMove queue depth, age, throughput and destination checks
  • HL7 sender/gateway queues, message failures and endpoint reachability
  • Modality worklists, image ingestion, prefetch and reporting workflow states
PACS · RIS · DICOM · HL7 · C-STORE · C-MOVE · DMWL
04 / 06

Network boundaries

Separating application failure from infrastructure ownership.

I validated DNS, ports, host-to-host routing, VPN access, firewall state, certificates and source-to-destination communication so the right team received a specific, evidence-backed escalation.

  • DNS, ping, SSH, telnet/nmap and route validation
  • Source and destination port reachability
  • VPN, host firewall and “no route to host” isolation
  • TLS certificate expiry and service-facing connectivity checks
TCP/IP · DNS · nmap · telnet · iptables · TLS · VPN
05 / 06

Incident leadership

Technical ownership that stays connected to impact.

I participated in Code Blue and on-call response for healthcare production systems, balancing rapid mitigation with change risk, evidence preservation, customer communication and validation of the complete clinical workflow.

  • Impact and urgency triage in high-stakes environments
  • Incident bridges, customer updates and cross-team coordination
  • Safe mitigation, approval and maintenance-window awareness
  • Evidence-rich Engineering/SRE escalation and post-incident documentation
impact · evidence · mitigation · validation · RCA · runbooks
06 / 06

Automation mindset

Turning repeated investigation into reusable leverage.

I built 100+ Python extraction and automation workflows earlier in my career and continued using shell pipelines, repeatable checks and documented procedures to reduce manual effort and improve consistency in support operations.

  • Python scraping, validation and data-processing workflows
  • Bash/shell pipelines for logs, counts, comparisons and health checks
  • Repeatable operational checks and engineering handoff
  • Git-based workflows and technical documentation
Python · Bash · Scrapy · Selenium · Pandas · Git

Experience

Built in real production environments, not tutorials.

I have worked where downtime affects clinical teams, merchants, partners and customer operations. My role has consistently been to move from a broad symptom to defensible evidence, clear ownership and safe recovery.

Sep 2025 — Apr 2026Enterprise SaaS

Technical Support Specialist, Tier 2 Shopify

Owned merchant and partner cases involving platform integrations, authentication workflows, payment-related symptoms and API behaviour. Reproduced defects, translated findings for customers and prepared structured Engineering/Product escalations in an SLA-driven environment.

40–60 cases weeklyZendeskJiraIntegrationsDefect reproduction
Sep 2021 — Jan 2025Mission-critical healthcare

Information Systems Specialist Intelerad Medical Systems

Delivered Tier 1/2 infrastructure and backend support across 20+ hospital environments. Investigated Linux services, PostgreSQL/Sybase, storage, routing queues, DICOM/HL7 workflows, audit events, backups, replication and Code Blue incidents — resolving approximately 85% without escalation.

250+ alerts/monthLinuxPostgreSQLSybasePACS / RISOn-call
Apr 2019 — Apr 2021Embedded systems

Embedded Systems Support Engineer Calko Canada

Provided Tier 2/3 support for embedded manufacturing systems, device connectivity, wireless/IP networking, cloud backup platforms, infrastructure diagnostics and deployment validation.

Device connectivityNetworkingQA automationDeployments
Jan 2018 — Nov 2018Python engineering

Software Developer / Python Engineer Turbolab Technologies

Built 100+ reusable web-scraping and data-automation workflows using Python, Scrapy, Dragline, Selenium, XPath, Redis and Pandas, with direct client requirements gathering and documented engineering handoff.

PythonScrapySeleniumRedisPandasGit

Selected case studies

Real production stories, told without the confidential details.

These are sanitised accounts drawn from my Intelerad support work. Customer names, identifiers, internal ticket numbers and proprietary commands are intentionally excluded.

Critical incidentGo-live protected

Production recovery without direct server access

During weekend on-call coverage, a healthcare client was preparing to move from test into live production when remote access failed and the environment became unstable. I could not log in directly, so I worked through the client infrastructure engineer: guiding Linux process and resource checks, reviewing scheduled activity and isolating a legacy test-phase cron job that was consuming capacity. We backed up the configuration, disabled the problematic activity and validated that the production workflow was stable enough for the deployment to continue.

SignalRemote access failure during a time-sensitive production go-live
MethodGuided Linux diagnostics, resource correlation and cron review
OutcomeEnvironment stabilised and the client continued the deployment
DICOM routingBacklog isolated

Tracing an image-routing backlog from queue to destination

I quantified the AutoRoute queue by destination and requested date, checked how old the backlog was, reviewed sender logs and transfer speed, then validated the destination through DICOM echo and TCP port checks. I also checked receiver-side logs and storage pressure before confirming that real studies were transferring and the queue was recovering.

  • Queue depth, age and destination grouping
  • AE-title, DICOM echo and port reachability
  • Sender/receiver logs, throughput and capacity validation
Sybase capacityWrite failure prevented

Growing a production database before it exhausted capacity

A monitored Sybase database was approaching its threshold. Before changing anything, I checked the configured device limit, counted the devices already in use, confirmed that no other growth process was running and verified the current database allocation. I then used the approved growth workflow in controlled increments and rechecked database usage, device count and service health after completion.

  • Capacity and device-limit checks before action
  • Controlled database growth with operational safeguards
  • Post-change threshold, device and workflow validation
Audit workflowQueue drained

Recovering local audit events that stopped propagating

I grouped queued audit events by destination host and state in PostgreSQL, verified the Local Audit and Audit Trail service processes, checked the configured ports and tested host-to-host connectivity. After isolating retry and failed states, I used the supported reset workflow and monitored the queue until the events processed successfully.

  • PostgreSQL state and destination analysis
  • Service, process and port verification
  • Supported queue reset followed by completion checks
HL7 integrationMessage flow restored

Unblocking an HL7 File Sender queue without losing evidence

When an outbound HL7 route stopped progressing, I identified the oldest queued message, correlated it with the route-specific sender log and tested the remote endpoint. A specific message was repeatedly blocking processing, so I preserved it in a case folder, removed it from the active queue through the approved procedure and verified that later messages completed. A service restart was used only when the evidence showed it was necessary.

  • Oldest-message and route-specific log analysis
  • Remote endpoint and port reachability checks
  • Evidence preservation and post-recovery completion validation

Technical foundation

Broad enough to isolate the layer. Precise enough to escalate well.

I do not claim to be the architect of every component. I bring strong applied support depth, disciplined ownership boundaries and the ability to work effectively with Engineering, QA, Product, SRE and client infrastructure teams.

01

Linux & operations

Ubuntu, CentOS, Windows Server, SSH, systemctl, journalctl, processes, cron, filesystems, service recovery, Bash and shell pipelines.

02

Databases & data

PostgreSQL, Sybase, MySQL, SQL diagnostics, connections, capacity, transactions, workflow state and replication awareness.

03

Networking & security

TCP/IP, DNS, VPN, ports, nmap/telnet, host firewalls, routing, TLS and certificate checks.

04

Integrations

REST/API symptoms, authentication, PACS/RIS, DICOM, HL7, modality worklists, image routing and message queues.

05

Monitoring & incidents

Grafana, alert triage, performance evidence, queue age/depth, on-call, incident bridges, RCA and post-recovery validation.

06

Automation & delivery

Python, Bash, Git, Scrapy, Selenium, Pandas, Zendesk, Jira, ServiceNow, Confluence, runbooks and escalation notes.

How I work

Calm under pressure. Practical with complexity.

I do not just close tickets. I reproduce the problem, preserve evidence, isolate the failing layer, choose the lowest-risk action, validate the full workflow and document what the next person needs to know.

  1. 01Scope impact
  2. 02Correlate evidence
  3. 03Isolate layer
  4. 04Recover safely
  5. 05Verify workflow
  6. 06Document & prevent

Best-fit opportunities

Where I can contribute quickly.

Enterprise Technical Support Engineer Application Support Engineer Production Support Engineer / Analyst Integration or Solutions Support Healthcare Technical Support Customer Success Engineer

Beyond the terminal

The same discipline, curiosity and hands-on mindset continue after work.

I value consistency, continuous learning and understanding how things work — whether the system is a production platform, a training programme or a car in the garage.

01

Strength training & bodybuilding

Progressive training has taught me patience, measurable improvement and the value of showing up consistently even when results take time.

02

Books & perspective

I enjoy practical books that challenge habits and assumptions, including Atomic Habits and The Subtle Art of Not Giving a F*ck.

03

JDM and sports cars

I enjoy diagnosing, maintaining and improving cars. It is another form of systems thinking: understand the symptom, isolate the component and verify the fix.

Let’s talk

Need someone who can own the customer conversation and still go deep into the system?

I am based in Edmonton and open to remote or hybrid opportunities across Canada.

Email Savieo ↗ LinkedIn GitHub Resume V05 DOCX