Furkan Yildiz

Concept, design, and implementation of hdabdichtungstechnik.de for a specialist company for building waterproofing in Heidelberg. Scope: complete website (services, references, FAQ, legally compliant pages), contact form with spam protection, database for all inquiries (Cloudflare D1), protected admin dashboard for lead management with status and notes, automatic email notification for new inquiries, as well as deployment and domain setup via Cloudflare. Result: The company receives inquiries in a structured system instead of scattered in their inbox.

PolGerWorks supplies Polish skilled labor teams (B2B) to German construction and industrial companies. As co-founder, I am responsible for the complete digital setup: website polgerworks.com (concept, design, implementation, deployment via Cloudflare), email infrastructure with own domain (DKIM/SPF, team mailboxes, signatures), operating system in Notion (skilled worker pool with over 80 contacts, partner management, job board with matching views per trade) as well as bilingual sales documents (order PDFs DE/PL, flyers, email templates). Result: from a blank slate to operational business with the first active orders within two weeks.

At Tenion AG, I test a complex SaaS platform with multiple modules for administration, communication, and organizational processes.

My focus is on testing complete user flows rather than isolated functions. I test typical and atypical usage scenarios to identify inconsistencies, logic errors, and problems in the interaction between different areas.

I immerse myself in different roles and use cases and check how the system behaves in real-world use. I pay particular attention to navigation, data consistency, and understandable user flows.

A central part of my work is the structured recording of bugs. I document problems clearly and comprehensibly with concrete steps, expected behavior, and actual results, so that developers can quickly understand and efficiently fix issues.

Additionally, I also test under unusual conditions, such as repeated actions, switching between modules, or altered workflows, to find errors that are often overlooked in standard scenarios.