Acing the MLH Fellowship selection rounds
Tags: opensource, beginners, productivity, programming
Published: 2022-02-02 06:28:42

Since my selection, I have received a lot of queries regarding my [MLH](https://mlh.io/) Fellowship journey and tips and tricks to get into the fellowship. Here, is an attempt to answer those queries and express my gratitude to this amazing program. 

### The start for me 🙈
The first hackathon which I took part in was [Hack The Mountains](https://www.linkedin.com/company/hack-the-mountain-s/) which was powered by MLH. I was in my sophomore year when I first came to know about MLH and then it took me another 6 months to know about the MLH Fellowship. But don't worry, you don't have to wait that long!🙈

### How MLH Fellowship started 🧐
Due to the pandemic, many students in the community lost their internships and jobs. So, MLH launched an educational program called MLH fellowship to help student developers get hands-on experience. The [MLH Fellowship](https://fellowship.mlh.io) is a remote internship alternative for aspiring technologists. You can spend 12 weeks for main fellowship or 3 weeks for prep fellowship while building your skills by collaborating on real-world projects. The fellowship is powered by **GitHub, Meta, Adobe, AWS, American Express, Indeed** and many other industry players.

### The Application Process ✨
The first step is to check if you're eligible for the fellowship which you can check from [here](https://fellowship.mlh.io/faq). Once you are done, you can proceed to the initial application. From this point onwards, I'll be giving a lot of tips and tricks that are solely based on my thoughts and experience.

The initial application tests you both technically and intellectually. You will be asked to submit a code sample, and I would recommend you focus more on the quality of the project because you will be asked questions based on it in the following interviews. You must make sure not to submit someone else's code. The project you submit should be unique in terms of idea or implementation. Submitting one file code or algorithm implementation of a particular DSA problem would not be recommended. It is **NOT necessary** to **submit a project** in the application if you have an awesome Pull Request, it works. The admission team is more interested in knowing _what you have learned_ in the process and _how it is unique_.  A lot of people wanted to know the project I had submitted so here you go, to know more about it refer [here](https://dev.to/aniket762/empowering-everyone-to-code-with-google-s-eye-49e9).

{% github Aniket762/playground%}

The code sample shows your technical expertise and the behavioural questions focus on showing your interest in the program and your enthusiasm for the community.

Break down the essay questions and write things that show your interest in the program, what you are bringing to the table, what makes you different, and similar experiences if you had any. Make sure your answers show a lot of enthusiasm and answers the question _why you should be selected out of all the candidates_. After 2 to 3 edits of your answers, I am sure you can make it to the interviews. Jumping straight to the phone screen round.

### Phone screen round 📱
Make sure you have proper audio, video, and internet connection. The interview starts with basic eligibility questions and then takes you to more generalised questions. Make sure to convey the reason why you want to be in this program and answer every question with confidence. Remember, you know it's a good interview when it feels less like an interview and more like a conversation. Phone screening round is more like an HR round which may also include some layered tech questions such as the project which you are most proud of and why. Preparing HR questions can be at times tricky I would suggest checking out [DanLok's YT](https://www.youtube.com/c/DanLok). Once you pass this interview, you move on to the last and final round, the technical round! 

### Technical round 🧑‍💻
This is the most important round and decides if you will be a fellow or not. The technical round has no HR question and it will be a code conversation as the team calls it. First, you are asked to share you screen and give a demo of the project you submitted. Then you would be asked to go through the code and explain some parts of it while also answering some questions based on the code. You need NOT write any code while sharing your screen, but you should know every line properly along with the reasons why you are using a particular module or tech stack. For example, you submitted a simple blogging website and used [NextJS](https://nextjs.org) for the front-end, so you might face questions ranging from the reason for choosing Next over any another framework to complex conceptual questions in the area depending upon the interviewer. You might be asked your future plans with the code sample like how you plan to scale your application or what new features you would like to add. So make sure to know each and every thing about your project.

### Conclusion 🤲
I have worked in several organisations starting from leading a [campus club](https://webwiznitr.netlify.app/) to mid-range product-based startups and also got the opportunity to work with one of the finest tech companies in the world. Relating those with my MLH interviews, it felt pretty easy and comfortable, because of a couple of reasons:

- MLH has one of the most amazing sets of interviewers who will make you very comfortable the moment the interview starts.

- The questions asked in the interviews are not on business logic or to trap you, all they want is to check your enthusiasm for technology and the entire program.

- The technical interviews varies depending upon the interviewer and the project. Talking about my experience, the questions I faced were easy for me. Since it was my project and I knew every single line in it, so I was very confident with every question asked. Moreover, I did a couple of mock interviews with [Sumana Basu](https://www.linkedin.com/in/sumana-basu/) which helped me gain a lot of confidence and is something I would highly recommend. 

So that's all the tips from my side. If you still have any queries or need any help with the application, feel free to reach me out on [LinkedIn](linkedin.com/in/aniket-pal/) or drop a comment 💕

Lastly, a huge shoutout to the 14 highly enthusiastic coders I met during the fellowship! 🥳 

![My MLH Podmates](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3qg1yj2wdkjh9v1pvr4c.png)