rtCamp Interview Experience (On-Campus)

I applied to rtCamp for the role of WordPress Engineering on-campus, the selection process included the following rounds:

Round 1: Resume Shortlisting

My resume shortlisting process spanned an extended period of three months. While some of my peers received interview invitations within a month, my journey involved a more extended wait. The interview links arrived via personal email, notifying me of the scheduled interview time.

Round 2: The Interview

The interview process at rtCamp began with a combined lobby for all candidates, totalling around 12 individuals. We introduced ourselves in the lobby, creating a preliminary camaraderie. Following the introductions, candidates were directed to their respective interview rooms.

Introduction and Weather Chat:

The interview commenced with a customary introduction and a brief discussion about the weather. This set the tone for a more relaxed start to the technical dialogue.

Frontend or Backend Preference:

Clarifying my technical preferences, I was asked whether I leaned towards Frontend, Backend, or both.

GitHub and Git:

A series of questions unfolded, probing my understanding of Git and GitHub:

1. Can we use GitHub without Git?
2. Features of Git.
3. Where is all the Git data stored?
4. Difference between .git and .github directory.
5. Explanation of Gitignore.

Repository and Code Upload Scenarios:

The conversation delved into scenarios related to repositories and code upload dynamics:

1. Can another person push code in a private repository?
2. How does GitHub identify a user uploading data?
3. Implications of copying authorized Git and GitHub into code.

Technical Frameworks and Libraries:

1. Difference between jQuery and React.
2. Distinction between DOM and Virtual DOM.
3. Preference between React and jQuery for a website with 50 pages.
4. JavaScript and Session Handling:

JavaScript:

1. Difference between JavaScript and vanilla JavaScript.
2. Speed considerations for building a slider using pure JavaScript or React.
3. Feasibility of using sessions without cookies.
4. Security and Validation.

Security aspects:

1. Authorization of user logins.
2. Data is stored in JWT (JSON Web Token).
3. Encryption versus hashing for password security.
4. Significance of salt in hashing.
5. Understanding Rainbow tables.
6. Form Validation and HTTP Methods:

Form Validation & HTTP methods:

1. Validation preferences for a form with name, email, and a message box.
2. Security considerations of server-side versus client-side validation.
3. Implications of disabling JavaScript on client-side validation.
4. Differences between GET and POST methods.

The interview concluded with a fundamental database concept explanation of indexing in databases.

In the end, the interviewer ran out of questions to ask as he had cross-questioned for every topic to check for the clarity of concept asked, hence be thorough with the topics prepared.

Learning the following topics will surely help you for the interview:

GitHub and Git, Repository and Code Upload Scenarios, Technical Frameworks and Libraries, JavaScript and Session Handling, Security and Validation, Form Validation and HTTP Methods, Cookies and Sessions, Database Indexing and Working in Incognito Mode.

My interview at rtCamp provided a thorough exploration of various technical dimensions. Each question served as a gateway to understanding my knowledge and problem-solving abilities. While my journey didn’t culminate in a position at rtCamp, the experience enriched my learning and problem-solving skills. I wish future candidates the best of luck in their interview endeavours!