Software engineer · Open to opportunities

I learn by building real systems.

I’m Abhishek, a software engineer working across backend systems, infrastructure, and developer tools. I build useful software, solve the hard parts, and share what I learn.

01 / Selected work

Things I’ve built.

These projects show what I build, how I make decisions, and what I learn when ideas meet real constraints.

PROJECT 01 Active

Rust desktop application

open-mpv

I built open-mpv as a fast, minimal photo and video viewer for GNOME on Wayland. It opens local files directly, with no media library, account, telemetry, or background service.

WHAT SHIPPED
  • 01

    View photos, animated images, SVGs, and videos in one window.

  • 02

    Zoom, pan, rotate, go fullscreen, use subtitles, and move through folders.

  • 03

    Trash files with undo, rotate JPEGs without quality loss, and add markup without changing the original.

  • 04

    Install it on Fedora 44 through an x86-64 RPM release.

  • Rust
  • GTK4
  • GStreamer
  • glycin
  • Wayland
PROJECT 02Paused · learning project

Version control system

Fervion

I built Fervion to explore a different model for version control. It is an API-first, offline-capable VCS built around content-addressed storage, encrypted data, and services written in Go and Rust.

Explore the architecture
USABLE LOCALLY

The object engine, APIs, refs, operation logs, encrypted storage, offline queue, and promotion flow work locally.

WHY IT STOPPED

I stopped because a non-Git model could not fit GitHub’s ecosystem without weakening the idea or rebuilding too much infrastructure.

NOT PRODUCTION-READY

Identity, attestation, multi-replica deployment, and offline conflict handling are unfinished.

  • Go
  • Rust
  • PostgreSQL
  • S3

02 / Experience

What I’ve worked on.

I’ve worked on a real product with backend, infrastructure, and delivery constraints.

FEB — AUG 2026

GODIGICOM TECHNOLOGIES · SARWAM

Founding Backend Engineer

I worked on SARWAM’s backend during its founding phase, helping turn an early product direction into working software. My work covered backend implementation, infrastructure decisions, and delivery while the product was still taking shape.

ROLE FOCUS
  • Backend systems
  • Infrastructure
  • Product delivery

03 / Capabilities

What I use to build.

Tools change, but the engineering problems stay the same.

02

Systems

I work with storage models, local-first workflows, performance, resource ownership, and native Linux applications.

RustLinuxConcurrencyGit internals
03

Infrastructure

I use containers, cloud infrastructure, CI/CD, orchestration, secrets, and monitoring to ship and run software.

DockerAWSKubernetesCI/CD
04

Data & Delivery

I work with PostgreSQL, object storage, testing, automation, monitoring, and technical documentation.

PostgreSQLS3PrometheusGitHub Actions

04 / About

I like finding out how things really work.

I learn best when I build something real. That is when APIs need boundaries, files need safety, services need monitoring, and product ideas need trade-offs.

I keep going past the tutorial, solve the parts that break, and write down why I made each decision. That helps me learn and makes the work easier for others to understand.

05 / Contact

Have something useful
to build?

I’m open to software engineering roles, internships, contract work, and open-source collaboration in backend systems and infrastructure.

Find me on LinkedIn or GitHub.