Skip to main content

The next step

One sunny day in 2007, I started as engineer #6 at a scrappy little startup that I knew to be as Google for jobs.  Ten amazing years flew by, working with some of the smartest people I will ever know in life. Some highlights of work I did, that I feel really good about.

  • Tokenization and search quality improvements to Indeed's international search (China/Japan/Korea/Germany) 
  • Performance improvements to indexing and search back-end systems, that improved performance and lowered bandwidth costs. 
  • A complex re-architecture to horizontally shard Indeed's index of resumes
  • Helped grow the jobs recommendation engine through performance and ranking improvements, introducing geohash clustering and other architectural changes.
  • Implemented TLS support for Indeed's service framework
  • Built wrappers around Hystrix, to ease adoption within Indeed. 
  • Built systems for monitoring and visibility of microservices, mongo and mysql.
  • Gave four public tech talks in conferences 
  • Led a group of women to submit proposals to the Grace Hopper conference, twice. 

Most of the work I did had very measurable impact on the company.

I saw Indeed go from a little startup through to a successful acquisition in 2012.  It grew even more after that, becoming a global presence in hiring around the world, with engineering offices in five different cities around the world. I helped hire many engineers, data scientists and engineering managers into the organization. My title may not have always reflected what I did, but to me I was the "Jill of all trades" within software engineering.

While all this was going on, I faced many personal challenges including my daughter's autism diagnosis, supporting my sister when we lost lost my 13 month old nephew to a rare liver disease, and supporting my sister-in-law through a messy divorce with an abusive spouse. There were many days when I wanted to give up.

In the early days of  working at Indeed, I simply couldn't stop working because we needed both our incomes. Also, getting work authorization for immigrants via H1B is a long drawn out process, that doesn't allow for a lot of flexibility in terms of taking breaks between jobs. Eventually, I switched to a part time role at Indeed for a couple of years, till we found the right fit for my daughter in a school we really liked. I was lucky to get the support from the leadership at the company to make part-time work for me. In the later years, I worked full time because I loved it and enjoyed it, and felt that I could juggle work-life balance effectively. There was so much to do, and I was having so much fun learning new things everyday that time flew by!

Things on the personal front improved over the years too. We stopped comparing my daughter to other typically developing kids and crying about it. We are always working on helping her navigate her unique challenges, and measure progress relative to her, rather than other kids. My sister and brother in law went through a long period of grief, tried again and now have a healthy little baby boy. My sister in law's divorce came through. She moved and switched to a job she loves, and travels around the world for work.

It is easy to not rock the boat, and to keep enjoying stability, and I did that for a while. But the time has come for me to look outside of Indeed's walls to the world at large. Over the last year, I learned a lot about the infrastructure and devops space. I found myself wanting to learn about it more and play a more direct part in it. I want to understand how other organizations are transforming how they build, provision and run their applications.
I also started yearning to be the newbie again, to learn how to execute and excel in a new domain. I want to write code for the open source world. Many developers seem to have so much time and energy outside their work hours, that they work on their personal projects during their free time. I am not like that. As a mom, I have no time outside work to be able to explore OSS during my own time. I'd rather get paid for it. I talked to a few different places that met my criteria before deciding. I am joining Hashicorp, as a software engineer working on consul.

It is so hard to say goodbye to a place I helped create. I have so many supportive co-workers that I learned a ton from. It was a very tough decision to make. When I emailed one of the co-founders, Rony, after I resigned, he said "Thanks for everything you did for indeed. You were so very critical to its success. I don't think people realize how critical. ". That was so amazing to hear, and hard to walk away from.

There are a lot of exciting things about my new job, but there are a lot of unknowns too. I have to figure out how to execute well as a remote employee, and work in a very different domain. Building products for enterprises is very different from consumer facing start-ups, and I am excited to jump into it. I find myself ready to take this plunge and see where life leads me next.






Comments

Popular posts from this blog

What are your future plans? Why are you *still* a developer?

If I had a nickel for every time someone has asked me that question I'd have enough change for a year? Inspired by my friend's post here , I thought I'd write about how I ended up doing what I do now. Then I thought about it some more and decided to write about something else. Is it important to know where you are going in life? If you aren't moving forward in your career does it mean that you are doing something wrong? What does "moving up the ladder" even mean? I am going to attempt to answer these questions for myself. Its almost 5 years since I began my professional career. It has been great so far, lots of ups some downs as well. However, once in a while when I get the title question it still throws me off. It is usually my parents or well meaning relatives, sometimes friends that ask this. I have nothing much to say to them except "I enjoy what I am doing right now, haven't really thought about the future". But the truth is - I have thou...

What's your black triangle?

There is a great post from 1994 about  black triangles  in the context of building large and complex systems. You might think that 1994 sounds like the dark ages, but the principles outlined in that post do stand the test of time. Here is my favorite excerpt from that post: What she later came to realize (and explain to others) was that the black triangle was a pioneer. It wasn’t just that we’d managed to get a triangle onto the screen. That could be done in about a day. It was the journey the triangle had taken to get up on the screen. It had passed through our new modeling tools, through two different intermediate converter programs, had been loaded up as a complete database, and been rendered through a fairly complex scene hierarchy, fully textured and lit (though there were no lights, so the triangle came out looking black). The black triangle demonstrated that the foundation was finally complete the core of a fairly complex system was completed, and we were now ready t...