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. While I don’t consider myself an expert in any single domain, I always strive to do my best work. Although I started out as a frontend-only engineer, 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’ve been building CRUD apps for a while, and I’m starting to feel a bit burned out. I think it’s time for a change. I’d love to work on agentic CLI tools, editor extensions, or developer tooling that improves how engineers work, especially around observability, logging, debugging, 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 accept it and change how we approach things. I have a few preferences for how I’d like to be interviewed. Prior to LLMs, when writing code was mostly hand-driven, take-home assignments or coding something on call worked well. After LLMs, however, I believe this is mostly irrelevant. Writing code is no longer the bottleneck, but the ability to write good code and understand what you’re doing is.

We’re at a stage where anyone can make something work using LLMs, irrespective of having good knowledge about the subject. So, IMO, this makes the old way of interviewing irrelevant. If I’m being interviewed, I’d like to be asked about the fundamental building blocks of what I’m going to work with, such as understanding the tech stack, the tooling it uses, how deployments work, how the platform primitives work, and the difference between local and prod setups. IMO, understanding those things alone makes you a worthy candidate.

I’d rather be given access to one of your repos to build a feature or fix a bug, and then open a PR for it than do a take-home assignment or invert a binary tree problem. The final judgment should be based on how well I’ve implemented the task, whether I’ve adhered to the project’s code standards, covered tests, delivered a thoughtfully designed user experience, and successfully made the feature work.

If your process includes interviewing for things that I’m never going to use or work with in my day-to-day work, I’d rather not waste your time or mine, respectfully. But if you think we think alike, feel free to reach out! :)

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