Consulting

Two ways to hire me. Either I join your team for a stretch, or I take one defined piece of work, finish it, and hand it back. Same engineer, same subject: video that has to reach people and keep reaching them.

Contract engineering

I embed in your team and work the way the team already works: your board, your reviews, your on call if that is part of the role. The work is video delivery and packaging, ad insertion, player integration across browsers and living room devices, and the Amazon Web Services media stack underneath it, from origin and packaging out to the edge.

Day rate, remote on Central European Time, through an agency or direct. Three months or more is the shape that works. Anything shorter is better bought as one of the engagements below.

Fixed scope, via Atlantic Blue Solutions Ltd

My company. One price, one date, and a document or a change set at the end of it. Three shapes come up more than any others.

Streaming observability audit

2 to 4 weeks

Playback complaints arrive as anecdotes. Nobody can say how many sessions broke, on which devices, or at which point in the delivery path.

Common Media Client Data and Common Media Server Data reported from the player through the content delivery network, landing in the tools you already query. You get the rollout itself, dashboards over the fields that matter, and a written read of what the first weeks of data say about the quality of experience you are actually shipping.

Server side ad insertion, integration and measurement

2 to 4 weeks

Ads fail to stitch, or they play and the counts disagree with what the seller invoiced. The break is somewhere between the ad server, the manifest manipulator and the player, and no single team can see the whole path.

One Video Ad Serving Template workflow traced end to end, ad request through manifest to beacon, under both server side and server guided insertion. You get the integration working, the failure modes written down, and a measurement note saying which numbers to trust and why the others differ.

Streaming cost review

1 to 2 weeks

The delivery bill grows faster than the audience. The encoding ladder was set once, for a device catalogue that has since changed, and nobody owns it now.

A costed model of your codec ladder and your egress, rung by rung, against the sessions each rung actually serves. You get the changes ranked by money saved against the work to make them, so the cheap ones can ship the same week.

Where this comes from

I built a server side Video Ad Serving Template proxy for a UK broadcaster in 2026. Before that I worked on delivery infrastructure at DAZN and at Peacock scale, and on digital rights management workflows at castLabs. The pattern across all of it is the same: the stream is fine in the demo and breaks in the field, and the fix starts with being able to see it.

Start

Email hello@juliantellez.com and tell me what's broken. A paragraph is enough. I will tell you which of the two this is, roughly what it costs, and if it is not work I should take, I will say so.