Skip to main content

About

Thirty years fixing expensive problems. Now on my own.

I'm Mark Kreyman. I started in telephony in 1996 and worked on the phone systems large companies answer on. Since 2011 I have written the software behind live TV for millions of subscribers, healthcare payments, patient referrals and panic buttons for hotel housekeepers. Now I do that work directly for the businesses that need it.

01 · Story

The short version

I started in 1996 at VocalTec, selling software that carried phone calls over the internet, then spent years on the messaging systems behind business phones at Avaya and the firms that installed them. In 2011 I started writing the software myself. Most of it was work that was not allowed to stop: healthcare payments at Optum, part of UnitedHealth Group, live streaming at Sling TV, safety devices at ROAR For Good, patient referrals at Blockit.

Six industries that look nothing alike, and underneath they were the same job. Something expensive was being done by hand, or by a system that had stopped fitting, and somebody had to work out what it really cost before writing a line of code to replace it.

The most recent chapter before going independent was as the sole backend engineer for a production e-commerce and savings platform at a national performance-marketing company — a walled system serving real customers at national scale, where I owned the whole server side and carried the pager for it.

Working for myself changed who I answer to, not the standard. I design, build, test, deploy and operate what I write, and you talk to me rather than to an account manager.

Mark Kreyman, independent senior software engineer

02 · Approach

How I work

Four commitments that decide what actually ships.

4 working principles

  • Quality-gated engineering

    Nothing ships without the gate: compile-clean, linted, type-checked and a full test suite green. That is not ceremony — it is how one engineer moves fast without breaking what already works.

  • Real systems, not demos

    Software that runs in production with real users, real data and real failure modes: background jobs, retries, observability, and a plan for the 3am page.

  • Direct partnership

    You talk to the engineer building it. No account layer, no status-report theatre — short feedback loops, working software you can see, straight answers.

  • Owned end to end

    Architecture through deploy. I take responsibility for the whole system, not for a ticket inside somebody else's.

03 · Credentials

Experience

Where the thirty years went.

  • In production systems since 1996, starting in internet telephony, and writing the software since 2011
  • Sole backend engineer for a production e-commerce and savings platform at a national performance-marketing company
  • Founder and sole engineer of loopctl, CronBooks and HomeCareBilling
  • Elixir, Phoenix, PostgreSQL, Oban and Fly.io, with Ruby on Rails before them
  • Denver Metro, Colorado — working with clients nationwide
Mark Kreyman on LinkedIn

Want to talk through a project?

Start with the discovery chat. It's a real conversation that scopes what you're building — no forms to fill in, no sales call.

Start a discovery chat
Start a discovery chat