Skip to content
TrenckTech

About

One engineer, on purpose.

I'm Dylan Trenck. I build software for businesses, and I've deliberately kept this a practice of one, so the person you hire is the person who does the work.

I started building things because I wanted to know how they worked, and I never really stopped. That curiosity turned into a Computer Science degree, then a career, and eventually into this: a practice built around the kind of work I actually want to do.

How I got here

I was born in Norwalk, Connecticut and moved to Tampa in 2012. I studied Computer Science at the University of North Florida, where most of my attention went to machine vision and multi-modal machine learning. Teaching software to make sense of images, audio, and language at the same time, instead of one at a time.

Along the way I worked on an advertisement prediction project during an internship at Sporelogic, and started HighlightHub, a system that finds highlight-worthy moments inside hours of video. Both taught me the same thing from different directions: the model is almost never the hard part. The hard part is the messy reality around it, the data, the workflow, the human who has to trust the output.

Why an independent practice

The more businesses I talked to, the more I noticed the same gap. Small and mid-sized companies have real software problems, genuine, expensive, solvable ones, and two bad options for fixing them. Agencies quote six figures and staff the project with whoever is free. Marketplace freelancers are cheap until they vanish halfway through.

What's missing is the obvious middle: one experienced engineer who takes the problem seriously, quotes a real number, and is still there when it ships. That's what TrenckTech is. Not an agency in disguise, not a side project. A practice, run deliberately small so nothing gets lost in translation.

How I work

I care more about whether something is right than whether it's impressive. The best outcome I can deliver is often smaller than what a client came in asking for, and I'd rather tell you that on the first call than discover it together in month three.

I also believe you should own everything at the end: your code, your accounts, your infrastructure, in your name. If the arrangement stops working for you, it should cost you nothing but the notice period to walk away. Software that holds you hostage isn't software you own.

Outside the work

I train mixed martial arts, play guitar badly and enthusiastically, and spend more time at the beach than I probably should. I've been fascinated by the aerospace industry for as long as I can remember, and I still hope to write software that ends up somewhere off this planet.

If any of this sounds like the kind of person you want on your problem, the next step is a conversation.

Say hello

I would rather talk than be researched.

Thirty minutes on a call will tell you more about whether we are a fit than anything else on this site.

or email dylan@trencktech.com