Hi folks! About a year ago, I was in your place, struggling quite a bit with DSA. I was particularly weak at identifying patterns in problems, and on top of that, I couldn’t find enough questions to practise each pattern thoroughly.
To make things easier, I built [DSASheeeet](https://dsasheeeet.vercel.app/home), where you can practise almost every possible problem-solving pattern with a carefully curated set of problems to help you understand each topic inside out.
Apart from that, it also features 423 companies, so you can prepare for upcoming company assessments without spending hours researching questions. Whether you’re preparing for placements, planning a job switch, or struggling to identify patterns in DSA problems, DSASheeeet is here to make your life easier.
Hello coders may Dsa striver a2z sheet se kar raha hu may dsa ke question ko 10 min approach karta hu uske baad video dekhta hu or pseudo code copy may likha leta hu or method samajh leta hu kya aise hi dsa kiya jata hai
I have a basic knowledge about dsa have done ques from a to z but I wish to revise dsa entirely so are there any sheets that can be used for revision and contains good ques to practice for placement
Amazon reportedly cut up to 250 jobs from its Devices and Services division this week.
Layoffs are part of the tech industry. Companies change priorities, restructure teams and move in different directions.
For those preparing for SDE roles, it’s a reminder that preparation shouldn't stop at DSA and interview questions. Problem-solving, understanding systems, learning new technologies and building practical projects are important too.
Came across this article on takeUforward community that discusses what upcoming engineers can learn from Amazon's latest layoffs
What do you think matters most for long-term career growth in tech is it strong fundamentals, practical experience or the ability to adapt to new technologies?
Switching from a startup to a company like Amazon isn't easy, so it's always interesting to see how someone actually pulled it off.
One of our community members shared their entire journey, from spending a year at a startup to cracking Amazon SDE-1.
They’ve broken down their prep strategy, interview rounds, what Amazon tested and what they’d do differently if they had to start over.
If you're preparing for SDE roles or aiming to move to a product-based company, there are some useful takeaways
Read the full experience here → From 1 Year at a Startup to Amazon SDE-1 For those who’ve made a similar switch what was the toughest part of the process for you? Drop it in the comments
An engineering manager at Anthropic just posted on X that traditional coding interviews are not a great way to evaluate engineers anymore and he’s put them to rest.
He also made an interesting point: hunger beats tenure according to him junior engineers have a massive opportunity to impress through the work they do rather than just how many years of experience they have.
The reactions on X are mixed, Some people think this is the right call for the future of hiring while others point out that at volume, reviewing every resume and evaluating candidates individually could get very difficult.
With how rapidly the way we build software is changing, the debate around the correct way to filter and interview engineers is heating up too.
What do you think? are traditional coding interviews becoming outdated or is there still a place for them?
A lot of us are trying to land SDE roles and referrals are a big part of that conversation but sending dozens of LinkedIn DMs and waiting for replies isn't really a strategy
We came across this article on takeUforward that breaks down how to approach referrals better from finding the right person and reaching out with a specific job opening to making sure your resume is actually worth referring.
It's a useful read if you're currently applying for internships or fresher SDE roles
Microsoft has reportedly introduced a Voluntary Exit Offer for employees across India, the US, the UK and Canada.
No official layoff announcement. Instead, eligible employees are being given the option to leave with financial support.
But what does this actually signal?
Is it simply about giving employees more flexibility, or could it hint at a bigger shift in how tech companies are managing their workforce?
There's more to this announcement than the headlines suggest.
TakeUForward has published a detailed breakdown covering who may be eligible, how this offer differs from Microsoft's earlier voluntary retirement program, what the company has actually confirmed and what remains speculation.
The article also explores what this could mean for students and engineers preparing to enter an industry that's rapidly evolving with AI.
Been going through a lot of recent interview experiences and one thing keeps showing up that DSA is still the base, but companies are testing a lot more around it now.
Practical coding tasks, debugging someone else’s code, project deep dives and even AI-assisted rounds where you have to review and fix generated code instead of writing everything yourself.
If you're preparing for placements, you can check out this article on TakeUForward. It breaks down what final-year students should focus on, how to prepare for different interview formats and which skills to build alongside DSA.
My laptop’s internal camera isn’t working, so I’m planning to use an external USB webcam. Is it okay to use one for online assessments (OAs) at companies like Amazon, Infosys, etc., and during interviews? Can it cause any issues with proctoring or eligibility?
Ever wondered what happens when a Google interview tests more than your ability to write code?
Understanding an unfamiliar piece of code, tracing its execution, and figuring out how it works can be challenging, even when the logic looks simple at first.
I came across this Google Technical Interview – Code Comprehension Round experience on Take U Forward and it's worth checking out if you're preparing for technical interviews
Have you ever struggled to understand someone else's code during an interview? What part did you find the most difficult?
One thing that can hurt your chances in a senior tech interview? Having the right answer but failing to explain why it's the right choice.
At the Staff Software Engineer level, interviewers may expect much more than coding skills. System design, AI concepts, architecture decisions, and leadership can all become part of the discussion.
But how do you prepare for questions where there's no single correct answer?
Would you rather face a tough DSA problem or defend a system design decision when the interviewer keeps challenging your approach?
This eBay Staff Engineer AI Platform interview experience is worth cheaking out if you are curious about what these interviews can involve
What would you do if you solved the coding question but got stuck on the technical questions? Would you focus more on DSA or spend equal time on CS fundamentals and SQL?