Software engineering & AI · Hamburg
Manual chaos in.Automated order out.
I am a software engineer. I build custom applications, automate work with AI, and teach teams to use it — from small businesses to corporations.
Hamburg and remote. German or English, on site or from a distance — from ten-person operations to large corporations.
Services
Four areas I work in. Most projects touch more than one.
- Software
Software consulting & development
Custom applications from first sketch to running in production — and straight advice about what you already have. If what you own can be saved, I say so instead of selling you a rewrite.
- Web applications, internal tools and portals
- APIs and interfaces between the systems you run
- Architecture consulting, code reviews, second opinions
- Modernising what exists instead of rebuilding it expensively
- Tests, documentation and a deployment you operate yourself
- Automation
Process analysis & automation
First I look at how the work actually gets done — with the people who do it every day. Then the work that comes back daily and moves nobody forward disappears: copying data, producing documents, triaging requests.
- Map the workflow, name the bottlenecks, put numbers on effort and return
- Automate recurring work, from quote to invoice
- Connect the systems you already run: CRM, ERP, e-mail, file storage
- Extend your existing software with AI instead of replacing it
- Training
AI training for your team
Not a talk about AI — working with AI: on your real tasks, with your real documents. Built for business teams and managers, explicitly not for developers.
- Workshops for business teams, assistants and leadership
- Exercises on your own work, not on sample data
- Clear rules about what may go in and what may not
- Follow-up until it sticks in day-to-day work
- Claude Skills
Claude Skills & MCP development
A Claude Skill is a capability you teach an AI permanently: your quote format, your review steps, your tone of voice — defined properly once, then identical every time. The field is new and almost nobody offers this yet. I build those skills, and the MCP servers that connect them to your systems.
- Claude Skills for your recurring tasks and formats
- MCP servers: make internal systems and data reachable for AI, safely
- Plugins and bindings into your existing software
- Operations, versioning and permissions — so it does not stay a prototype
Not sure which of these you need?
Then that is exactly where we start. You do not need to know whether the answer is software, automation or training — we work that out in the call. I take on anything around software and AI. And if I am the wrong person for the job, I will tell you that too.
The same work, wired two ways
The work stays with your team. What goes away is the retyping, forwarding and checking.
Two views of the same workflow. Left: one person is wired by hand to five separate tools, the connections crossing each other. Right: the same person hands off once to an automation that drives the same five tools in an orderly fan-out. The output is identical in both.
Today: Every system hangs off a person. Five tools, five manual steps, every day.
With automation: One handoff. The systems talk to each other; the person just decides.
AI does not replace people.
It amplifies them.
The person at the desk is the same on both sides, and still makes the same calls. What changes is what they spend the day doing.
How I work
From the first question to the point where you no longer need me — to the same standards I work to at Tesla. Just without the corporate machinery around it.
01 — Analysis
Whatever the project size
- Code review, not solo commits
- Automated tests where it hurts
- Deployments at the push of a button, not by hand
- Documentation from day one, not bolted on at the end
- 1
Analysis
I look at how the work really gets done — with the people who do it every day. Afterwards we both know where the time goes.
- 2
Concept
You get a plan with a price: what gets built, with what, in what order, and what it should return. If it does not add up, I say so.
- 3
Build
Every week or two there is something finished to try. I write tests around the parts that hurt when they break — no months of waiting for one big release where half of it turns out wrong.
- 4
Integration
It gets connected to the systems you already run, so it lives where you already work — not in one more tab nobody opens.
- 5
Handover
The code is yours, with documentation and a walkthrough. You should be able to run it without me — or hand it to someone else without them starting from zero. I stay reachable if you need me.
About
I am Tareq Jami, a software engineer based in Hamburg. Since 2019 I have been building web platforms, internal tools and interfaces — for large corporations as much as for thirty-person operations. I currently work as a Lead Frontend Engineer at Tesla and maintain ng-openapi, an open-source tool for developers, on the side.
What I have learned along the way: most of the time does not disappear into the hard work, it disappears between the systems — retyping, forwarding, checking. That is where Jami IT starts. I am not selling AI. I am an engineer, and AI is one of my tools — sometimes the right one, often plain well-built software does the job better.
Good fit
- Small business, mid-sized company or corporation — I have built for all three
- Teams that already suspect where it hurts — or want to find out
- A wish not to depend on me once it is done
- A willingness to change a process, not just digitise it
Probably not a fit
- Pure staffing or body leasing
- AI because it should be AI — with nobody able to say what for
- AI as a requirement where plain software is the better answer
- Work that needed to be done yesterday
Common questions
The things that come up first in almost every intro call, answered up front.
What does it cost?
It depends on what gets built, which is why I do not quote a flat rate before seeing how you work. After the intro call you get a plan with a price: what will be done, in what order, and what it should return. Small pieces are billed by time; clearly scoped projects can be fixed-price.
Do we need to know what we want first?
No. It is enough to notice that something takes too long every day. Working out whether the answer is software, automation or training is part of the job — and the first step of every project.
How long does a project take?
From half a day to several months. A team workshop is done in a day, a first automation often runs after two to three weeks, a full application takes correspondingly longer. Either way there is something finished to look at every week or two, rather than a long silence.
Do you work on site or remotely?
Both. In and around Hamburg I am happy to come in, particularly for the analysis and for workshops — seeing people at their actual desks helps. Everything else works just as well remotely. In German or English.
What happens to our data when AI is involved?
We settle that before anything is built: which data may leave the building, which may not, and which models or hosting options are therefore even on the table. If data cannot leave, that is a requirement like any other — not a reason to abandon the project.
What is a Claude Skill?
A capability you teach an AI permanently instead of explaining it again every time: your quote format, your review steps, your tone of voice. Defined properly once, the AI then does it the same way every time. Via MCP servers it can additionally reach your own systems — in a controlled and auditable way.
Will we depend on you afterwards?
That is explicitly not the goal. The code is yours, with documentation and a walkthrough, and you operate the deployment yourselves. You should be able to run it without me — or hand the whole thing to someone else without them starting from zero.
Contact
The fastest route is a no-obligation intro call. Thirty minutes on whatever is stuck right now — an application nobody dares touch, a process that eats hours every day. Afterwards you know whether software, automation or both are worth it for you. Including when the answer is "probably not".
- Reply
- Within one business day, from me personally.
- Then
- A short call, by phone or video. Not a sales pitch.
- Languages
- German and English.