Author profile

Kristian Razum

Founder & Principal Engineer, LoadTester · Cloud Native d.o.o., Zagreb, Croatia

About

Kristian Razum is the founder of LoadTester and the principal engineer behind the platform. He has spent roughly a decade working on backend systems, distributed workers, and high-throughput HTTP services, and started LoadTester after repeatedly running into the same pattern: teams knew they should be load testing before releases, but the tooling they had available made it too expensive, too manual, or too disconnected from their actual delivery workflow to do it consistently.

He writes and reviews LoadTester's editorial content — pillar guides, tutorials, metric explainers, and tool comparisons — so that the documentation reflects how the product is actually built and how real teams use it, not a marketing abstraction of either.

Background & experience

Kristian's work on LoadTester covers the full stack of a managed load testing platform: the test execution engine (distributed workers, rate control, virtual user modeling), the telemetry pipeline (latency percentiles, throughput, error classification), the scheduler, the API used by CI/CD integrations, and the dashboard. That end-to-end ownership shapes the editorial stance — when an article discusses p95 versus p99 behavior, thresholds, or how a CI smoke test should be structured, the framing comes from having implemented the system that produces those numbers.

Before LoadTester he worked on backend systems where HTTP performance, queueing, and downstream latency were recurring operational concerns. Those experiences, including the mistakes, inform the "common mistakes" and "best practices" sections that show up throughout the guides.

Areas of focus

HTTP and API load testingPercentile latency (p50 / p95 / p99)CI/CD performance gatesThreshold design & SLOsRelease regression detectionWorkload modeling (VUs & RPS)Tool evaluation & comparisons

Editorial role & review process

Kristian is the visible, accountable author on LoadTester articles. Every article carries a publish date and a "last reviewed" date so readers can see when the content was last checked against current product behavior, current tooling in the ecosystem, and reader feedback. Material changes trigger a re-review; small typo fixes do not. The review standard is laid out in the editorial policy.

Comparison and "vs" pages carry a commercial disclosure: they are published by a vendor, they are not neutral directory listings, and they link to the editorial policy so readers can judge the framing for themselves.

Contact & further reading

Kristian can be reached via the company contact details on the About page, or directly on LinkedIn: linkedin.com/in/kristian-razum.