𝐅𝐫𝐨𝐦 𝐚 𝐓𝐢𝐞𝐫-2 𝐜𝐨𝐥𝐥𝐞𝐠𝐞 𝐭𝐨 𝐀𝐝𝐨𝐛𝐞- 𝐰𝐡𝐚𝐭 𝐝𝐨𝐞𝐬 𝐢𝐭 𝐫𝐞𝐚𝐥𝐥𝐲 𝐭𝐚𝐤𝐞 𝐭𝐨 𝐛𝐫𝐞𝐚𝐤 𝐢𝐧𝐭𝐨 𝐁𝐢𝐠 𝐓𝐞𝐜𝐡? The journey isn't just about coding. It's about making the right decisions, building the right skills and staying ahead in a rapidly evolving tech landscape. In the first episode of Inside Tech Careers, we're joined by Shivam Goel, Senior Computer Scientist at Adobe, as he shares: -> His journey from a Tier-2 college to Adobe -> What companies really look for in software engineers -> Why System Design has become a game-changer for backend interviews -> How AI is transforming software engineering—and what developers should do to stay relevant -> Practical advice for students and professionals aiming for top tech companies Whether you're preparing for placements, switching careers, or dreaming of Big Tech, this conversation is packed with actionable insights you won't want to miss. 🎙️ 𝐉𝐨𝐢𝐧 𝐮𝐬 𝐋𝐈𝐕𝐄 𝐭𝐨𝐝𝐚𝐲 𝐚𝐭 6:00 𝐏𝐌 🔗 https://lnkd.in/dVKEx2hN See you there! 👋 #InsideTechCareers #Adobe #BigTech #SoftwareEngineering #SystemDesign #ArtificialIntelligence #CareerGrowth #TechCareers #Programming #Developers #GeeksforGeeks
Shivam Goel on Breaking into Big Tech at Adobe
More Relevant Posts
-
🚀 Your dream job doesn't happen by chance—it happens through the right roadmap. Every successful software engineer starts with the fundamentals, builds real-world skills, and stays consistent. Whether your goal is Google, Microsoft, Amazon, Apple, Meta, NVIDIA, Adobe, or any top product-based company, following a structured learning path can make all the difference. Here's the roadmap: ✅ Learn Programming Fundamentals ✅ Master DSA ✅ Solve Coding Problems Consistently ✅ Strengthen Core CS Concepts ✅ Build Industry-Level Projects ✅ Learn System Design ✅ Create an ATS-Friendly Resume & LinkedIn Profile ✅ Practice Mock Interviews ✅ Land Your Dream Offer 🎯 At Code Era Technologies, we're committed to helping students bridge the gap between learning and getting hired through practical, industry-focused training. 💬 Which stage are you currently on? Let us know in the comments! #CodeEraTechnologies #SoftwareEngineering #ProductBasedCompanies #Programming #DSA #Coding #TechCareers #CareerRoadmap #InterviewPreparation #LeetCode #SoftwareDeveloper #CareerGrowth #Students #TechEducation #DecodeYourPotential
To view or add a comment, sign in
-
-
Today, I attended Intuit's Shipped & Equipped session and had the opportunity to hear from the recruiting team and software engineers about engineering at Intuit, AI, and what companies expect from new graduates. Here are a few takeaways that really stood out to me: 💡 Ownership starts early. Being a software engineer is not just about writing code. It is about understanding the problem, making technical decisions, collaborating across teams, and thinking about scalability, testing, and reliability from day one. 🤖 AI raises the bar, not lowers it. AI can speed up onboarding, documentation, testing, and prototyping. But engineers are still expected to understand systems, debug effectively, and know why a solution works. ✨ Transparency builds trust. Using AI for projects is completely fine, but be honest about what AI contributed, what you built, and how you validated the final solution. 📚 Never stop learning. My favorite takeaway from the session was: "Don't let AI skip the learning process." As technology evolves, curiosity and strong engineering fundamentals remain just as important. A big thank you to Danna Hymanson, Alexandria Williams, Veronica Lekhtman, Iara Ribeiro, and the Intuit Emerging Talent team for sharing your experiences and answering everyone's questions so openly. I truly enjoyed the session and am excited to apply these learnings as I continue building and learning. #Intuit #SoftwareEngineering #AI #ComputerScience #Learning
To view or add a comment, sign in
-
Excited to announce that I joined Microsoft🚀 Every day, LinkedIn is filled with posts about people announcing their career switch into tech. After seeing so many of them, I wanted to share something different. Instead of just talking about the destination, I’m going to show you how to prepare for yours. Start preparing for SDE interviews here- https://bit.ly/4hqMUdr Before touching a single resource, audit yourself across 4 pillars: ✅ DSA ✅ SQL/Data Fundamentals ✅ System Design ✅ Communication Rate each 1 to 5. ➡️ If you’re weak everywhere with no strong pillar, don’t spread thin across all four. That’s the #1 reason candidates fail every round instead of clearing at least one. ➡️ Pick ONE. Work for 3–4 weeks until it’s genuinely strong, not “revised.” ➡️ Once one pillar is solid, layer the next on top of it, don’t start fresh. If DSA is your strength, move into System Design by scaling up your solved problems. ➡️ Finally, run timed mocks that mix coding and reasoning. ➡️ Behavioral isn’t a side quest either. Reuse the 3–4 experience stories across every question, refined until they’re crisp, not rehearsed. Along with this, one new skill that gives you an edge in tech interviews is: ➡️ AI fundamentals : RAG, LLMs, Vector Search as production skills, not theory. It could be a lot for many. But if you need the right guidance to help you elevate your skills, that’s where Tutort Academy fits in: It offers a structured roadmap for DSA and System Design, 1:1 mentorship, and company-aligned preparation for serious career switches. They’ve already helped 2,800+ professionals from both tech and non-tech backgrounds transition into PBC’s. The market rewards engineers who build software that solves real problems. 🙌🏻 #careerswitch #aijobs #aicareer #sdeinterview #tutortacademy #walmart #techinterview
To view or add a comment, sign in
-
-
One interview habit I picked up while preparing for Google still helps me as a backend engineer at Atlassian.👇 Whenever I finished solving a coding or System Design question, I stopped asking myself, "Is my solution correct?" Instead, I started asking, "What would the interviewer challenge next?" That's where the real discussion usually begins. Questions like: 🔹If the traffic suddenly grows 10x, what's the first thing that breaks? 🔹 Would you still make the same design choice if reads were 100x higher than writes? 🔹 How would you modify your solution if this API had to meet a strict latency SLA? 🔹 What's the trade-off between keeping this logic in memory versus pushing it to the database? There isn't always one correct answer‼️ They're trying to understand how you reason through engineering trade-offs, not whether you've memorized another pattern. That's something I appreciated even more after moving from Google → Atlassian. The engineers who stand out aren't necessarily the ones who write code the fastest. → They're the ones who can justify why they made a particular decision and clearly explain the trade-offs involved. That's exactly the kind of engineering thinking Bosscoder Academy helps working SDEs build through structured mentorship, System Design discussions, and feedback from engineers who've been through these interviews themselves. So if you're an SDE aiming for a switch to SDE-2/3 roles at top product companies while juggling a 9–5, Bosscoder Academy can save you months of trial and error. 🔗 Explore their program here: bcalinks.com/Lej9jOK They’ve helped 2200+ engineers crack top PBC roles through: 💡 Structured curriculum to help you master DSA, System Design, & AI 💡 Real world, AI-powered projects & 24/7 doubt-solving 💡 1:1 mentorship from industry experts 💡 Resume reviews, mock interviews, & job switch support #collab #softwareengineering #systemdesign #backendengineering #google #atlassian #PBCs
To view or add a comment, sign in
-
-
After 5 years at my current company, this one interview pattern stands out to me.👇 Most software engineers don't get rejected because they write bad code. → They get rejected because they stop thinking the moment the solution passes all the test cases. Early in my career, I made the same mistake. I believed getting the correct output was the finish line. As I grew into an SDE-II, I realized experienced engineers naturally ask a different set of questions before they're satisfied with a solution: 🔹 If the input grows from 10⁴ to 10⁷ records, is my bottleneck still the algorithm, or will memory, I/O, or cache behavior become the real constraint? 🔹 What assumptions is my solution making? Is the input sorted? Does it fit in memory? Are duplicate values possible? What changes if those assumptions no longer hold? 🔹 Am I optimizing the right trade-off? Is reducing time complexity from O(n log n) → O(n) worth the extra memory, added complexity, or lower readability? 🔹Can another engineer understand *why* I chose this approach? The best solutions don't just work, they clearly communicate the reasoning behind the data structure, algorithm, and trade-offs. Those are the conversations interviewers at top product companies try to have during coding rounds. They're evaluating engineering judgment as much as coding ability. That's why structured preparation matters. Bosscoder Academy helps working SDEs build that engineering mindset through mentorship, interview simulations, and structured feedback, not just by solving more DSA problems. If you're aiming for SDE-2/3 roles at top product companies while balancing a full-time job, I'd highly recommend getting structured guidance from the industry experts at Bosscoder Academy. 🔗 Explore their program here: bcalinks.com/Lt7LNOb They’ve helped 2200+ engineers crack top PBC roles through: 💡 Structured curriculum to help you master DSA, System Design, & AI 💡 Real world, AI-powered projects & 24/7 doubt-solving 💡 1:1 mentorship from industry experts 💡 Resume reviews, mock interviews, & job switch support #collab #softwareengineering #microsoft #sdeprep #jobswitch #careergrowth
To view or add a comment, sign in
-
-
Excited to share a ₹60 LPA offer. 🚀 Every day, LinkedIn is filled with people announcing their career switch into product companies. But what most people don't share is what it actually took to get there. A few months of focused preparation can compound into a ₹60 LPA career. That sounds exaggerated until you do the math. People look at interview prep as a cost. >4 months of evenings. >Weekends spent studying instead of relaxing. >Saying no to a few trips or late nights. If you're planning a product-company switch in the next 1-2 months, get the complete roadmap—https://bit.ly/4b6Rud2 The engineers who make these jumps look at it differently. They see it as an investment that compounds long after the interviews are over. For high-paying SDE roles, that usually means: ~ Strong DSA—not just solving problems, but explaining your thinking. ~ System Design that goes beyond textbook diagrams. ~ Real-world projects that demonstrate ownership and engineering decisions. ~ AI skills that are becoming part of every modern engineering team—LLMs, RAG, GenAI integrations, AI-assisted development, and knowing where these tools actually add value. These aren't just interview skills. They're the foundation for bigger salary hikes, stronger appraisals, better stock grants, and greater negotiating power throughout your career. That's why structured preparation makes such a difference. Tutort Academy brings together DSA, System Design, SDE + AI-focused real-world projects, and detailed 1:1 mock interviews into a single roadmap that's already helped 2,800+ professionals move into product-company roles. Very few investments can change the next 10 years of your career. A few focused months of preparation are one of them. #careerswitch #sdeinterview #aiinterview #aijobs #google #techcareer #tutortacademy
To view or add a comment, sign in
-
-
Moving from Microsoft → Cohesity and now Weave... One interview question humbled me more than any System Design round👇 "You said you'd check the logs." "Which logs?" That follow-up completely changed how I approached senior backend interviews. Early in my career, "check the logs" felt like a reasonable debugging answer. Today, I know it's almost meaningless. A senior engineer is expected to narrow the search before opening a dashboard. For example, I'd first ask: → Is this request failing across all pods or just one? → Did latency increase after the last deployment? → Do traces point to our service or an upstream dependency? → Is p99 latency increasing while p50 stays stable? 🔸Only then do logs become useful. That's the difference I've noticed after moving through Microsoft, Cohesity, and now Weave. Senior interviews are becoming less about finding *an* answer and more about proving you know **where to look first** when production behaves unexpectedly. That kind of production thinking isn't something most of us practice intentionally, even after years in backend engineering. That's exactly where Bosscoder Academy's EVOLVE helps. It goes beyond DSA and System Design by helping experienced engineers develop the production mindset, debugging approach, and engineering judgment expected in Senior SDE interviews. And if you're preparing for a serious switch to Senior roles, learning from industry experts at Bosscoder Academy can be highly profitable. 🔗 Explore EVOLVE for SDEs with 6+ YOE here → bcalinks.com/gcz7u5N They’ve helped 2200+ engineers crack top PBC roles through: 💡 Structured curriculum to help you master DSA, System Design, and AI 💡 Real world, AI-powered projects & 24/7 doubt-solving 💡 Leadership skills for Senior roles with 1:1 mentorship from industry experts 💡 Resume reviews, mock interviews, and 100% job switch support. #SoftwareEngineering #BackendEngineering #SystemDesign #SeniorSDE #JobSwitch
To view or add a comment, sign in
-
-
𝗗𝗿𝗲𝗮𝗺𝗶𝗻𝗴 𝗮𝗯𝗼𝘂𝘁 𝗠𝗔𝗔𝗡𝗚 𝗶𝘀𝗻’𝘁 𝗷𝘂𝘀𝘁 𝗮𝗯𝗼𝘂𝘁 𝘄𝗿𝗶𝘁𝗶𝗻𝗴 𝗰𝗼𝗱𝗲. 𝗜𝘁’𝘀 𝗮𝗯𝗼𝘂𝘁 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝗱𝗼 𝘄𝗵𝗲𝗻 𝘆𝗼𝘂𝗿 𝗰𝗼𝗱𝗲 𝗱𝗼𝗲𝘀𝗻’𝘁 𝘄𝗼𝗿𝗸. 🐛 You can solve DSA problems. You can build projects. You can learn frameworks. But 𝗿𝗲𝗮𝗹 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝘀𝘁𝗮𝗿𝘁𝘀 𝘄𝗵𝗲𝗻 𝘁𝗵𝗶𝗻𝗴𝘀 𝗯𝗿𝗲𝗮𝗸. 𝗜𝗱𝗲𝗮 → 𝗕𝘂𝗶𝗹𝗱 → 𝗗𝗲𝗯𝘂𝗴 → 𝗗𝗲𝗽𝗹𝗼𝘆 🚀 This cycle teaches skills that matter in real engineering teams: • 𝗕𝗿𝗲𝗮𝗸𝗶𝗻𝗴 complex problems into smaller ones • 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 instead of randomly changing code • 𝗥𝗲𝗮𝗱𝗶𝗻𝗴 logs and error messages • 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 before assuming something works • 𝗧𝗵𝗶𝗻𝗸𝗶𝗻𝗴 about edge cases • 𝗪𝗿𝗶𝘁𝗶𝗻𝗴 maintainable code 𝗠𝗔𝗔𝗡𝗚-𝗹𝗲𝘃𝗲𝗹 𝗽𝗿𝗲𝗽𝗮𝗿𝗮𝘁𝗶𝗼𝗻 𝘀𝗵𝗼𝘂𝗹𝗱𝗻’𝘁 𝗯𝗲 𝗼𝗻𝗹𝘆 𝗮𝗯𝗼𝘂𝘁 𝘀𝗼𝗹𝘃𝗶𝗻𝗴 𝗟𝗲𝗲𝘁𝗖𝗼𝗱𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺𝘀. It should also teach you how to 𝘁𝗵𝗶𝗻𝗸, 𝗱𝗲𝗯𝘂𝗴 𝗮𝗻𝗱 𝗯𝘂𝗶𝗹𝗱. That’s the difference between “I can code” and “I am an engineer.” 𝗪𝗵𝗶𝗰𝗵 𝘀𝗸𝗶𝗹𝗹 𝗱𝗼 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸 𝗱𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿𝘀 𝘂𝗻𝗱𝗲𝗿𝗲𝘀𝘁𝗶𝗺𝗮𝘁𝗲 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 — DSA, debugging, system design, or writing clean code? 👇 #Google #Microsoft #Apple #Meta #Infosys #Amazon
To view or add a comment, sign in
-
-
One thing surprised us during this year's campus hiring. Our new hires are now completing the training program in just 8-9 weeks. Just a year ago, the same training typically took 12-13 weeks before they could start making meaningful contributions to real projects. The training hasn't become easier. The students have become better. They're learning faster, asking better questions, and challenging us to raise our own standards. AI hasn't reduced the need for software engineers. It has raised the expectations. Today, everyone has access to AI that can generate code. Great engineers stand out because they understand the problem, question the solution, make thoughtful decisions, and use AI to build better software. As we begin another campus hiring season, we're looking for students who are ready to raise the bar, not just write code. #CampusHiring #SoftwareEngineering #ArtificialIntelligence #AI #Engineering #Students #PixelCompute
To view or add a comment, sign in
-
-
We don't measure hiring success by how many people join us. We measure it by how much stronger every new hire makes the team. Great talent thrives in a great engineering environment. That's where exceptional growth happens. We'd rather leave positions unfilled than lower our hiring bar. This is the standard we hire for. 👇
One thing surprised us during this year's campus hiring. Our new hires are now completing the training program in just 8-9 weeks. Just a year ago, the same training typically took 12-13 weeks before they could start making meaningful contributions to real projects. The training hasn't become easier. The students have become better. They're learning faster, asking better questions, and challenging us to raise our own standards. AI hasn't reduced the need for software engineers. It has raised the expectations. Today, everyone has access to AI that can generate code. Great engineers stand out because they understand the problem, question the solution, make thoughtful decisions, and use AI to build better software. As we begin another campus hiring season, we're looking for students who are ready to raise the bar, not just write code. #CampusHiring #SoftwareEngineering #ArtificialIntelligence #AI #Engineering #Students #PixelCompute
To view or add a comment, sign in
-
Explore related topics
Explore content categories
- Career
- Productivity
- Finance
- Soft Skills & Emotional Intelligence
- Project Management
- Education
- Technology
- Leadership
- Ecommerce
- User Experience
- Recruitment & HR
- Customer Experience
- Real Estate
- Marketing
- Sales
- Retail & Merchandising
- Science
- Supply Chain Management
- Future Of Work
- Consulting
- Writing
- Economics
- Artificial Intelligence
- Employee Experience
- Workplace Trends
- Fundraising
- Networking
- Corporate Social Responsibility
- Negotiation
- Communication
- Engineering
- Hospitality & Tourism
- Business Strategy
- Change Management
- Organizational Culture
- Design
- Innovation
- Event Planning
- Training & Development