Backend-focused Software Developer building maintainable, production-minded systems with a strong emphasis on API design, database modeling, system reliability, and clean architecture.

My current core stack is Go, PostgreSQL, Docker, Kubernetes, Redis, and TypeScript. I work mostly on backend systems, but I also use TypeScript and React when full-stack ownership or frontend/backend integration is required.

I focus on backend engineering with a practical, system-oriented mindset.

My main areas of interest are:

• Clean and maintainable API design
• PostgreSQL schema design, query optimization, and transaction boundaries
• Authentication, authorization, RBAC, JWT, and secure backend workflows
• Production-readiness: logging, monitoring, error handling, configuration, and deployment awareness
• Containerized development with Docker and Docker Compose
• Kubernetes fundamentals for running backend services in distributed environments
• TypeScript-based backend and frontend development when needed

I care about building systems that are understandable, testable, observable, and easy to evolve without rewriting the whole codebase after a few months.

• Go — REST APIs, service/repository layers, concurrency fundamentals, context, error handling
• PostgreSQL — schema design, raw SQL, indexes, transactions, migrations, query performance
• Redis — caching, rate limiting, session-like workflows, distributed coordination basics
• TypeScript / Node.js — Express.js, API development, backend services, validation, authentication
• Java / Spring Boot — secondary backend experience with REST APIs and layered architecture

• Docker
• Docker Compose
• Kubernetes
• Linux CLI
• Git / GitHub
• GitHub Actions
• Environment-based configuration
• Local development workflows
• Service orchestration and containerized infrastructure

• Layered Architecture
• Clean Architecture
• API-first development
• Domain-oriented modeling
• Authentication and authorization flows
• Service boundaries
• Transaction-aware backend design
• Background jobs and async workflow basics
• Observability-oriented backend thinking

• React
• TypeScript
• React Query
• Redux Toolkit
• Tailwind CSS

I use frontend technologies mainly to build practical interfaces for backend-heavy systems and to understand end-to-end product behavior.

I am currently focused on becoming stronger in backend engineering through:

• Building Go-based backend services with PostgreSQL
• Writing more raw SQL and improving database design skills
• Learning Docker, Kubernetes, and production-oriented deployment workflows
• Improving system design and backend architecture decisions
• Strengthening observability, monitoring, and operational thinking
• Building portfolio projects that reflect real backend engineering problems

I am building DevMatch, an Upwork-style platform focused on project matching, user roles, authentication, backend workflows, and scalable API design.

The project includes:

• Token-based authentication
• Role-based authorization
• PostgreSQL-backed domain modeling
• API-first backend architecture
• TypeScript backend implementation
• React-based frontend integration
• Clean separation between domain, service, persistence, and transport layers

The goal is not only to build a working product, but to practice real backend engineering decisions around data modeling, API boundaries, authentication, authorization, and maintainability.

I am actively studying backend engineering through practical projects and selected technical resources covering:

• Go backend development
• PostgreSQL and database engineering
• Docker and Kubernetes
• REST API design
• Clean architecture and refactoring
• System design fundamentals
• Security and authentication
• Observability and production-readiness

• Email: onatarslan13@gmail.com
• Secondary: onat.arslan@btbilgi.com.tr

I build backend systems with maintainability, operational clarity, and long-term evolution in mind.