SENIOR BACKEND / SYSTEMS / INTEGRATION ENGINEER
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.
Production systems, not demo apps.
Most of my work starts with an existing system, real users, legacy constraints, and a boundary that needs to become reliable.
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.
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.
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.
What I use to get systems shipped.
Backend
- C#
- .NET / ASP.NET
- Web APIs
- Dapper
- SSE
- Background processing
Data
- SQL Server
- Oracle
- Query optimization
- ETL / SSIS
- Data modeling
- Reporting
Cloud & Ops
- Azure App Service
- Azure Blob Storage
- Azure SQL
- Application Insights
- IIS
- Production monitoring
Integration
- Third-party APIs
- Messaging providers
- Modbus TCP
- Protocol integration
- Retry & state handling
- System boundaries
AI-assisted Delivery
- Problem framing
- Architecture & contracts
- Grill → spec → tickets
- AI-assisted implementation
- Code review
- Acceptance & verification
Three systems that show the pattern.
Professional, client & independent work →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.
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.
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.
REMOTE · TAIWAN
Backend, integration, production ownership.
I work best where software has to cross boundaries: legacy applications, databases, external providers, computation modules, devices, and the people operating them.