Hi everyone! I've been Software Engineer for almost 10 years and I've always worked for product companies of all sizes (from Startups to big corporations). The thing is, I love Software Craftsmanship and everything around it. I love getting better as an architect, I love learning about what's new on the framework I'm working on so it makes my/our life easier, and I also spend spare time trying to improve my testing and leadership skills, BUT I don't like spending time practicing algorithms because unless you work for companies building Dev tooling (FAANG typically) you are not going to need them. As a Mobile Engineer, I'm planning to start processes (if there are open positions) with companies like #Slack, #Twitter, #Zillow, #Square, #Dropbox, #Airbnb, #Tinder, #Pinterest, #Intuit and #Netflix (Products I love that I currently use / I've used in the past) Any chance I could get tips from you on what topics you would cover and which ones I could avoid? I totally get it's going to depend on the company, but some commonalities might give me a better idea of what to prepare the most. Some examples : 1) Primitive Types. 2)Arrays 3) Strings 4) Linked Lists 5) Stacks and Queues 6) Binary Trees 7) Heaps 8) Searching 9) Hash Tables 10) Binary Search Trees 11) Recursion 12) Dynamic Programming 13) Greedy Algorithms 14) Graphs 15) Domain Specific (System Design, Language-related, OOP, FP) Thank you in advance!
None of the above. Interviewers mainly want to know how well you can memorize LC solutions
This is key. Interviews have nothing to do with real word or day to day. The key is memorizing leet code - data structures and algorithms. Understand that and you will have many doors opened .
Thank you both!
I agree with Apple for FAANG, but not non-FAANG. My data points are in FAANG you often come across interviewers with a looong stretch of their resume at the same company but clueless about real life design. Their questions are hardcore LC stuff and they often judge you on a combo of speed and cramming complexity alternatives into a 45 min interview slot. In my experience pre-IPO very senior interviews have a heavier emphasis on system design. They do ask algo, but from the set that you’d be able to solve if your day to day involves solving problems. The part I find challenging is how the LC heavy FAANG path tends to stand between you and a safe high TC, while the more crafty jobs come with a mix of base-matching and slice of opaque pie in the sky. My take away: weaponize your readiness. Then let life happen.
Thank you for your thoughtful analysis. I totally see your point. I'm kind of scared that when working for any of these companies, people won't really care about clean code, clean Architecture and other important concepts when thinking about building a product at scale. I've read many books (Clean Code, Clean Architecture, Effective Java, Effective Kotlin, The Software Craftsman, DDD...) and I have a feeling that, because of the interviewing process being a bit broken, I'm going to end up working on really spaghetti code that's really difficult to change due to valley companies' ingeniering culture - > I don't care how but get your stuff done.
Their level of care will depend on what stage you come in. If they’re still growing they won’t BS themselves with LC and go with pragmatism. If they’re in maintenance mode their mental frame will be to test you for BS tolerance and conformity. Net net consider a rejection a self-filtering blessing. Plant many seeds. You sound like the kind of person good people would want to work with, be yourself.
World Conflicts
Yesterday
624
Peaceful Protest Hasn’t Worked and Has Been Met With Aggression.
Tech Industry
Yesterday
886
I watched two Google Engineers refuse to give up a seat for a lady holding a newborn baby at the airport.
Tech Industry
Yesterday
3305
Pray for folks at Tesla
Software Engineering Career
Yesterday
454
If your team does daily standups, your manager is a micromanager
Work Visa
Yesterday
859
Hypocrisy of Indians
This has been covered so many times. Use the search functionality
+1
I did, but most of what I found was FAANG-related or other random stuff using the keyword "topics"