Independent Engineer

Independent Engineer

Overview

Since March 2025, I have been working independently, building software systems for businesses while continuing to explore new domains, technologies, and ways of solving problems.

This chapter of my career is where everything from my previous experiences came together.

From Klimart, I learned how businesses operate.

From Justdial, I learned software engineering.

From Neohumans, I learned adaptability, product experimentation, and how to operate in uncertainty.

Working independently forced me to combine all of those lessons.

Every project starts in the same place.

An unfamiliar business.

An unfamiliar problem.

A set of constraints.

And a question:

What is the simplest system that genuinely solves this problem?

Engineering Philosophy

I enjoy solving problems that do not already have a template.

Throughout my career I have worked across manufacturing, logistics, AI products, real-time communication systems, analytics, automation, robotics experiments, and operational software.

The industry changes.

The technology changes.

The pattern remains the same.

Understand the business
↓
Find the real constraint
↓
Challenge assumptions
↓
Design the simplest viable solution
↓
Allow the system to evolve naturally

I do not believe every company needs the same architecture.

I do not believe every problem needs the latest technology.

I do not believe complexity is a goal.

Instead, I try to find the right amount of technology for the situation.

That means balancing:

• capability
• cost
• maintainability
• development speed
• future flexibility

The objective is not to build the biggest system.

The objective is to build the best solution for the problem.

Selected Systems

Kavalife ERP

A manufacturing workflow engine built for a herbal extraction business.

The challenge was understanding how material moved through a factory and translating that reality into software.

The system evolved into a process-driven ERP capable of handling QA/QC workflows, batch management, lot tracking, production execution, yield tracking, and manufacturing traceability.

Key lesson:

Understanding the business process is often more important than choosing the technology stack.

Leo Operations Platform

An operations platform built for Leo Packers and Movers.

The project started as a simple quotation calculator.

As new operational challenges emerged, it evolved into a broader platform covering warehouse management, billing workflows, employee advances, fuel tracking, and operational visibility.

Key lesson:

Complexity should be earned, not assumed.

Trainer App

A personal training platform built to solve a problem I experienced myself.

The goal was to create a simple, mobile-first system for planning workouts, tracking progress, and continuously refining training routines.

Key lesson:

The best product ideas often come from experiencing the problem firsthand.

What This Period Taught Me

Working independently has required me to become more than a developer.

Every project demands understanding:

• business operations
• user behavior
• technical constraints
• project scope
• long-term maintenance

It has strengthened my ability to enter unfamiliar domains, learn quickly, and make practical engineering decisions under real-world constraints.

More importantly, it reinforced a belief that now guides much of my work:

Software is a tool.

Technology matters.

But understanding people, processes, and business problems matters more.

Current Focus

My current focus is deepening expertise across:

• System Design
• Distributed Systems
• PostgreSQL
• TypeScript
• AI-Assisted Software Development
• Product Engineering

At the same time, I continue building systems that solve real operational problems while refining my ability to balance engineering quality, business needs, and long-term maintainability.

Looking Forward

The goal is simple.

Continue learning.

Continue exploring unfamiliar domains.

Continue solving unique problems.

Continue building systems that create meaningful business value.

And continue proving that thoughtful engineering does not require unnecessary complexity.