Akıncan Kılıç

 

Akıncan

Answers on my behalf

Or start here

From model to production

I build AI systems from the training data to the machines they run on.

I train and serve models

I build labelled datasets, fine-tune language and vision models, compare checkpoints, and turn the selected model into an API that other systems can use.

  • LoRA and supervised fine-tuning, held-out evaluation, error analysis and human review
  • GPU training and inference with batching, async jobs, vLLM and containerized endpoints

I build on Google Cloud

I deploy event-driven services, APIs and data pipelines on GCP, then set up the permissions, secrets, storage and monitoring they need to run safely.

  • Cloud Functions, Cloud Run, Compute Engine, Pub/Sub, Cloud Storage and Artifact Registry
  • Firebase, Firestore, IAM, Secret Manager, BigQuery, Cloud Logging and release automation

I build data systems

I turn messy source data into something models, analysts and products can trust, from ingestion and validation through embeddings, clustering and report generation.

  • Schema validation, entity resolution, quality controls, resumable jobs and human handoffs
  • Embedding services, vector search, clustering experiments and large asynchronous workloads

I run the infrastructure

I set up and operate Linux machines, private networking and protected service access alongside the AI and data workloads running on them.

  • VM and VPS setup, SSH hardening, disabled root access, fail2ban, firewalls and Tailscale
  • Docker, NGINX, TLS, protected API keys, machine scaling, logs, metrics and health checks

Intero Logo

Apr 2024 - Present

Founding Machine Learning Engineer

Intero

I joined Intero as its founding machine learning engineer. I build the machine learning systems the product runs on, and I run the infrastructure they sit on.

What I worked on

  • I built the LLM pipeline from scratch, and I still run it.
  • I train, evaluate and serve the models behind it, GPU work included.
  • I built the async data and vision infrastructure that feeds it.
  • I run the Google Cloud services and the Linux machines all of it sits on.
  • Production ML and Cloud Platform

    LLM orchestration, Google Cloud and Linux operations

    The platform the machine learning work at Intero runs on. I build the services the product calls, provision and run the machines underneath them, and keep the pipeline between them typed and resumable so a failed stage picks up where it stopped instead of starting over.

    • I build on Cloud Functions, Cloud Run, Compute Engine, IAM and Secret Manager, with Firestore holding application state.
    • I provision the Ubuntu hosts myself, with Tailscale, locked-down SSH, fail2ban, Docker, NGINX, TLS and monitoring.
    • I designed the typed stages, the contracts at each boundary and the event orchestration that moves work between them.
  • 32B Model Fine-Tuning and Serving

    Two QwQ-32B LoRA fine-tunes trained on four H200 GPUs

    The use case and dataset content are private, so this covers the model work only. I fine-tuned two QwQ-32B models for a classification system, from data preparation through training to the served endpoints. The system scored 93% on a benchmark kept out of training.

    • I trained with LoRA at rank 128 and alpha 128 through Axolotl, on 171,031 labelled examples I prepared.
    • Four NVIDIA H200 80GB GPUs per run, four epochs, and I kept epoch two once the later ones started losing ground.
    • I served the selected weights with vLLM on Modal behind OpenAI-compatible endpoints, with FastAPI at the request boundary.
    Read more
  • Distributed Data and Vision Infrastructure

    Async workers, GPU inference and repeatable Linux deployments

    The long-running side of Intero. Jobs that chew through a lot of data over hours, on machines that have to recover without anyone watching them. I built the workers, the storage they write into and the GPU vision inference running on top.

    • I built bounded asynchronous workers with batched writes, retries and atomic storage.
    • I run a Dockerized Linux VM fleet with private networking, protected access and repeatable rollouts.
    • I deployed GPU vision inference with versioned outputs, structured logs, metrics and failure recovery.
Viable Logo

Jun 2022 - May 2024

Junior Machine Learning Engineer

Viable

I spent two years working remotely with a US team, moving between the data side and the model side of the product depending on what needed building.

What I worked on

  • I ran embedding and clustering services in production, GPU inference included.
  • I built the ingestion path that turned inconsistent customer files into usable data.
  • I chose the models and the clustering algorithms, and built the evaluation behind those choices.
  • I automated the recurring report work and the checks that ran before anything went out.
  • Clustering and Embedding Infrastructure

    GPU embeddings, high-memory clustering and model evaluation

    Embeddings want a GPU and clustering wants memory, so I split them into two services instead of one that did neither well. I also built the tooling that decided which models and algorithms we actually shipped.

    • I built a FastAPI embedding service that kept the transformer model loaded on GPU and exposed a narrow authenticated API.
    • I moved long clustering runs into asynchronous Compute Engine workers and stored large results in Cloud Storage.
    • I compared classical, density-based, agglomerative and LLM-assisted approaches with labelled examples and clustering metrics.
  • AI-Assisted Data Ingestion

    An eighteen-stage pipeline for inconsistent customer exports

    Customers sent us files that agreed on nothing. Different columns, different date formats, different identifiers, different encodings. I built the pipeline that turned all of it into one shape the product could load.

    • I separated encoding, headers, dates, identifiers, reshaping and validation into explicit, resumable stages.
    • I used a language model to classify unfamiliar columns and return constrained mappings instead of free-form output.
    • Deterministic checks, dry runs and operator review kept uncertain model decisions away from production writes.
  • Report Operations and Quality Systems

    Scheduling, parsing and delivery checks for customer reports

    Reports went out on a schedule, and most of the work around them was manual and easy to get wrong. I automated the recurring parts and put checks in front of delivery so a bad report did not reach a customer.

    • I built a scheduled Cloud Function that handled report cadence, company resolution and operational updates across several services.
    • I used confidence thresholds and deterministic rules to automate ordinary cases while keeping uncertain matches visible to operators.
    • I built parsers that checked citations, quotations, empty sections and low-support findings before delivery.
Akıncan Kılıç

2026 - Present

Software Engineer

Vipulse

I designed and built Vipulse’s multilingual corporate website and its publishing platform. The work covers the Next.js application, Payload CMS, PostgreSQL data model, lead capture, consent-aware analytics, search foundations and the release workflow.

I took the project from information architecture and visual system through implementation and deployment, with separate English and Hungarian content and a CMS workflow the company can operate directly.

What I worked on

  • I built the application in Next.js, TypeScript and React.
  • I designed the Payload CMS collections and PostgreSQL publishing model.
  • I implemented multilingual routing, structured metadata, lead capture and consent-aware analytics.
  • I set up previews, validation and controlled Vercel releases.

Built here

See the project
  • Vipulse Corporate Website

    A multilingual website and publishing system for electronics manufacturing

    I designed and built Vipulse's production website, publishing platform and lead-capture system. The Next.js application serves separate English and Hungarian content from Payload CMS and PostgreSQL, with technical product pages, structured metadata, consent-aware analytics, spam controls and a preview-to-production release workflow.

    • A Next.js and Payload CMS platform with separate English and Hungarian content, previews and structured publishing workflows.
    • Technical service pages, reusable product modules, metadata, sitemaps and schema markup built for industrial buyers and search engines.
    • Protected lead capture, rate limiting, transactional email, consent-aware analytics and controlled Vercel releases.
    Read more
Manisa Celal Bayar University Logo

Sep 2019 - Jun 2023

BSc Computer Engineering

Manisa Celal Bayar UniversityEducation

Four years of computer engineering fundamentals, including algorithms, operating systems, data analysis and artificial intelligence. I graduated as valedictorian with a 3.84 out of 4.00 GPA.

My graduation work included a custom wire protocol built directly on sockets and a tweet signal/noise classifier with data collection, annotation, transformer training and a small inference application.

What I worked on

  • Algorithms, data structures and operating systems
  • Machine learning and statistical evaluation
  • Networking and protocol design
  • Software engineering and database systems

Built here

See the project
  • Tweet Noise Classifier

    Training an ALBERT model to separate signal from noise on Twitter

    For my graduation project, I trained an ALBERT-xxlarge-v2 classifier to separate useful tweets from bots, marketing and unrelated posts around a trending topic. I built the collection pipeline, a human annotation interface, Firestore persistence, the PyTorch training and checkpoint flow, and a Flask API that served the selected model for batch classification.

    • I collected topic streams, defined signal and noise labels, and built a Flet interface for reviewing and annotating tweets.
    • I fine-tuned ALBERT-xxlarge-v2 with PyTorch and Hugging Face, then loaded the selected checkpoint for inference.
    • Firestore connected collection, annotation and batch classification; Flask exposed the model through a small HTTP service.
    Read more
Sapienza University Logo

Sep 2021 - Feb 2022

Erasmus exchange

Sapienza Università di RomaEducation

A semester in Rome studying machine learning, cybersecurity and software engineering. Living and studying abroad also gave me the chance to learn Italian and work in a new academic environment.

What I worked on

  • Machine learning coursework
  • Cybersecurity coursework
  • Software engineering coursework
  • International study experience

GitHub activity

Public contributions from the past year

@akincan-kilic