2007 · 2014
Foundations
- Işık University · Bachelor's degree, Computer Engineering, 2007 to 2014.
- Algorithms, data structures, operating systems, databases, networks: the layer everything else runs on.
F1 HELP F10 NEXT
MEHMET BERKAY AYAZ
Software engineer, full stack developer, technical lead, system builder.
enter system> SELECT * FROM identity WHERE access = 'visitor';
IDENTITY
- NAME
- MEHMET BERKAY AYAZ
- LOCATION
- BRITISH COLUMBIA, CANADA
- DOMAIN
- SOFTWARE ENGINEERING
- CURRENT ROLE
- DEVELOPMENT TEAM LEAD · HEALTHCARE TECHNOLOGY
- SPECIALIZATION
- .NET / C#WEB SYSTEMSCLOUD ARCHITECTURETECHNICAL LEADERSHIP
- IN SERVICE SINCE
- 2017
1 row returned
I build systems that sit between people, data and real-world operations.
I started close to the device, writing native Android and iOS apps, and moved steadily deeper: full stack web engineering, enterprise systems, architecture, and now leading the team that builds them.
Career memory
Stored in the order it happened. The machine was upgraded along the way, and so was the engineer.
2016 · 2017
Mobile
- Lambton College · post-graduate diploma, Mobile Application Design and Development, 2016 to 2017.
- Native Android in Java, native iOS in Swift, and the PHP and MySQL behind them.
- Certifications · RxSwift, Swift 3, server-side Swift with Vapor, iOS HomeKit, Sketch mobile design.
2017 · 2018
Apps in the field
- Beacontree · One-Touch Lock-Out, NFC lock-out and tag-out for industrial equipment.
- MovingPlanIT · a tennis CRM for Android, on secured PHP REST APIs.
- Mühendis Beyinler · a tech news reader, downloaded more than 10,000 times on Google Play.
- OpenXC Remote · vehicle data over Bluetooth, relayed with Firebase Cloud Messaging.
- Restaurant POS · a point of sale that helps new waiters serve better.
- mail + parcel/
- logistics/
- care mgmt/
- integrations/
- monitoring/
2019 · 2024
Enterprise web
WCG: The IT Exchange · software developer and consultant
Mail, parcel and logistics systems, a care management system, and internal server monitoring. Server side in C#, data in SQL Server, documents through XSLT, integrations through REST, and client interviews to learn what the software was really for.
C# · ASP.NET MVC · .NET Framework · jQuery · SQL Server · XSLT · REST
2024 · 2026
Healthcare, developer to lead
Provincial Health Services Authority
Software developer, 2024 to 2025. Web applications joining AngularJS and Angular front ends to .NET on the server.
Technical lead, 2025 to 2026. Led the developers: code reviews, mentoring, schema design, sprint and release management in Jira and Azure DevOps, and the translation between product owners, analysts, QA and code.
.NET · Angular · AngularJS · SQL Server · Jira · Azure DevOps
2026 · now
Development team lead
SWITCH BC · healthcare safety, wellbeing and collaboration
Technical strategy and delivery for enterprise applications: ASP.NET and Angular architecture, SQL Server schemas, CI/CD in Azure DevOps, and a team to mentor. The job is now the system and the team that builds it.
next
Direction
- plan cloud-native architecture on Azure
- build developer tooling and automation
- pair AI-assisted and agentic development, MCP integrations
- guard application security, by default
Interests in progress, not claims.
graph.system
The career, compiled as a system.
compiling
-
Where the systems run now.
- App Service
- Key Vault
- Entra ID
- Static Web Apps
- Azure DevOps
-
The surface people actually use.
- Angular
- AngularJS
- TypeScript
- JavaScript
- Knockout
- jQuery
-
The primary stack, from .NET Framework to modern .NET.
- ASP.NET Core
- Web API
- EF Core
- Dapper
- ASP.NET MVC
- Blazor
-
The contract between the pieces.
- REST
- JSON and XML
- Versioning
- Integrations
-
Where the truth lives.
- Schema design
- T-SQL
- Stored procedures
- Query tuning
-
What all of it is for.
- Logistics and parcel
- Healthcare technology
- Care management
- Carrier integrations
- Reporting
-
How the pieces fit, and why.
- REST APIs
- Authentication
- SSO
- Caching
- Background jobs
- Cloud migration
-
Built in, not bolted on.
- Application security
- OAuth and OIDC
- Secrets management
- Least privilege
-
Getting changes out safely, repeatedly.
- CI/CD
- Azure DevOps
- Git and Bitbucket
- Release management
- Jira
-
The newest layer, treated like any other dependency.
- AI-assisted development
- Agentic workflows
- MCP integrations
- Automation
-
Systems are built by teams.
- Code reviews
- Architecture decisions
- Mentoring
- Release processes
- QA and dev collaboration
-
Everything above grew out of these.
- Java
- Android
- Swift and iOS
- PHP and MySQL
- XSLT
files.cases · class: sanitized
Case files
Generalized engineering problems from real work. No employer systems, names or data, only the shape of the problem and what it taught.
CASE-01
Legacy to modern .NET, without stopping the business
Problem
Long-lived web applications where the business rules live in three places at once: C#, stored procedures and XSLT. Nobody can freeze feature work for a rewrite.
Approach
Port slice by slice. Treat the old system's behaviour as the specification and prove parity with tests before switching anything over. Keep database changes as reviewed scripts, and let CI hold the line.
What I keep from it
A migration is a sequence of small, reversible releases. The rewrite that ships all at once is the one that never ships.
CASE-02
Integration pipelines for logistics data
Problem
Carrier and partner data arrives in every format ever invented: FTP drops, CSV, XML, PDFs, APIs. It arrives late, twice, or malformed, and shipments depend on it.
Approach
One shape for every feed: fetch, parse, validate, stage, apply. Idempotent imports so a replay is harmless, background jobs with honest failure logs, and reports people can check.
What I keep from it
Integrations fail at the edges, so the edges get the most code. Make failure visible, cheap and repeatable.
CASE-03
Identity and access at the edge
Problem
Applications in a regulated environment need single sign-on, role-based access in both the SPA and the API, and secrets that never touch source control.
Approach
Let the identity provider own identity. Validate tokens at the API, authorize by policy rather than by scattered checks, keep secrets in a vault, and grant the least privilege that works.
What I keep from it
Security is an architecture decision made early, not a checklist run at the end.
CASE-04
Engineering with AI agents, with guardrails
Problem
AI coding agents are fast and confidently wrong. Used loosely they produce volume, not software.
Approach
Run them inside the same discipline as people: a written plan, one task at a time, verification before anything is called done, hooks that block unsafe actions, and a human who reviews and merges.
What I keep from it
The tools changed. The engineering did not: small steps, evidence, review.
Personal and freelance archive
| Year | Project | Built with |
|---|---|---|
| 2026 | This machine | HTML, CSS, SVG and vanilla JavaScript |
| 2018 | Restaurant point of sale | Android, Retrofit2, SugarORM |
| 2017 | Mühendis Beyinler, tech news reader | Android, RSS · more than 10,000 Google Play downloads |
| 2017 | OpenXC Remote | Java, OpenXC, Firebase Cloud Messaging |
team.protocols
How I work with teams
Review code for the next person who has to read it.
Reviews are where a team's standards actually spread. Clarity first, cleverness last.
Write the decision down.
An architecture decision nobody recorded gets argued again six months later.
Bring QA in at the start.
Testers find the unclear requirement before it becomes the bug.
Make releases boring.
Small changes, repeatable pipelines, and a rollback nobody has to invent at midnight.
Teach by building together.
Mentoring works best on real tickets, with the reasoning said out loud.
END OF RECORD.
external connection available