Experience / Engineering
A continuous engineering practice across changing stacks.
This is not a list of technologies ranked by confidence. It is the shape of the problems I have worked on and the engineering concerns that carried from one generation of tools into the next.
- Enterprise applications
Oracle / PL/SQL / Forms / Reports
Business applications built around relational data, stored procedures, transactional correctness, reporting and long-lived operational workflows. This remains relevant experience: mature systems teach hard lessons about data integrity, backward compatibility, production constraints and change over time.
- Backend systems
Python / APIs / distributed services
Service boundaries add a different class of failure to application work. My focus expanded to API design, asynchronous and event-driven systems, Kafka, performance, consistency, observability, deployment and debugging behavior that only appears when multiple components interact.
- Product engineering
TypeScript / Node.js / SQL / containers
End-to-end product work means architecture cannot stop at the service layer. Data models, application flows, interfaces, infrastructure, security, telemetry and delivery decisions all affect the same product.
- Operations & delivery
Linux / Docker / AWS / observability
Production engineering includes the environment around the application: containers, Linux, deployment, monitoring, metrics and logs. Prometheus, Grafana and ELK-style workflows are part of making systems diagnosable rather than treating production as a black box.
- Current direction
Architecture, systems thinking and AI-assisted development
I use modern AI tooling as part of engineering work while keeping architecture, verification, constraints and ownership explicit. The useful question is not whether AI wrote a line of code; it is whether the resulting system is understandable, testable and fit for the real problem.
Selected professional history
The timeline behind the stack.
Selected roles rather than an exhaustive résumé. The point is continuity: enterprise software, technical leadership, backend/product engineering and creative technology all belong to the same working history.
- 02/2025 — 05/2025
Kazan A.Ş. / Team Leader
Technical leadership and software delivery in a team-lead role.
- 09/2022 — 06/2024
Bilgi Grubu / Team Leader
Team leadership across software engineering and delivery.
- 09/2018 — 09/2022
Contractor / Lead Developer
Lead-development work across backend and product delivery.
- 2013 — 2018
Agito Software & Consulting / Senior PL/SQL Developer
Senior Oracle / PL/SQL engineering across two periods: 09/2013–08/2015 and 08/2016–09/2018.
- 2008 — 2009
Fikr-i Harika / Creative & Technology Manager
A role where technology and creative production explicitly met — useful context for why this portfolio does not separate engineering and creative work into different identities.
- 2005 — 2011
Probel Software / Software Developer
Progressed from junior through mid-level to senior software development across two periods: 01/2005–05/2008 and 11/2009–11/2011.
Capabilities / Evidence-led