I build production systems end to end — a cold-calling CRM used by a real sales team every day, a lead-generation data pipeline that runs unattended around the clock, and a multi-agent AI operations layer that keeps it all running with a human approving the decisions that matter.
| Version | Markdown (GitHub) | PDF (application) | DOCX (editable) |
|---|---|---|---|
| 🇬🇧 English CV | View | Open / download | Download |
| 🇩🇪 Deutscher Lebenslauf | Öffnen | Öffnen / herunterladen | Herunterladen |
| 🌐 Portfolio | - | atakan-24.github.io | - |
The CV is maintained in three formats, each for a different purpose: Markdown is the GitHub/developer-facing version, PDF is the final, application-ready file, and DOCX is the editable master used to produce both. Content is kept identical across all three; only the format differs.
Why I didn't take a conventional apprenticeship route into IT, what I'm actually working toward over the next 12 months, and what happens if the plan doesn't work out.
| Version | Markdown (GitHub) | DOCX (editable) | |
|---|---|---|---|
| 🇬🇧 English | View | Open / download | Download |
| 🇩🇪 Deutsch | Öffnen | Öffnen / herunterladen | Herunterladen |
An AI-operated cold-calling platform (Next.js, Supabase, Telnyx voice/WebRTC, LLM voice agents) and the multi-agent automation layer that runs it — one human approving the decisions that actually matter, not every step.
| gh-radar | Daily digest of what actually needs you on GitHub — read-only by construction | HTTP layer refuses every method but GET, CI asserts it; 58 tests |
| git-secret-scan | Pre-commit hook + GitHub Action that stops API keys reaching a commit | Measured recall 80% → 100%, 98 tests, CI on 3 OS × 3 Python versions |
| yt-transcript | YouTube transcripts with a four-tier fallback chain | Routes around per-IP rate limits via an SSH relay; 40 tests |
| gitingest | Flattens a repository into one searchable file | Refuses to truncate — falls back to structure instead |
| fahm | Arabic spaced-repetition app, live | 3,177 lines in one HTML file, no framework, offline PWA |
| postgrest-keyset-page | Cursor pagination for PostgREST-style REST APIs | Fixes a real bug: offset pagination silently drops/duplicates rows under concurrent writes; the failure is reproduced live in the test suite |
| portfolio-tracker | Backend behind this site's analytics and "Ask me directly" chat | Never stores an IP or a name — country comes from a transient geolocation lookup, the chat is grounded to a fixed knowledge block and says "I don't know" instead of guessing |
I direct AI coding agents deliberately — clear specifications, hard guardrails, and treating every "it's done" as a claim to verify, not a fact.
My journey — a non-traditional path into engineering
Before writing code, I spent a few years running online businesses — e-commerce, affiliate marketing, a YouTube channel. That's where I learned to get someone's attention and turn it into a paying customer, long before I could write a line of code.
Around 20 I started learning to code, at first alongside that work. At 22 I moved to Egypt and shifted my focus fully to software — freelance client work first, then building the acquisition systems (cold calling, AI voice calling, email and outreach) for my own business, Team Gold. Most of what's above grew out of that: I don't build software in the abstract, I build it because a real workflow needed it, then operate it long enough to find out what breaks.
I didn't take the university route. What replaced it was building things, breaking them, and fixing them in production, repeatedly.
I also build and ship this kind of work for other businesses through teamgoldllc.de — production web systems, automation, and the infrastructure that keeps them running.
