Farhat IqbalTurning raw ideas into calm interfaces and resilient systems.

Every layer.     

When something works, I need to understand why. That instinct shapes how I build, from how an interface feels to what the system does underneath.

Full-Stack Dev & Product EngineerOpen to work
Resume
01/How I Think

Understand the problem.
Build and test it.

I start with the task and the people using the product. I design the interface, build the software behind it, and test how they work together.

Start with the people using it.

Understand the task before deciding what to build.

Make the interface easy to follow.

Use clear language, familiar patterns, and useful feedback.

Build for everyday use.

Consider loading, errors, accessibility, and maintenance.

Check the result and improve it.

Test the work, listen to feedback, and refine the details.

Portrait of Farhat Iqbal

From thought to form

An eye for detail.
An instinct for depth.

  1. I / Seeing

    Learning to look.

    Composition, type, and the quiet difference a small decision makes.

    Visual design & editorial craft
  2. II / Building

    Giving ideas form.

    Turning that attention into interfaces and software people can use.

    Selected products
  3. III / Understanding

    Going beneath.

    Following the interface down to the hardware and systems that make it possible.

    The hardware bridge

From intention to interface

Give the idea
somewhere to live.

The thinking becomes the work.↓

Selected work

Selected projects.

Systems, hardware,
and product craft.

oorbE

20-module decoupled enterprise Android architecture with Shizuku IPC binder daemon, UID 2000 execution, and hardware AES-256-GCM Keystore security.

Kotlin / Jetpack Compose / Gradle / Shizuku

Case study
MODULES20+ Decoupled Gradle
oorbE Interface Mockup
20 Modules · Shizuku IPC · Keystore AES
1
oorbE: 20-module decoupled enterprise Android architecture with Shizuku IPC binder daemon, UID 2000 execution, and hardware AES-256-GCM Keystore security.

“Design is not decoration.It is the last layer of a system that already works.”

02/The Path

It started with graphics.
Then down to the metal.

PHASE 01

Design

Photoshop, Illustrator, InDesign, Canva. Learned that composition is an argument, not decoration.

Creative Suite & UI
FigmaUI & Systems
PhotoshopRaster & Depth
IllustratorVector Precision
InDesignEditorial Grid
LightroomColor Balance
CanvaRapid Brand Systems
Spatial & Geometry
Blender & UnityMesh & Game Assets
Unity EngineSpatial Environments
Three.jsWebGL Canvas
Cycles / EeveeRaytracing
GLSL ShadersMath Lights
Spatial MeshCoordinate Space
PHASE 02

3D & Space

Blender & Unity. Learned that space, light, and depth are decisions that change what things mean.

PHASE 03

Systems

Linux, Windows & Hardware mods. Understood what the kernel does while the interface looks calm.

Core OS & Hardware
Arch LinuxDaily Driver
Linux KernelHAL & Syscalls
WindowsNT Kernel & WSL2
Bash & ShellAutomation
HyprlandWayland Compositor
Hardware ModsSilicon & Servers
STACK ·
Next.js & ReactUI & Web Core
Vue.jsReactive Core
TypeScriptType Safety
KotlinJetpack & Gradle
React NativeMobile Platforms
Tailwind CSSDesign Tokens
PHASE 04

Full Stack

React, Vue, Go, Python & PostgreSQL. The designer and the systems engineer are the same person. No handoff.

PHASE 05

AI & Systems

Autonomous pipelines. Tool-calling protocols. Knowledge graphs. Moving from writing static syntax to architecting self-directed software engines.

Intelligence & Pipelines
n8nWorkflow Automation
MCP ProtocolsTool-Calling Bridges
Agentic LoopsAutonomous Runtimes
Knowledge GraphsOntology & Memory RAG
Model GatewaysInference & Latency

An eye for form.A mind for systems.

Farhat Iqbal in natural light in Kashmir
Farhat Iqbal21 / Srinagar

A bit more about me

I like knowing
how things work.
Then making them better.

I’m Farhat, a 21-year-old designer and systems engineer from Srinagar, Kashmir. I work across visual design, product interfaces, and the software underneath them. I’m interested in the whole experience: how something feels to use, how it behaves, and how it holds up in the real world.

My practice grew from design into 3D, web development, Android, and Linux. That range shapes how I work. I can move from typography and interaction to application architecture, trace a problem down to its source, and bring the details back together as one product.

Away from the interface

I experiment with hardware, build tools for my own workflow, and keep a second brain to connect what I learn. Curiosity usually starts the project; attention to detail finishes it.

Let’s build something considered.

Outside the screen / A few things I return to

The same curiosity.A different medium.

Looking closely. Making by hand. Taking things apart.
Different ways of keeping the eye—and the mind—open.

Whatever the medium

Make it mean something.