Sachin Gupta

Author
Sachin Gupta

Blogs
Sachin sees hiring through the lens of systems thinking and design operations. Their structured yet poetic approach to writing helps readers rethink how they scale teams and workflows.
author’s Articles

Insights & Stories by Sachin Gupta

From hiring pipelines to collaboration rituals, Sachin Gupta maps out ways to design intentional, high-performing organizations—one post at a time.
Clear all
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Filter
Filter

Segmentation Fault - Debugging Contest by IIIT Allahabad

Segmentation Fault was a one-of-its-kind online debugging contest conducted on HackerEarth on 22nd October 2013.

Organized by IIIT ALLAHABAD, it aimed to assess the grasping power of contestants and test their basics of C/C++/Java. Consisting of multiple choice questions covering all the fundamentals of these languages—with 30 questions in the first round and 25 questions in the second round—the event was a huge success.

This year, around 700 students registered for the contest. 400 participated in the first round, and 103 advanced to the second round from various colleges across India and abroad.

We had around 400 participants in the first round.

After the first round qualifiers, 103 made it to the second round from different colleges across India and abroad.

Here is a testimonial by the organizer:

"HackerEarth platform was very helpful to host this event and to promote it. Because of its sleek interface, the site was very user-friendly and provided the administrator full authority. With no prerequisites, it also provided a platform for those who were new to programming and wanted to learn something new. The participation turned out to be greater than expected for such a contest and helped in boosting the competition among the participants."

Deepak Agrawal
Segmentation Fault Organizer
IIIT ALLAHABAD

If you are a college looking to host such contests, we welcome you to join our growing developer community.

Email us at contact@hackerearth.com.

Join as a Python developer at HackerEarth

HackerEarth is a pretty cool place to work

Help us change the way programmers write code and get hired. HackerEarth is a tech startup based in Bangalore, India. We are building the largest platform to engage with programmers around the world. Today there is no interesting place where programmers can interact and collaborate with each other, and most importantly do one thing that they absolutely love to do — write code. In the process, we are helping companies filter the right candidates.

Being passionate programmers ourselves, this is a problem very close to our hearts and hence we are striving to solve it, and we are looking for great people to join us.

Who are we & why work with us?

An amazing team working on big problems

We are a team of 5 full-time right now, graduates of IIT Roorkee, IIT Delhi, etc., who have worked at Google, Microsoft, Amazon and contributed to high-quality open source projects like Mozilla, Fedora, MINIX3, etc. Kaushik MV — ACM ICPC world-finalist — joined us recently to further organize and synchronize our efforts in reaching out to programmers. Above all, we are a couple of geeks who love to hack and build interesting products and we invite you to be a part of it.

HackerEarth was incubated at the GSF Accelerator in 2012 and was also one of the winners of the program. Since then, we have grown and scaled quickly, increasing the programmer base to more than 40K and acquiring new customers along the way.

Challenges ahead like never before

There are challenges ahead like never before, where you will be hacking on Python & Django, scaling infrastructure, re-architecting the backend, and get to push code from the first day itself. HackerEarth is working on big problems, challenges that make you shudder at first, and is waiting for you to come and solve them. With such a small team, you will be owning huge ideas and codebases from the start. Meanwhile, the talented team will always be on its feet to help you accomplish whatever you aim for.

Your Role and Responsibilities

  • Take ownership of a product feature and build it end to end.
  • Understand issues like response time, scalability, asynchronous systems, user engagement and write code considering these paradigms.
  • Interact with programmer communities, college coding groups, open source communities and understand how to engage with them.
  • Contribute to the ways the platform can be made much more engaging and reach a larger audience.

Required Skills

  • 1 year+ experience in Python.
  • Hands-on experience in Django.
  • Understanding of how MVC frameworks work.
  • Knowledge of development on a Linux system.

We put the willingness to learn & build above anything else, so if you think you’ve got it in you, don’t let these skill requirements deter you from applying.

Desired Skills

  • Interest in contributing to open source projects.
  • Knowledge of system programming in UNIX environment.
  • Knowledge of HTML, CSS, and JavaScript.
  • Interest in writing content—tutorials, blog posts, solutions to algorithmic questions, etc.
  • Prepared to go through the roller-coaster highs and lows of a startup journey.

Job Perks

  • Industry comparable salary and equity.
  • Machine and accessories of your choice.
  • Really flexible hours.
  • If you’re sick, just stay home.
  • Movie/Gaming night outs.
  • Traveling in and around India.
  • Attend developer events and conferences for free.

We are writing tons of code, building some intense technology, and it’s a great opportunity to learn. We are backed by some awesome people in the startup community. Moreover, you get a chance to be an initial team member of a company building a global product out of India.

Apply for this position

If you’re interested, drop us an email at vivek@hackerearth.com. Please add

An open letter to our users

We would like to convey our deepest apology to all the participants of the InMobi Hiring Challenge. We messed up this one, we realize it and we regret it. Servers shot to 100% CPU utilization, page loads were excruciatingly slow, and the random 500s in the first 20 minutes disrupted what we had expected to be a smooth challenge. It was our fault, we miscalculated. We thought that 20 large instances would be enough to support the load, but we learned the hard way—when there are more than 600 people simultaneously submitting code, you need much more server bandwidth than that.

Fortunately, we had invested time in scripts to auto-launch server instances on AWS and were able to immediately fire up more instances. But as soon as we did that, we realized the database was going to become a bottleneck. Though we were able to resolve all issues within the first 30 minutes, it was still disheartening to see people trying to access the event page and not being able to do it.

We started HackerEarth with a vision of changing the way recruitment is done in the industry today. We want to eliminate all kinds of bias in the hiring process and let the code speak over all the big talk. We are building a platform where every developer has an equal chance to apply to companies with the skill they know best—coding. But we fell short of our promise this Sunday. We want to make a developer's code their identity, we want you to write code on our platform, and we want you to have absolute fun while doing it.

Ever since this crisis happened, we have invested all our resources in making sure that something like this never happens again. It's not that our platform cannot deliver—it's just that our system was not intelligent enough to anticipate the load and scale accordingly. We are young, we code fast and deploy faster, but amidst this, we made a mistake by not investing enough in testing. We had never stressed our system, never tried to understand under what load it would break down—but we are doing that now.

It hurt us badly to read the responses of our unhappy users, but we are, in a way, thankful to each and every one of you who tweeted us, reached out on Facebook, and emailed us. Though we wish we had not made so many of you angry, we are glad we got to hear from you. It has helped us realize our shortcomings and strive harder to make our platform even more robust and failure-proof. We also express our sincere apologies for the inconvenience caused to our stakeholders.

Thanks for taking the time to read this.