Sifen.
open to work · full-stack/ 2026

I build

software

that ships, and stays shipped.

I'm Sifen, a full-stack developer in Addis Ababa, Ethiopia. I deliver TypeScript products end-to-end, from API and auth to motion-tuned UI, and publish the libraries I wished existed.

currentlyshipping at clientreach.ai
basedAddis Ababa, Ethiopia
stackts · next · node · bun
01/ about

A generalist who keeps shipping specific things.

I started writing code to figure out how things actually worked: small servers, scrapers, half-finished games. That curiosity turned into a career. Today I build full-stack TypeScript products with the same instinct: understand the moving parts, focus on what matters, and ship something that holds up in production.

I work end-to-end, from design tokens to deploy pipelines, with a preference for the boring middle layer most teams underinvest in: auth, sessions, data fetching, error states. The decisions that quietly determine whether a product feels solid or fragile.

what i'm focused on

  • 01Full-stack TypeScript delivery: frontend, API, data layer.
  • 02Auth, sessions, OAuth: done right, once, then reused.
  • 03Design-engineering: Figma → motion-tuned, accessible UI.
  • 04Developer tooling: skills, libraries, starters.
02 / signal

loading live GitHub data…

03/ stack

The tools I reach for, grouped honestly.

No buzzword soup. These are the things I've actually shipped to production this year, organized so you can scan the layer that matters to you.

Languages

  • TypeScript
  • JavaScript
  • Lua
  • Bash
  • SQL
  • Go

Frontend

  • React
  • Next.js (App Router)
  • Redux Toolkit
  • TanStack Query
  • Tailwind CSS
  • Framer Motion
  • Expo

Backend

  • Node.js
  • Express
  • Fastify
  • Hono
  • Bun
  • REST
  • JWT / OAuth
  • Zod

Data & infra

  • MongoDB
  • PostgreSQL
  • Mongoose
  • Upstash QStash
  • Vercel
  • Docker

Workflow

  • Neovim / LazyVim
  • Hyprland / Omarchy
  • Git
  • GitHub Actions
  • Claude Code
04/ selected work

Things I've built, picked carefully.

Six projects I'd point a recruiter or future collaborator at first. Each one shipped, and each one has the engineering decision I'm proudest of called out in the case study.

05/ notes

Engineering notes worth writing down.

Short essays on the engineering decisions I keep making: auth as a library, client state vs. server cache, runtime-aware tooling. Updated whenever I notice a pattern repeat across projects.

06/ contact

Have a project to ship?

I'm currently open to full-stack roles, freelance engagements and product collaborations. Fastest replies come through email or Telegram.