First Week of the 4th phase in EncorAcademy
Hello there, hope you are ok, it’s been a surprising beginning of the year, but we need to keep learning right, it is all that matters because knowledge is happiness, and I am at this internship to learn new things, and hopefully find a job on this great company.
Last Tuesday we started the “4th Phase: Your personal brand”, of the internship in Encora. The main goal is to prepare us for job interviews. We are going to build our CV, but mostly we are going to prepare ourselves more for the questions that can be asked.
General when you apply to some job vacancies at small companies, startups, or general jobs, all of the are going to ask you more technical questions about the technologies or frameworks they are asking you to work with. But here in Encora as a big software development company, as in the Big 5 Tech Companies (Amazon, Apple, Google, Facebook, and Microsoft), they will ask you more questions about algorithms, more about Big O, and that stuff.
That I learned in the book, Cracking the cod Interview, that is one of the readings of the phase, besides 2 videos of coding interviews. In those videos I saw how people at technical interviews on Google, were asked to solve a problem; it was a medium-hard problem, but what the interviewer was going to evaluate, was how he solves the problem. First Clarification, if he asks if he didn't understand at all the questions, or if he has some doubts about the question in general; after that comes the Thinking Out Loud, it is about to say out loud what you are thinking, so that way maybe the interviewer can help you if you get a little stuck. Talk Before You Write, before to start coding or writing, always is better to take a moment to think about what are you going to do, it helps us to clear our minds, and finally to test our solution, try to write our code, and test if you can or if it is a whiteboard, imagine what it is supposed to return.
Other stuff I learned these days, was more about OOP and SOLID, I apply such concepts in Java with my mentor, so that way I saw where those were implemented.
I also learned about Big O, I assumed that you heard of it, and well it helps us know how much time our solution is going to take, the complexity of our functions, so we can be evaluated if it is the optimal solution to solve a problem. It has been very difficult for me to understand it, but I am still reading more about it. Hope next week I can give you more specific details of it.
As always I wish you a happy week, and let's keep learning right, cheers!