Software engineer · Worms, Germany
Websites, web applications and digital experiences for businesses with something to prove.
Sites and products I designed and built, all of them live. Three were built for other people; one is my own.
FTA – Faruk Tepe Architektur · Architecture · 2026
A digital presence for a Rhein-Main architecture office — built so the practice can publish a new project by dropping a folder of photographs into place.
Own product · Hiring platform · 2026
A two-sided hiring platform for Turkish-speaking businesses across Europe — native iOS app and web, on one Supabase backend.
Nutrition practice · 2026
A bilingual practice site for a dietitian working between Turkey and Germany — an editorial nutrition guide with online consultation booking.
Engineering · Personal brand · 2026
A bilingual personal brand site for a civil engineer in the Frankfurt region — career, projects and an international profile, in English and German.
Work outside the browser — smart contracts, computer vision, iOS. Source is public.
Smart contracts
A decentralised lending protocol in Solidity: twelve contracts covering credit scoring, a lending queue, investor funds, an insurance pool and liquidation bounties.
Solidity · Hardhat · Ethers.js · Hardhat Ignition
View on GitHubComputer vision
Detects, classifies and counts eleven types of vehicle in traffic footage. Custom-trained YOLOv8 with ByteTrack, so a vehicle crossing the line is counted once and not again.
Python · YOLOv8 · ByteTrack · OpenCV · Roboflow
View on GitHubiOS
A SwiftUI film search client for the OMDb API — MVVM throughout, its own networking layer with error handling, image caching, and an in-app switch between three languages.
Swift · SwiftUI · MVVM · OMDb API
View on GitHubiOS · WidgetKit
An iOS home-screen widget that mirrors a choice made in the app. Shared storage through an App Group and a timeline that reloads the moment the selection changes.
Swift · SwiftUI · WidgetKit · App Groups
View on GitHubFive things, done properly, rather than a list of everything I could theoretically take on.
Marketing sites and company presences that load fast, read well and turn visitors into enquiries. Designed and built by the same person, so nothing is lost in the handover.
Dashboards, portals and internal tools built around how the business actually works — auth, roles, data and the awkward edge cases that come with real users.
From an idea on a call to something in people's hands. Product architecture, interface design, development and the launch itself.
Technical SEO, structured data, indexing and Core Web Vitals. Usually the difference between a site that exists and a site that gets found.
Sites go stale the day they launch unless someone keeps them. Updates, changes, monitoring and a person who answers when something breaks.
I studied Computer Engineering at Selçuk University and now work from Worms, in Germany, building for clients here and across Europe.
Most of what I do is turning something complicated into something that feels obvious. An architecture office with thirty projects and nowhere to put them. A hiring platform where two kinds of user must never be able to become each other. The interesting work is almost always in the constraints, not the screens.
I work directly with the people I build for. No account manager in between, no agency markup, and no handover between a designer who left and a developer who inherited it.
Four steps, and you know where the project is at every one of them.
Understand the business, the audience and what the site actually has to achieve. Usually one call and a short written brief.
Visual direction and structure, shown as real screens rather than a mood board. You approve it before a line of production code exists.
Development on a live preview URL you can open at any point. Feedback goes straight into the build instead of into a document.
Deploy, connect the domain, submit for indexing, measure. Then keep improving it — launch day is the beginning of the useful data.
One point of contact from the first call to launch. Nothing gets lost being explained a second time.
Sites are built to hit their Core Web Vitals from the first deploy, not optimised in a panic afterwards.
Metadata, structured data, canonicals and sitemaps ship with the site. Being findable is not an add-on.
No page builder, no bought template with your logo dropped in. What gets built is what your business needs.
Next.js, TypeScript and Postgres — boring, well-supported tools that another developer can pick up in five years.
Ongoing changes, updates and support, so the site is still current a year later.
Tell me what you're working on. I read everything that comes in and reply within a working day.