Software engineer · Lahore, Pakistan

I make complicated systems easier to run.

I’m Junaid Hussnain, a software engineer with 5+ years of experience building backend products, operational tools, and the interfaces that make them understandable.

Built to be inspected

Source codeArchitecture decisionsWritingProduction delivery

Selected work

Systems with evidence behind them.

Public code, concrete decisions, and honest status. No placeholder concepts or invented outcomes.

01Product / open source

Active build · 2026

Stackline

View source

An ATS-focused resume builder for experienced software professionals that keeps personal data in the browser.

The problem

Resume tools often hide their scoring, collect sensitive career data, or export layouts that parsing systems struggle to read.

Engineering decisions

  • Local-first data and autosave
  • Explainable role and keyword checks
  • Selectable-text DOCX and PDF exports
  • Tested React domain logic with Docker delivery
ReactTypeScriptVitestDocker
02Operations platform

Active build · 2026

E-Manager

View source

A Laravel and Livewire system for finance, project, and workforce operations with granular access control.

The problem

Invoices, bank movements, expenses, worker payments, and monthly project reporting need one consistent operational model.

Engineering decisions

  • Role and module-level permissions
  • Signed exports and auditable activity
  • English and Spanish workflows
  • Feature tests around visibility and financial rules
LaravelLivewirePHPSQLite
03Developer tooling / open source

Public utility · 2026

Laravel Development Workflow

View source

A reusable engineering workflow that turns Laravel feature requests and bug reports into verifiable delivery steps.

The problem

Fast framework work can skip edge cases, authorization boundaries, realistic data, and a reliable regression loop.

Engineering decisions

  • Acceptance criteria before implementation
  • Failing tests before bug fixes
  • Realistic factories and boundary states
  • Explicit verification as the definition of done
LaravelTestingDocumentationAutomation

Engineering practice

Useful software survives the demo.

01

Model the real workflow

I start with users, permissions, failure states, and the decisions the system needs to preserve—not a list of framework features.

02

Keep operations visible

Queues, imports, reporting, observability, and deployment belong in the product conversation from the beginning.

03

Leave a maintainable trail

Tests, narrow contracts, readable documentation, and boring infrastructure make the next change cheaper and safer.

PHP / LaravelTypeScriptPythonPostgreSQLRedisDockerGitHub Actions

About

Based in Lahore
Available across time zones

The code matters. So does what happens after it ships.

I’ve spent more than five years working across web products, backend systems, automation, and the operational details that keep software useful.

My best work usually begins where a neat demo ends: permissions, imports, failure recovery, reporting, maintainability, and the decisions a team will need to revisit six months later.

A lot of that experience lives in private product work. This site is my commitment to making the transferable parts public through inspectable tools, practical engineering notes, and open-source contributions.

“I care about reducing the cost of the next change—not just completing the current one.”

Engineering notes

Writing down the decisions.

View all notes

Start a conversation

Have a difficult system or a useful idea?

I’m interested in product engineering, backend architecture, developer tooling, and open-source collaboration.

Email Junaid