01 / INTRODUCTION

BASED IN INDIA / NEPAL
OPEN TO REMOTE WORLDWIDE

AYUSH KARN - SOFTWARE ENGINEER

Engineering
complete systems.

I design and build software, cloud, data and AI systems. I turn complex problems into reliable products and platforms.

SCROLL TO DISCOVER
02THE SYSTEMSCROLL + DRAG TO EXPLORE

01 / PROBLEM

Frame the problem before the solution.

Align users, goals, constraints, risks, and success measures before choosing technology or committing to a build.

ENGINEERING SIGNALA testable problem statementBUSINESS VALUELess waste and faster alignment

02 / ARCHITECTURE

Make the important tradeoffs visible.

Define boundaries around scale, coupling, security, reliability, cost, and change so the system can evolve safely.

ENGINEERING SIGNALExplicit tradeoffsBUSINESS VALUESafer scale and integration

03 / BUILD

Turn the design into working software.

Connect the interface, APIs, services, tests, observability, and delivery pipeline into a product people can depend on.

ENGINEERING SIGNALObservable deliveryBUSINESS VALUESoftware that is easier to change

04 / DATA

Make the data trustworthy.

Move from ingestion through cleanup, transformation, quality checks, validation, and lineage without losing meaning.

ENGINEERING SIGNALTraceable transformationsBUSINESS VALUEDecisions backed by evidence

05 / INTELLIGENCE

Add intelligence after foundations.

Connect knowledge, context, embeddings, retrieval, models, and evaluation so AI answers stay useful and grounded.

ENGINEERING SIGNALEvaluated retrievalBUSINESS VALUEUseful AI people can trust
LIVE ARCHITECTUREDRAG TO INSPECT
01USERSREADY
02GOALSCONNECTED
03CONSTRAINTSREADY
04CURRENT FLOWCONNECTED
05RISKSREADY
06SUCCESS METRICSCONNECTED
ACTIVE LAYERPROBLEM FRAME
CHAPTER 01PROBLEM

A testable problem statement

03SELECTED WORKVIEW ALL PROJECTS ↗

Selected work.

Systems built to solve real problems across software, data, cloud, and intelligence.

04CAPABILITIESWHAT I BUILD

From idea to
infrastructure.

I work across layers, connecting product thinking with the engineering depth required to make systems last.

01

Software Engineering

Backend systems, REST APIs, web applications, service architecture, and distributed systems.

+
02

Architecture & Cloud

Solution architecture, integrations, scalable platforms, cloud systems, and enterprise design.

+
03

Data Platforms

Pipelines, lakehouse architecture, transformation, metadata, lineage, and governance.

+
04

AI Engineering

LLM applications, RAG, local AI, document intelligence, and assisted workflows.

+
PythonC# / .NETTypeScriptReactAzureDatabricksSQLDuckDBDocker

HP INC.

Building at
enterprise scale.

Software Engineer II

2023 - Present

Building enterprise platforms across software, data, cloud, and architecture.

Solution ArchitectureEnterprise Data PlatformsMetadata & LineageCloud Integration
SELECTED IMPACT

Designed integration workflows connecting ERP, warehouse, lakehouse, and metadata ecosystems. Improved visibility into enterprise data flows while preserving ownership and operational context.

Software Engineer

2021 - 2023

Developed services and data products connecting operational systems with analytical platforms.

Backend ServicesData EngineeringPlatform IntegrationEngineering Operations
06CURRENTLYUPDATED 2026-08-15
BUILDING

Local Finance Intelligence

A private, local-first system for understanding personal financial data.

LEARNING

Advanced RAG architectures

Evaluation, retrieval strategy, and dependable agentic systems.

EXPLORING

AI-native developer workflows

New interfaces between human intent and software creation.

07ENGINEERING JOURNALALL WRITING ↗

Thinking,
made visible.

Notes on building dependable systems and making complexity easier to reason about.

08HOW I THINKENGINEERING PRINCIPLES

Good systems are
understandable systems.

01

Design systems, not isolated features.

Think about how components interact before optimizing individual pieces.

02

Understand before abstracting.

Good abstractions usually appear after understanding the underlying problem.

03

Reliability beats cleverness.

Production systems should be understandable, observable and predictable.

04

Privacy is an architectural decision.

Data boundaries belong in the design conversation from day one.

DIGITAL ENGINEERING SKETCHBOOK

Small experiments.
Useful questions.

Prototypes, visualizations, and technical studies that explore ideas before they become systems.

10ABOUTTHE HUMAN IN THE SYSTEM

HOW I OPERATE

01UNDERSTANDFind the real constraint02DESIGNMake boundaries visible03BUILDShip the useful core04LEARNMeasure and improve
CURRENT FOCUS: RELIABLE AI SYSTEMS

I like building things at the intersection of software, architecture, data, and intelligence.

My work moves between code and systems thinking, understanding a difficult problem, finding the right boundaries, and building something people can trust.

Outside engineering, I practice traditional drawing and watercolor, a different way of learning to observe carefully.

BASED BETWEEN INDIA & NEPALREMOTE-FRIENDLY · SELECTED HYBRID
MORE ABOUT ME ↗

HAVE AN INTERESTING PROBLEM?

Let's build something
worth understanding.