codedecks

Big Ω (Big Omega) is a browser extension which enhances your experience while you are solving coding problems online on various competitive programming websites like Leetcode ★ Company Tags - Reveals information about which companies have asked the problem that you are currently solving and how many times this problem been asked by the same companies Download here

Those who have voted for yes 🙌 Please join our instagram page for further updates https://instagram.com/codedecks_in

Spring Boot by Java Brains https://youtube.com/playlist?list=PLqq-6Pq4lTTbx8p2oCgcAQGQyqN8XeA1x

🏆 Thanks for having 500 subscribers here

How to make Java your strong point? Master the basics 💯 And master the questions in this doc, they’re commonly asked in technical interviews. Created by veterans at Bosscoder Academy, that have helped 1000+ software engineers crack top product based companies. Checkout them here - https://bit.ly/3nxaiN1

Sharing some of the Success metrics from our Big Omega Extension 🥳😇

Journey of Ramanathan from Zoho → Flipkart : He was a member of the Technical staff at Zoho. Ramanathan knew if he could upskill, then he could crack a better role in tech. So, he started upskilling in Problem Solving and System Design using online resources. But he encountered some problems - 1. There was no structure to the resources and it made it difficult to figure out what is the correct way to upskill. 2. He also faced difficulties due to a lack of guidance, which could’ve helped him figure out the right path. 3. Ramanathan’s peer group also lacked in providing him with guidance and support for preparation. After struggling due to these reasons for sometime, Ramanathan came across a free masterclass by ……. To be continued Check full post here https://www.linkedin.com/posts/grusiya_upskill-dsa-tech-activity-7058285318495510528-1pmV

This is my understanding of what interviewers are by-and-large looking for in a candidate for a Staff Software Engineer (or higher) position, at least as it pertains to the systems design interview. Can you take a vague goal (”design Twitter”) and come up with a fully-developed proposal? Are you able to spot ambiguities in the requirements and ask good clarifying questions? Are you able to distinguish between features that really need to go into the MVP versus ones that are really extended/optional features that can be punted? Do you proactively look for issues with your design, or do you need prodding from the interviewer? Are you able to assess different options and make trade-offs, or are you attached to certain ways of doing things? Do you have a good sense of what to prioritize, or do you get lost in the weeds? Are you able to produce an actual deliverable within the timeframe you are given? Does your design meet all functional and non-functional requirements? In particular, does it scale? While you are not expected to produce an industry-grade design in 45 minutes ー this would be quite unreasonable to ask ー what you produce should be something that can be turned over to a product team for implementation. Are you able to achieve the basic requirements quickly so that you have time to extend your design in an interesting way? Are you able to use speech, notes, and diagrams to communicate your ideas clearly to someone else? Are you able to take feedback?

What are the expectations from L6, L5 and L4 levels in a System Design Interview ? L6: How complete is the design, how much can the candidate drive the discussion (while being mindful of feedback/direction given by the interviewer), how expansive is the answer (while also going deep enough to show real understanding rather than just buzzword regurgitation). L4: needs a lot of probing. What if traffic increases 10x? Will your solution work if X,Y, Z happens? How do you handle failure in this part? Etc. L5: should offer multiple solutions and analyse trade offs with minimal probing More info: https://www.teamblind.com/post/Facebook-Difference-between-E4-and-E5-in-interviews-ZtHtfjCt