KCWANG

SENIOR BACKEND · SYSTEMS · INTEGRATION

Kevin Wang

I turn fragmented systems into reliable production workflows.

Backend, systems, and integration engineer with 13+ years of experience taking over real production systems, defining boundaries between services and vendors, and turning messy workflows into reliable software.

Taiwan · UTC+8 · Remote
01 13+ Years building production systems
02 1M+ Push notifications / day
03 50K+ SMS deliveries / day
04 5 SMS provider integrations

THE PATTERN

“The technology changes. The job stays the same: find the boundary where reality gets messy, make the contract explicit, and make failure recoverable.”
Production ownershipIntegration boundariesReliabilityIncremental modernization
01 / PROFESSIONAL EXPERIENCE

Production systems,
not demo apps.

Existing users. Existing constraints. Systems that cannot simply stop while they are being improved.

2020 — PresentRemote

Senior Backend / Systems Engineer

Official title · Blockchain Systems Development Engineer

Quande Information Technology

Own and evolve existing production systems spanning customer operations, messaging, integrations, data, deployment, and reliability.

  • Operate a notification platform delivering 1M+ push notifications and 50K+ SMS messages per day across five SMS providers.
  • Own a customer-operations platform deployed to Azure Web App; changed a blocking 12-tab user view into independently loaded and refreshable tabs.
  • Use application-side revalidation plus downstream state checks for operations that mutate external system state.
  • Maintain C#/.NET and SQL Server services across Azure and IIS, with production monitoring through Application Insights.
C#.NETSQL ServerAzure Web AppDapperIISApplication Insights
01
Previous role · ~5 yearsTaiwan

Software Engineer

Education Budget & Accounting Platform

Maintained and evolved a long-lived budgeting and accounting platform serving 3,300+ schools and roughly 15,000 users.

  • Evolved .NET Framework / SQL Server production workflows while preserving compatibility with older fiscal-year data.
  • Introduced new fields incrementally rather than forcing incompatible schema assumptions onto historical records.
  • Moved shared summary work to overnight processing when many schools needed the same calculations in a short decision window.
.NET FrameworkSQL ServerIISReportingLegacy evolution
02
Earlier careerTaiwan

Software Engineer

Duty-free Retail Incentive Platform

Designed the ETL pipeline and co-designed the backend calculation model for a multi-store incentive-calculation system.

  • Designed Oracle-to-SQL Server ETL flows for roughly 6–7 high-volume retail stores.
  • Handled incomplete records, encoding problems, invalid characters, failed records, and orphan data with explicit classification and replay paths.
  • Automated complex incentive calculations so HR could focus on validating results instead of manually cross-referencing reports.
OracleSQL ServerSSISStored ProceduresETL
03
02 / ENGINEERING RANGE

Deep where it matters.
Broad at the boundaries.

Current-stack strength in .NET and SQL, with enough systems range to own the integration surface around them.

01

Backend

  • C#
  • .NET / ASP.NET
  • Web APIs
  • Dapper
  • SSE
  • Background processing
02

Data

  • SQL Server
  • Oracle
  • Query optimization
  • ETL / SSIS
  • Data modeling
  • Reporting
03

Cloud & Ops

  • Azure App Service
  • Azure Blob Storage
  • Azure SQL
  • Application Insights
  • IIS
  • Production monitoring
04

Integration

  • Third-party APIs
  • Messaging providers
  • Modbus TCP
  • Protocol integration
  • Retry & state handling
  • System boundaries
05

AI-assisted Delivery

  • Problem framing
  • Architecture & contracts
  • Grill → spec → tickets
  • AI-assisted implementation
  • Code review
  • Acceptance & verification
03 / SELECTED EVIDENCE

Three systems.
One engineering pattern.

View the full evidence archive ↗
01
Owned Product · Production · Dozens of users

PatchGrid

Live-event file delivery and coordination

Born from a real live-production problem: teams exchanging console and show files through filenames, dates, and version suffixes with no clear authoritative copy. PatchGrid is now a production SaaS used by dozens of users.

Production SaaS.NETReactLive audio
Case study ↗
02
Client Delivery · Delivered system

MSAR V2 / ITRI

Computation orchestration across multiple teams

An integration layer connecting frontend requests, DB APIs, frequently changing computation modules, result artifacts, and persistence. The architecture isolates team-owned code behind explicit execution boundaries.

IntegrationOrchestrationPythonOperational tooling
Case study ↗
03
Professional · Production

Messaging Platform

High-volume multi-provider notification delivery

Production push and SMS delivery handling 1M+ push notifications and 50K+ SMS messages per day, with five SMS providers, retry behavior, delivery-state tracking, and operational troubleshooting.

C#SMSPushIntegrationReliability
Case study ↗

TAIWAN · UTC+8 · REMOTE

Bring me the system
nobody wants to touch.

I work best where software crosses boundaries: long-lived applications, databases, external providers, computation modules, devices, and the people operating them.