Skip to content

Full-Stack Software Engineer

Engineering systems that hold up in production.

5+ years building .NET services and, more recently, cloud-native Azure and React applications, now engineering with agentic workflows.

Capabilities

  • Backend architecture

    Domain-focused services with clear boundaries, where business logic stays independent and testable.

    .NET, Clean Architecture, N-Tier architecture, CQRS, MediatR, design patterns, microservice architecture

  • Distributed processing

    Independently scalable workloads that split work into asynchronous, parallel steps.

    Azure Functions, serverless background jobs, asynchronous parallel processing, distributed-systems reasoning

  • Data and persistence

    Query-shaped data access, with explicit SQL where performance matters.

    Dapper, Microsoft SQL Server, stored procedures, SQL performance and optimization, Azure Blob Storage

  • Frontend engineering

    Maintainable, testable interfaces inside micro-frontend architectures.

    React, TypeScript, React Query, Axios, Single-SPA micro-frontends, Jest, React Testing Library

  • Quality and operations

    Software that is safe to change and explains itself in production.

    Unit and integration testing (xUnit, Moq, FluentAssertions), observability with Application Insights and Serilog

  • Engineering practice

    Deliberate trade-offs, and AI coding agents working under human review.

    System design, architectural trade-offs, AI-assisted engineering workflows

Selected Work

  1. Public project

    Content-Driven Church Website

    A bilingual site for a local church in Bitola: 2,500+ prerendered routes over a CMS and a build-validated Bible kept in git.

    • Next.js
    • React Server Components
    • Sanity CMS
    • Zod
    • Fuse.js
    • Vercel
  2. Design study

    Resilient Loan Decisioning Pipeline

    A conceptual design for an invented lender: parallel application checks, versioned decision rules, and failures that refer an application instead of declining it.

    • Azure Functions
    • Durable Functions
    • .NET
    • Application Insights
    • Serilog
  3. Design study

    CQRS Service with an Optimized Read Side

    A conceptual design for the same lender's review queue: CQRS commands, a read model shaped for filtered browsing, and a frontend that mirrors both.

    • .NET
    • MediatR
    • Dapper
    • SQL Server
    • React Query

Engineering Principles

  1. Boundaries before frameworks.

    Clear domain boundaries outlast every tool choice.

  2. Keep business rules visible.

    Rules should be easy to find, change and test.

  3. Design reads on purpose.

    Query shape and workload drive data access decisions.

  4. Debuggable by default.

    If production cannot explain itself, the design is unfinished.

  5. Autonomy needs guardrails.

    Agents can plan and build, but their output must be tested, reviewed and traceable.

  6. Design for failure.

    Assume retries and partial failures, and make operations safe to repeat.

Direction

Today
Full-Stack Software Engineer
Deepening: architecture
Clean Architecture, design patterns, software architecture
Deepening: scale
Distributed systems, large-scale systems design, performance engineering
Deepening: modern engineering practice
AI coding agents, spec-driven development, AI-assisted architecture design, keeping AI-built software secure, reviewable and reliable
Next
Senior Software Engineer
Long term
Senior Engineer and Software Architect

Contact

Let's get in touch.

Based in North Macedonia (CET/CEST)

Most people call me Kiko.