On the journey of tough problems

Finding a computer programmer job was the first professional problem I faced. First, I had to make a resume listing all programming languages that I knew, and projects I had worked on. Second, I emailed over fifty companies. I told them about my interest in working for them. Third, some of them got back and told me to do an interview. Fourth, I spoke to a group of 3 to 6 people at various companies who had gone through a similar process as me. One company was kind enough to consider me worthy of giving a job. Finding a job without job finding skills felt magical. I never understood then how it all worked. I now understand the magic a little better.

Exploring and discovering the problem space is part of problem-solving. Not being able to connect the dots between actions and results is frustrating. The way we view our problems plays a critical role in what actions we take. The actions we take lead to our development. What was the last problem you had? How did you feel when you first encountered it? What actions did it take to get resolved? I’ll share my perspective on problems that I’ve faced in life.

I started a company to create maps for self-driving cars. All I knew when I started was how to solve problems with code. I had to learn the rest. Few people attempted to solve this unique problem. Most tough problems lie at the intersection of various disciplines. I lacked knowledge about the car industry, robotics and map-making. Lacking knowledge causes anxiety. Where do I start? What do I do first?

How do I maximize the impact of my actions on the company? The impact is increased revenue, reduced costs, and growth in the customer base. To maximize impact, I had to choose what problems to focus on. Problems I focussed on were the problems that got solved.

Let’s look at my problems laundry list again. The car industry, robotics, and map-making. I had to pick my first problem. I decided to build an interactive tool to visualize the 3D maps for point cloud maps in a week. Here's why I picked that problem.

  1. Existing skills: Using my software development skills would be simpler. I can get initial results in a few hours to a week.
  2. Unique advantage: Robotics professionals would not build web-based map data visualizations.
  3. Fast Feedback opportunity: Seeing the custom-built maps would enhance customer and internal conversations.


The goal was for me to reduce the scope of the problem to something actionable in a limited time. I lacked skills in automotive business development. One of my cofounders tackled that. I did not have a unique advantage in robotics. I reached out to my network to find someone. Feedback on map quality would be hard to get if we only shared a file or a screenshot with a customer. This insight was my hook to all other future work I did.

How did I decide that this was the right scope? I reduced the scope of the problem to a point where my ambition drove me and not my fear. This enabled me to take action. My actions translated into learning towards my bigger goal. Time boxed actions are a superpower. They gave me honest feedback about my work. Did my work meet the quality bar? Did I take on too much or too little? This sharpened my iteration process. It helped me solve problems with greater ambiguity in the future.

I needed to grow into an effective problem solver to tackle bigger problems. I am not even capable of defining all problems well. Growing up school taught me how to solve well-defined problems. The real-world problems lack a clear definition.

The best way for me to deal with this ambiguity was to take action and learn from others around me. Starting a company? Talk to the best. Read more about the processes. Find your inspiration, living or dead. Understanding the minds who came before you teach you about their thinking process. The mind is the toughest to master

"The important thing is to take that first step. Bravely overcoming one small fear gives you the courage to take on the next" - Daisaku Ikeda


Be brave and take your first step. Most people lack the bravery to take the first step. The courage I developed in starting a company translated to other areas. It helped me abandon my fear of rejection. That led me to start this blog. I overcame the fear of never getting fit and started working out. Each of us can enjoy our problems with a dose of courage and lots of action.


PS: For those who are curious what the maps that I created looked like.

Building Confidence

To startup or not to startup? This is the million-dollar question that I asked myself every couple of weeks through my 20s. How do I decide? What are the criteria? Will the idea be good enough? Am I good enough? Will I be able to execute? So many questions and no answers. Every day potential entrepreneurs wake up feeling I am not good enough. Building confidence to take that plunge is tough. Here’s a little insight into my journey.

In the competitive job market of India, a job in the field of your study after graduation is a privilege. I had an internship in the final semester of college and no job lined up. I wanted to work at a startup. My definition of a startup was a company that had few employees. I got an offer from a firm that had under 20 employees in 2011. The highlight of my job was I got to work with computers and didn’t have to badge in and out.

My company was building a product that needed someone to go and showcase the product. I volunteered. I learned later that I had assumed the role of a part-time sales engineer. I once told the customer, “You should understand our product. It’s not our fault. You are at fault." I was proud of what I had said and done. In reality, I had failed. All the effort of my team and myself over the past few months to get the product to a point to showcase it felt wasted. I’m grateful to my company for giving me space to learn a lesson and not firing me for it. In a close-knit team, it’s heartbreaking to see your work not convert into revenue. I later learned that this was the hard reality of sales.

I arrived in Silicon Valley in early 2013 to study Software Engineering. I felt that I could assemble a computer gathering parts from companies on the US-101. It is a well-funded state-of-the-art technology playground. A tiny fraction of companies become household names worldwide. Most of them either die in oblivion or get acquired. The other big thing for computer programmers here is a hackathon, a marathon of hacking.

Put a group of technologists for 12-24 hours and feed them pizza.  You lose sleep, consume sugar, caffeine, and carbs. You fuse your brain with the computers to build interesting things. It's the closest to the singularity you can get to. I built an app to control your music player with your brain waves (mood). I met my future co-founder building a party assistant to show a dancing skeleton of you to the attendees. I was able to control a computer to do interesting things. This led me to my first job in the USA.

Click-clack-click-clack on the keyboard in front of a computer was a large part of my job. I found myself immersed in writing code for customers I would never see in my life but they paid money to my company. That money after exchanging hands would result in me getting paid. This in turn would let me pay my student loans and bills. A big part of my learning was how was potential customer value turned into revenue for the company. This led me to challenge myself a step further.

Starting a company was not an overnight decision. I needed confidence and fallback options played out in my head. First, I had the confidence to find a job if the startup didn’t work out. I also needed to sustain myself for a certain time frame without a salary. I had never built a new product and sold it to customers. I did not understand the market of my company (automotive technology). I had no experience in hiring and managing people. I also had no idea how to fundraise. To do something outside your comfort zone, you need to understand your comfort zone well. With this information, I clarified the risk I was taking with my family and co-founders. A shared understanding of your personal and professional risks with your founding team is crucial. This helps make decisions when conditions are not favorable. I was fortunate to build that trust early and it serves me well to this day. 

Building confidence to take on something ambitious is an iteration. You start with none, take action and then you get some. Confidence is not something you have when you are doing something for the first time. The big hairy ambitious goals that we strive for are all done for the first time. Each time you take a small step you get the confidence to do it better. The key is to build on your prior confidence and keep going for your ambitious goals.

What about starting a company? Ask yourself the following questions


How do you sell a product to someone else?

How does your favorite company make money?

What's your process to build something that will make money?


It's important to assess facts on your own. Every person associated to a startup is taking some risk, but not the same one. The VC is taking a financial risk, the founder is taking a time and money risk. Early team members are taking career and financial risks. There is only so much risk you can understand upfront. The best way to learn is to take the plunge. I want to leave you with my favorite quote on courage


No matter how wonderful our dreams, how noble our ideals, or how high our hopes, ultimately we need courage to make them a reality. Without action, it’s as if they never existed. - Daisaku Ikeda