Hello, Farmaan here! Welcome to my professional profile. I’ve been working as a Software Engineer for 4 years and have worked with multiple startups. I started out as a frontend-only engineer, but I now see myself as a well-rounded Software Engineer, comfortable handling challenges across the stack. If you’re looking for someone like that, I might be your guy. Below are a few things about me that I think you might find interesting.

I consider myself good with all things TypeScript. Whether it's writing client- or server-side code, building data-only APIs or crons, or stitching all of these together.

I also care deeply about the quality of what I build, from the codebase and developer experience to the user experience. Performance, loading times, and good UI feedback are all important to me, and I always try to build something I would want to use myself.

I'm also decent with relational and non-relational databases. I know these things matter less and less as LLMs progress, but I still believe a fundamental understanding of them is required to make the end result both effective and efficient.

I enjoy building product applications and want to keep doing that, but I'd also love to work on agentic CLI tools, TypeSafe SDKs, editor extensions, or developer tooling that improves how engineers work, especially around observability, logging, debugging, agents, sandboxes and understanding system behavior. I'm particularly interested in tools that reduce friction, and make the developer experience better.

We’re currently going through the biggest shift software engineering has ever seen, and it’s important that we change how we approach interviews.

Prior to LLMs, when writing code was mostly hand-driven, take-home assignments or coding something on a call worked well. Today, writing code isn’t the bottleneck. Understanding what you’re doing and producing good code is.

I’d prefer interviews that focus on fundamentals such as the tech stack, tooling, deployments, platform primitives, and the differences between local and production environments.

Ideally, I’d rather be given access to a repository to build a feature or fix a bug and open a PR than solve algorithm problems or do take-home assignments. The evaluation should be based on how well the task is implemented, whether project standards are followed, tests are covered, and the feature actually works.

Got an opportunity? Feel free to reach out. I’m always up for building cool things and having interesting conversations.