NOTE: SOME ANSWERS ARE NOT CORRECT! PLEASE DO NOT CONSIDER IT AS A SOURCE OF TRUTH, I CREATED THIS REPO TO TRACK THE PROGRESS DURING THE PROCESS ONLY.
Instabug Backend Internship Summer 2022 Technical Task
Received my rejection letter in 06/06/2022. Sad, but atleast we are one rejection closer to an offer!
It consists of six MySQL questions where we had to run POST requests on their API endpoint to execute the problems' queries and submit the solution.
| Question No. | Complexity | Wrong Attempts No. | Requirements | Time of Submission MM/DD/YYYY HH:MM:SS | My comments |
|---|---|---|---|---|---|
| 1 | Easy | 4-5 (First question to answer so didn't know the system) | Basic SQL | 06/01/2022 10:26:18 PM | I hope I'll not lose marks because I submitted wrong table names instead :@@@@@@ |
| 2 | Medium | 2 | Basic SQL | 06/01/2022 10:32:05 PM | Normal one I believe |
| 3 | Hard | 1 | Some Advanced Queries | 06/02/2022 2:09:54 AM | The server kept respond with Killing Query I thought they wanted a more efficient query But later then they mentioned that it is normal, and it was too late.... |
| 4 | Easy | 0 | Basic SQL | 06/02/2022 9:50:54 AM | Nothing, just a normal distinct question |
| 5 | Hard | 2 | Advanced SQL (Indexing) | 06/02/2022 4:54:41 PM | I HATE THIS PROBLEM AND 6 AS WELL |
| 6 | Medium | 1 | Advanced SQL (Indexing) | 06/02/2022 3:34:47 PM | I DON'T KNOW HOW CAN I IMPROVE THE EFFICIENCY OF INDEXED QUERIES |
Regarding this experience, I enjoyed it kind of. Yet it could have been better if it they have mentioned earlier some details like we could have submitted queries once more, and that Killing query issue is not a big deal.
Note: Check each file's history