Skip to main content

// About

The story behind the code

2020: Apprentice

SINC NOVATION Group took me on for my Ausbildung as Fachinformatiker für Anwendungsentwicklung (IHK), the German vocational qualification for application developers. I didn't know what a REST API was. I did know I wasn't leaving until I did.

The work was data preparation and cleaning scripts for secure card production, and website solutions. Data that has to be exactly right teaches you to check your assumptions before you trust your output.

The moment it clicked was when I understood that coding isn't about memorising syntax. It's about learning to think in systems.

I stayed four years, grew from apprentice into a fullstack developer, and worked remotely.

2024: From call center to AI

I joined Oracom GmbH as a Senior Fullstack Developer. Back then Oracom was a call center. It has since grown into a company that builds AI communication products.

I became the principal architect of that platform and an engineer on it, from choosing the tech stack to writing production code. We built it up from nothing, and that work continues.

The data thread from SINC carried over. Some of my first Oracom work was synchronising data between a customer's system and AWS, cleaning and importing tenant data, and rebuilding a tenant sign-in app in Nuxt. Preparing data turned into building data pipelines, and those pipelines became part of the AI platform.

2026: The lead

In July 2026 I became Team Lead of Oracom Intelligence , the company's IT department. The work didn't stop being code. It started being people too.

Leadership isn't delegating everything and disappearing. It's agreeing priorities so the team isn't pulled in every direction at once, making clear who owns what, helping people grow into their own judgment, and staying close enough to the code to review it honestly and contribute where it matters.

2026: The studio

In September 2026 I founded Nishan Systems , a Berlin studio for software, brand, and marketing. "Nishan" is Kurdish for brand, or mark. Its first client is a barbershop with two locations in Zwickau.

Timeline

  1. Sep 2026 – present

    Founder

    Nishan Systems · Berlin

    Studio for software, brand, and marketing

  2. Jul 2026 – present

    Team Lead & Senior Fullstack Developer

    Oracom Intelligence · IT department of Oracom GmbH · Berlin

    Leads the IT team of five team members; priorities, architecture, people management, and hands-on engineering

  3. 2024 – Jun 2026

    Senior Fullstack Developer

    Oracom GmbH · Berlin

    Principal architect of the AI communication platform and an engineer on it

  4. 2020 – 2024

    Apprentice, then Fullstack Developer

    SINC NOVATION Group · Remote

    Ausbildung zum Fachinformatiker für Anwendungsentwicklung (IHK); data preparation and cleaning scripts for secure card production, and website solutions

How I lead

I lead Oracom Intelligence , the company's IT team: five team members and me. I report to the CEO. My part is organisation, planning, people management, architectural guidance, and reviewing implementation, and I keep writing production code. These are ongoing responsibilities, not finished results.

  • Agree priorities, then protect them

    I set priorities with the CEO and the other departments. Unclear or urgent requests get their scope clarified and a place in that order, instead of going around it.

  • Make ownership and dependencies clear

    Larger work starts with a staged plan that says who owns which part, what depends on what, and how we will know it works, with acceptance criteria written down before anyone builds.

  • Gate big commitments with evidence

    Before a larger integration or a tooling change, I ask for a reproducible proof or a baseline and a pilot. A plan that fails its gate gets rescoped, not forced through.

  • Mentor and remove blockers

    I teach Nuxt and Tailwind, Git, MCP, agentic AI, RAG and embeddings, and the practices around them. I designed our RAG document pipeline and coached a teammate to build it, so one more person owns that skill.

    Read the case study

  • Stay hands-on where it counts

    I review implementation and take on reliability, integration, and complex technical work myself, most recently the lifecycle of real-time AI conversations.

    Read the case study

  • Keep the work sustainable

    Clear priorities, usable documentation, honest release communication, and systems colleagues can maintain without me do more for a team than overtime does.

Principles

  1. The Beaver Principle

    A principle I developed and live by, because beavers amaze me. I have read and watched a lot about them: they build with precision, not for show, and the whole river is better for it. So: build with absolute precision. Never for applause. Everything downstream should benefit. Nishan Systems is built on it.

  2. Systems thinking

    Features are parts of a system. I care about how the parts fit, what happens when they fail, and who has to maintain them after me.

  3. Developer experience is not optional

    The friction developers feel every day is a real cost, even when it never shows up on a dashboard.

    Post: The Invisible Burn

  4. People-first leadership

    I lead the humans behind the code: growing them, shielding them from burnout, and staying close enough to the work to know what I am asking of them.