Skip to content
Theme
00INTRO

Aayush Yadav

Software engineer — Tokyo, Japan

What have you actually shipped?

[+] Available from December 2026AY
01ABOUT

About

AI-focused software engineer in Tokyo. Two years building RAG and LLM systems for Japanese public-sector and construction clients.

  • RAG and LLM systems in production, not demos (done)
  • Retrieval pipelines — chunking, hybrid search, reranking (done)
  • Document extraction from construction and tender PDFs (done)
  • Geospatial data applications and map visualisation (done)
  • Mostly Python and TypeScript (done)

  • Requirements definition through design, build and test (done)
  • Release and maintenance — including whatever breaks after launch (done)
  • Full-stack when the project needs it (done)
  • Working directly with client stakeholders (done)
  • Agile teams of four to six (done)

  • English — native (done)
  • Hindi — native (done)
  • Japanese — professional working proficiency (JLPT N3, Dec 2025) (done)
  • Spec discussions run in both English and Japanese (done)
  • Multicultural teams, on-site with Japanese clients (done)

  • Permanent in-house engineering role in Tokyo (done)
  • Full-stack, applied AI, or cloud (done)
  • Available from December 2026 (done)
  • Currently in Japan on a valid work visa (done)
TAP EACH ROW TO EXPANDWHO
02EXPERIENCE

Experience

From a remote internship to on-site delivery for Japanese public-sector clients, in about three years.

001[DONE]

Hevonic.AI — Software Developer Intern

  • AI interview preparation platform, used at NYU (done)
  • Built the cover letter and resume generator end to end (done)
  • Caching, SEO and image work to cut page loads (done)
  • Next.js, Redis, MongoDB, AWS (done)

JUL 2023 – JAN 2024

002[DONE]

Human Resocia — Software Engineer Intern

  • Xreport invoice and reporting package, feature extension (done)
  • Frontend ~60%: plan management, dashboards, auth (done)
  • Backend ~40%: Excel and PDF report generation (done)
  • React, Django, Node.js, MySQL (done)

JAN – JUN 2024

003[DONE]

Japanese language training → relocation to Japan

  • Run in parallel with the internship, remote from India (done)
  • Relocated to Japan on a work visa (done)
  • JLPT N3 (Dec 2025) (done)

JAN 2024 – JAN 2025

004[DONE]

Suntec — Frontend Engineer

  • Fleet and vehicle data platform, on-site Nagoya (done)
  • Driver and operator modules, auth flows, dashboards (done)
  • Real-time vehicle views in Apache ECharts (done)
  • Video playback and file transfer over AWS Amplify and S3 (done)

FEB – MAY 2025

005[IN PROGRESS]

Pacific Consultants — Software Engineer

  • DX projects for construction and public infrastructure (done)
  • Built the team's first production RAG assistant (done)
  • Requirements definition through to maintenance (done)
  • Client meetings conducted in Japanese (done)

JUN 2025 – PRESENT

VIA HUMAN RESOCIA — ON-SITE AT CLIENT PROJECTSEXP
03SKILLS

Skills

What I have shipped with, grouped by what it is for. No self-rated percentages — the projects are the evidence.

AI & Machine Learning

  • Retrieval-Augmented Generation (done)
  • Large language models (done)
  • LangChain (done)
  • OpenAI API (done)
  • Prompt engineering (done)
  • Function calling and tool use (done)
  • Embeddings (done)
  • Chunking and reranking (done)
  • Retrieval evaluation (done)
  • OCR pipelines (done)
  • Self-hosted and local models (done)

Search & Retrieval

  • pgvector (done)
  • Vector search (done)
  • Semantic and hybrid search (done)
  • Index tuning (done)
  • Retrieval pipeline optimisation (done)

Languages

  • Python (done)
  • TypeScript (done)
  • JavaScript (done)
  • SQL (done)
  • Bash (done)
  • C++ (done)
  • Java (done)

Backend

  • FastAPI (done)
  • Node.js (done)
  • Express.js (done)
  • Django (done)
  • Flask (done)
  • Spring Boot (done)
  • REST APIs (done)
  • Async and multithreaded processing (done)

Frontend

  • React (done)
  • Next.js (done)
  • Vue.js (done)
  • Vite (done)
  • Tailwind CSS (done)

Data

  • pandas (done)
  • NumPy (done)
  • PyMuPDF (done)
  • PostGIS (done)
  • QGIS (done)
  • Mapbox (done)
  • MapLibre (done)
  • Apache ECharts (done)

Cloud & DevOps

  • AWS (done)
  • Microsoft Azure (done)
  • Docker (done)
  • GitHub Actions (done)
  • CI/CD (done)
  • DigitalOcean (done)
  • Vercel (done)
  • Cloudflare (done)

Databases

  • PostgreSQL (done)
  • MySQL (done)
  • MongoDB (done)
  • Redis (done)

Certifications

  • AWS Certified Cloud Practitioner (2023) (done)
  • JLPT N3 (2025) (done)
  • Ethnus MERN Full Stack (2023) (done)
EVIDENCE IS IN THE PROJECTS, NOT A PERCENTAGESKL
RESULTSFrom delivered work, not estimates
hours / year
1,400hours / yearof manual document work removed by retrieval tuning alone.
months
2monthsfrom sandbox to daily production use, over ~400,000 documents.
hour, was days
<1hour, was daysto prepare a deck, once the generator was in.
latency, perceived
40%latency, perceivedcut by token-level streaming in the chat assistant.
[+] EACH FIGURE IS TRACEABLE TO A PROJECT BELOWNUM
04PROJECTS

Projects

Six builds, led by the ones with numbers attached. Most are client work delivered on-site in Tokyo.

001

Production RAG assistant

Pacific Consultants 株式会社

LangChain and LLMs over roughly 400,000 construction and tender documents, covering search, summarisation and Q&A. Out of the sandbox and into daily use in about two months; retrieval tuning alone took roughly 1,400 hours of manual document work off the year. Python and Express behind it, React and TypeScript in front, Docker out to DigitalOcean with Cloudflare ahead of it.

Most of the accuracy work turned out to be retrieval, not prompting — chunking strategy, hybrid search over pgvector, and a reranking pass, measured against an eval set built from real user questions.
  • Python
  • Express
  • React
  • TypeScript
  • Docker
  • DigitalOcean
  • Cloudflare
Retrieval pipeline
Retrieval-augmented generation pipelineConstruction and tender documents are chunked, embedded and stored in a vector index. A question is embedded and rewritten, matched against that index by hybrid search with a reranking pass, and the retrieved passages are passed with the question to a large language model, which returns an answer citing the source documents.INGEST — OFFLINETender +construction PDFsChunkeroverlap + metadataEmbeddingsbatchVector index+ keyword fieldQUERY — LIVE~400k docsQuestionEmbed + rewriteRetriever — hybrid + reranktop-k passagesLLM — grounded answercites source documentsback to the asker, with citations
002

AI presentation generator

MLIT / 国総研

Staff describe what they need in a chat, and the system assembles an outline, body text and slides. Deck preparation went from days to under an hour. Existing documents are referenced automatically so the substance stays consistent between authors. Azure Web Apps and Functions, with Application Gateway and a virtual network restricting the public route.

  • Azure Web Apps
  • Functions
  • Application Gateway
  • VNet
003

MapAI

Otaru Canal · Kashiwa City

LLM-driven querying and visualisation of geospatial data, built to address overtourism congestion. Transit, rail, ferry, event, weather and retail data merged and normalised into 250m mesh cells, with congestion forecasting on top. MapLibre for the map, PostGIS on Azure and Neon, QGIS for preparation.

  • MapLibre
  • PostGIS
  • QGIS
  • Azure
  • Neon
004

Tender PDF extraction pipeline

Automated extraction from government tender PDFs into structured CSV and Excel. PyMuPDF for parsing, multithreading for throughput, and region-aware rules for the long tail of format differences between prefectures.

  • PyMuPDF
  • Multithreaded
  • CSV / Excel
005

ManiKani

Spaced-repetition learning SaaS

A subscription learning app built to production standards: a scheduling engine, RAG-backed generation of personalised mnemonics, and progress tracking. Next.js on the front with a separate FastAPI service doing the AI work, PostgreSQL and pgvector for retrieval, Redis for sessions and rate limiting, Stripe for billing.

  • Next.js
  • FastAPI
  • PostgreSQL
  • pgvector
  • Redis
  • Stripe
006

AI chat assistant

Conversational assistant with token-level streaming, persistent multi-session history and per-user rate limiting. Streaming alone cut perceived response time by around 40 percent. A prompt-template layer keeps conversation context inside the model's token budget.

  • Streaming
  • Prompt templates
  • Rate limiting
NUMBERS ARE FROM DELIVERED WORK, NOT ESTIMATESWRK
05CONTACT

Contact

Open to permanent in-house engineering roles in Tokyo from December 2026.

Location
Tokyo, Japan
Available
From December 2026
Documents

Resume and 職務経歴書 available on request, along with a 履歴書 if your process needs one.

Send a message

For a role, a contract, or a question about anything above. I read every message and reply in English or Japanese.

At least 20 characters.

Your name, address and message are stored so nothing gets lost, and sent to me by email. Nothing else is collected and nothing is shared.

CURRENTLY IN JAPAN ON A VALID WORK VISAEND