Economics Engineering Student → Data Engineering
I turn economic data into tested, reproducible systems with Python and SQL—then expose the evidence, limits, and engineering decisions behind every claim.
01 / Selected systems
Four focused systems. Each card states my ownership, the key engineering choice, the measured result, and the boundary between tested and deployed.
A personal inflation engine for households whose spending basket differs from the official average.
My ownership: Designed and implemented the calculation pipeline, API, persistence, tests, CI, and deployment.
Key decision: Used a Laspeyres index across 13 ECOICOP sub-indices so results remain explainable and comparable with official CPI.
An evidence-based economic detective game that turns macroeconomic reasoning into an inspectable scenario.
My ownership: Built the first end-to-end case, sourced retrieval, RAG hint agent, evaluation, FastAPI interface, and deployment.
Key decision: Kept citations and evaluation beside generation so the learning experience does not hide unsupported answers.
A medallion lakehouse for Turkish macro data, from validated Bronze Parquet to analytical marts, with a public run-evidence page.
My ownership: Built ingestion, validation, dbt/DuckDB models, API, dashboard, orchestration, run-audit ledger, and CI.
Key decision: Separated Bronze, Silver, and Gold contracts to make lineage, data quality, and failures observable.
A zero-runtime-dependency WebGL2 space-RTS engine with hand-written GLSL and a headless deterministic simulation path.
My ownership: Implemented the renderer, shaders, simulation loop, headless verification, and immutable proof artifacts.
Key decision: Stamped committed frames with engine-state checksums so visual results are reproducible rather than decorative.
02 / Live surfaces
Static-hosted builds that need no cold start. Each one opens in your browser and shows its own method, source, and limits.
03 / Verification
The evidence ledger ties public statements to immutable revisions and records limitations instead of hiding them.
Open evidence ledger →04 / About
I study Economics Engineering and build toward data engineering—connecting economic reasoning, reproducible pipelines, software quality, and simulation.
I optimize for small vertical slices, automated tests, explicit boundaries, and evidence that a system actually runs—not technology lists or unverified claims.
05 / Recruiter handoff
For data engineering internships, junior opportunities, or engineering collaboration, the fastest route is email or LinkedIn.
No résumé link is shown until a current, versioned résumé is published.