Lukas Janda hey@lukasjanda.com

Hey! I'm

Lukas Janda

I build and ship production software — fast. A senior full-stack engineer with an AI-accelerated workflow that turns weeks of delivery into days.

I founded and led a software company — a team of ~15 engineers at peak. With a modern stack and an AI-accelerated workflow, I now deliver that same scope with 2–3 people. I've run it both ways.

~15 engineerssame scope2–3 people

Available for contract and fixed-scope work — around 10–20 hours a week, remote, across EU and US hours.

// what I sell

  • Fixed-scope build

    An agreed scope at an agreed price, working and deployed in days rather than months.

  • AI integration

    LLMs and automation inside a product people actually use, not a demo that impresses once.

  • Integration work

    Making the systems a business already runs on talk to each other, and stay in sync.

  • Fractional tech lead

    Senior engineering judgment on the days you need it, without a permanent hire.

// track record

~15 → 2–3engineers for the same delivery scope

18 yrsshipping production software, since 2008

100+projects delivered

1000+features shipped

  1. 2008–2018

    Founder & engineering leadown software company, ~15 engineers at peak

    Grew it from the first paying client to a ~15-engineer team, owning architecture, hiring and delivery across the whole portfolio — and the client relationships that funded it. Ran the business side and the codebase at the same time.

  2. 2018–now

    Senior full-stack engineerproduct company, long-running production system

    Day-to-day delivery on software that real operations depend on: offline-first field apps, AI document pipelines, computer-vision workflows and the integrations that keep separate systems in sync. Production, not prototypes.

  3. 2020–now

    Independentlukasjanda.com, selected client work

    Fixed-scope builds, AI integration sprints and fractional tech-lead work, taken on directly. Small scopes, agreed up front, shipped.

// proof

A few things I build a lot, and how they actually work.

Offline-first field apps

capturelocal queuereconcilesync

Work is captured straight to the device and dropped onto a durable queue, so a dead connection never loses anything. When the network returns, queued events replay in order and conflicts resolve against server state — the person using it never has to think about "offline."

TypeScript · IndexedDB · service workers · REST / JWT

AI document pipelines

ingestextractclassifyvalidatereport

Inbound files move through isolated serverless steps: OCR pulls the text, an LLM classifies and structures it, results are checked against reference data, and a clean report comes out the other end. Each step is retryable, so one bad input never stalls the batch.

Python · serverless · Claude API · OCR

Image detection & segmentation

imageon-device modelvision-LLM fallbackstructured result

A fast on-device model locates and segments objects and text in a photo in real time; anything it's unsure about escalates to a vision-LLM for a second opinion. Raw pixels go in, structured and checkable data comes out.

YOLO · on-device CV · vision LLM · TypeScript

Automated discovery & monitoring

scan sourcesfilterLLM-scorededupdigest

A scheduled job sweeps multiple sources, cuts the noise with a keyword pass, then has an LLM score each item for fit with a short reason. Everything seen is remembered so nothing repeats, and a single ranked digest lands in your inbox each morning.

serverless cron · Claude API · KV store · email

System integrations

source APItransformdedup + retrydestination

Scheduled services move and reshape data between internal APIs and third-party platforms — format conversion, deduplication, retries with tracking — so systems that were never meant to talk stay in sync without anyone babysitting them.

serverless · queues · REST / SOAP · webhooks

// also: document & PDF generation · data-import pipelines · legacy API gateways · admin dashboards

// how I work

talk to usersrequirementssketch workflowalignprototypedeployreal usetune

I talk to the people who'll actually use the thing, agree the workflow before anyone writes code, then get a functional prototype deployed and in real use as fast as possible. Everything after that is tuning against reality instead of guessing — which is why scope stays honest and nothing gets built for six months before someone notices it's wrong. Tasks and use cases get documented as I go.

  • Remote and async-first, across EU and US hours, in English.
  • Around 10–20 hours a week, alongside a full-time role — enough for a fixed scope, not enough to be your only engineer.
  • Direct and low-overhead — you talk to the person doing the work.

// stack

Frontend
TypeScriptVue 3ReactMapLibrePWA
Backend
NodePython/FastAPIKotlin/Spring
Data
PostgreSQLSQLite/D1Supabase
AI
Claude & OpenAI APIsRAG and extraction pipelinesYOLO/computer vision
Platform
Cloudflare Workers/Pages/KV/R2serverless-first
Practice
Unit and E2E testingcode reviewrelease process

// say hey

Got something that needs building?

hey@lukasjanda.com

Usually replies the same day. Happy to start with a 20-minute call.