Chief Technology Officer
CurrentAfter having scaled from 0 to 1, and 1 to 10, we are on our journey to a 100. As of now, we have just over a dozen services with 6 hot codebases, and a lean team which scales our platform to a battle-tested billion API calls a day, and concurrency just shy of a million.If you are a CTO who thinks their job is chaotic, I can help you find harmony (if you are serious, DM me here or @sankalp_sans on Twitter).How?As a CTO, I have 3 main key focus areas – going wide, going deep, and going around.Going wide – having a 20k feet view of the org often gives clarity around seeming unnoticed and ignored patterns. This helps me eliminate fluff work, projects with no consequences, or projects with insufficient direction. I believe killing poor choices early in their lifecycle in an org, is the biggest leverage any leader can provide.Going deep – once you've identified and scoped in work (hopefully that scope is within what your team can deliver), you got to ensure your team also aces this. This is where I roll my sleeves up, and get down to the T to help get patterns right, help break new grounds, and often times come up with a new piece of tech pattern, which guides the team of engineers to follow.Going around – If you are doing it right, your teams will be smack in the middle of execution, and in a state of flow, and now it becomes your job to help them figure out the upcoming goals. You go "around" the immediate needs and targets and try to play the fortune teller with no scientific enough crystal ball to rely upon. This means you will have to spend countless hours with vendors, partners, often times with your terminal, establishing a largely feasible direction. This is where I help eliminate the "fog of war" for our gallant troops. It also means that often time you will come up with an impossible problem statement and also help your team with very good first steps to scale that mountain of an ambition.