Skip to content
Jiří Urbášek

Work with me

I’m a senior software engineer with 17+ years on Apple platforms and hands-on work on 30+ production codebases — startup MVPs, long-running consumer apps, enterprise, banking and FinTech, HealthTech, IoT and Bluetooth hardware, and my own indie apps.

If your team could use an experienced Apple-platform engineer — to build something new, untangle something old, or get a second opinion before a big decision — I’m happy to help.

I enjoy working with product-minded teams where engineering is close to the product, and where people care about what gets built, not just how many tickets get closed.

What I can help with

Why me

I’ve seen a lot of codebases

Working hands-on in 30+ production codebases means I’ve seen many ways to solve similar problems — including some that taught me exactly what not to do. :)

That makes it easier to recognise patterns, real problems and unnecessary complexity. Years of contracting also mean I can enter an existing project and become productive quickly, without months of onboarding.

I go deep on macOS, not just iOS

Right now I work as a senior macOS developer on system-level components, the kind of macOS work most app developers never touch:

On top of that, my own apps ship on both iOS and macOS with a shared codebase and CloudKit sync. So whether you need a Mac app, a Catalyst port, or something running way below the UI — I can help.

I think about the product

My own apps taught me more about product development than implementing yet another feature in somebody else’s application. When it’s your own product, you learn very fast that shipping code is not the goal.

Building something useful that people understand and actually use is the goal.

I’m fluent with AI — and still an engineer

I’m not just occasionally asking ChatGPT to generate a function. Coding agents are part of my planning, implementation, review and verification workflow, and I use different models to check each other’s work.

But AI is leverage, not magic. Somebody still has to understand the problem, recognise bad output and make the important decisions. That’s the part 17 years of experience is good for.

I’ve done the hard, unglamorous parts

A few examples:

Practical details

Let’s talk

If you’re building something interesting and think I could help, I’d be glad to hear about it. A short message about what you’re building and what you need is plenty — no formal process required. :)