Miloš Živković
span 07 about parent 00

Miloš Živković

Software & Cloud Engineerfounder & owner, ProtoCode

I work on secure, compliant and scalable systems, with twelve years of experience in software and cloud engineering. Today I work with SaaS companies, startups and enterprise clients that need scale and compliance.

Portrait of Miloš Živković
role
Software & Cloud Engineer
based in
Zrenjanin, Serbia · remote only, mostly with international clients and open to clients anywhere
company
Founder and owner of ProtoCode, since January 2021
experience
12 years
works across
Cloud infrastructure, platform engineering, DevOps, distributed systems, TypeScript, Node.js, AWS and AI implementation
how I build
Agents first, with tests, CI and my review on every change
works with
SaaS companies, startups and enterprise clients
span 07.1 capabilities four areas · twelve capabilities

What I work on

Most systems need all three areas at once: software that is built well, infrastructure that runs it at a sensible cost, and the security and compliance work around both. The fourth area is how I build all of it.

Software

Node.js & TypeScriptBack-end development in Node.js and TypeScript.
AI implementationSoftware that uses AI services such as OpenAI, ElevenLabs and Deepgram.
DatabasesServerless and non-serverless: DynamoDB, MongoDB, DocumentDB, PostgreSQL, MySQL.

Cloud

Cloud architectureOn AWS or other cloud providers.
DevOps & CI/CDFully automated CI/CD; infrastructure as code with Terraform.
Cost optimisationCloud cost optimisation, including a 58% cut in monthly infrastructure costs for a SaaS platform.

Security

DevSecOpsSecure infrastructure and platforms, with vulnerability management.
Compliance readinessGetting platforms ready for an ISO/IEC 27001 or SOC 2 audit. Readiness, not audit or certification.
Reliability & recoveryReliability and disaster recovery, including regular recovery tests.

Agents-first

Context before codeArchitecture, conventions and context files come before the code.
Parallel agentsSeveral agents at once, each on a separate, well-scoped task.
Tests, CI & reviewAgent-written code passes tests, type checks, linters and CI, and I review every change.
span 07.2 engineering log newest first

Engineering log

Period, role, organisation, what I was responsible for, and the system it ran in.

Jan 2021 – nowFounder & ownerProtoCodeSoftware development, cloud architecture, server administration, DevOps and security for client companies.Studio for startups, SaaS platforms and enterprises
2022 – nowTechnical LeadSaaS platformBack-end development in Node.js, DevOps, cloud engineering and architecture, compliance readiness. Led the security initiatives and the DevOps, DevSecOps and integration projects.SaaS product for marketers · AWS, Terraform, microservices · through ProtoCode
2022 – 2023Full Stack DeveloperClient projectBuilt a business jet charter platform end to end: front-end, back-end, cloud architecture and database.PHP, Laravel, Node.js · Hetzner Cloud · PostgreSQL with PostGIS · through ProtoCode
Aug 2019 – 2022Back-end DeveloperThe same SaaS platformBack-end development and DevOps.Node.js, TypeScript, microservices, AWS, CI/CD · freelance, then through ProtoCode from 2021
Before 2019Full Stack DeveloperFreelanceFull stack development on various freelance projects.PHP, JavaScript, Laravel, React, Vue

open spanCurrent entries keep a line running off the page: the work is ongoing.

span 07.3 engineering perspective five principles

How I think about systems

P-01

Operational complexity is a design concern, not an afterthought.

P-02

Infrastructure decisions have business consequences.

P-03

Reliability requires explicit failure assumptions.

P-04

Security belongs in architecture and process, not in documentation alone.

P-05

Compliance controls should map to real systems and responsibilities.

span 07.4 method agents first · engineering around them

How I build: agents first

Before an agent writes any code, I define the system it works in: the architecture, the conventions, the boundaries and the context it needs. The goal is a codebase an agent can understand before a person has to read it.

  1. Context firstarchitecture, conventions, context files
  2. Parallel agentsseparate, well-scoped tasks
  3. Tests & CItests, type checks, linters
  4. My reviewevery change
  5. Shipped

That is how I ship much faster than a conventional workflow. The speed comes from the engineering around the agents, not from skipping it: nothing an agent writes reaches production until it has passed the tests and CI and I have reviewed it.

span 07.5 bridge engineering → compliance readiness

Compliance readiness as engineering work

A compliance control eventually has to exist in an architecture, an infrastructure and an operating process. That is why I treat compliance readiness as engineering work.

On the SaaS platform where I am Technical Lead, I am taking the platform through readiness aligned with ISO/IEC 27001: security policies, system and architecture documentation, and the technical controls in AWS and the back-end services.readiness, not audit or certification

span 07.6 relationship person · studio

Miloš and ProtoCode

Related, not interchangeable. This site is about me; ProtoCode is the studio through which all my client work runs.

Miloš Živković

Software & Cloud Engineer

role
Founder and owner
offers
Development, architecture and implementation; consultancy for teams that need to implement AI or get ready for a compliance audit
this site
Who I am and what I can do
Founderthe connection

ProtoCode

Studio · services and projects

what it is
A studio providing software development, cloud architecture, DevOps, DevSecOps, compliance readiness, FinOps and AI implementation, usually for startups, SaaS platforms and enterprises
client work
All of it is contracted and invoiced through ProtoCode
team
Miloš, with sub-contractors when a project needs them
span 07.7 verification facts you can check

Where to verify

Each line points to something you can check. No badges, no logos.

signalvaluehow to verify
Years of experience12 yearsEngineering log; LinkedIn profile ↗
RolesFounder of ProtoCode; Technical Lead for a SaaS platform; earlier client and freelance workEngineering log; LinkedIn profile ↗
Client referencesAvailable on requestAsk by email: milos@protocode.rs
Compliance experienceISO/IEC 27001 readiness for a SaaS platform, 2026 (ongoing)Ask by email; case study on protocode.rs, once published
TechnologiesNode.js · TypeScript · AWS · Terraform · PostgreSQLEngineering log
span 07.8 next step the open span connects

Get in touch

Work with meProjects and services go through ProtoCode · protocode.rs
Write to memilos@protocode.rs
Find me on LinkedInlinkedin.com/in/milos-zivkovic
miloszivkovic.dev© 2026 Miloš Živkovićback to top ↑