Barry Flinn’s Post

3 Books Every New Grad Looking to Work in Tech Needs to Read Discover three essential reads for new graduates entering the tech industry! Read this post and more on my Typeshare Social Blog: https://lnkd.in/gDBmR8Fj

"One often meets his destiny on the road he takes to avoid it" - Master Oogway Until my 5th semester, I was convinced a tech career wasn't for me. Coding was not my cup of tea, and I was learning image editing, I even started making YouTube tutorials. (I love to share what I know) But In my 6th semester, Responsibilities hit, & getting a job became a priority. I realised I’d be wasting my potential if I didn’t try. I started preparing and this quote perfectly describes my preparation phase  "I quit every goddamn day, I just never said it out loud." - Harvey Specter Slowly and gradually, I started understanding things and kept going, still going cause in IT the learning never stops (This challenges me even more) And this journey just took an incredible turn. I'm happy to announce that I'm officially a Software Engineer at Google. Here's to new beginnings, accepting the unexpected & the power of dedication! Also, I would like to thank my recruiters Saranya M and E. S. for giving me this wonderful opportunity and helping me throughout the process. #Noogler #Google #SoftwareEngineer

For the next couple of weeks, I am going to change things up a little and share some advice for early-career folks getting started in tech in the form of a QnA mini-series. I find that the rapid innovation and evolution of tech often leads to anxiety, insecurity, and confusion surrounding how best to build a career foundation; and I am hoping that this series helps as a starting point. Q1: I want to establish myself in my engineering career, what is the one thing I should focus on? A: Deliberate curiosity. If you want to ask yourself one question at the end of every work week to track meaningful progress on your career journey, it should be: “Was I curious enough this week?” This can be hard to measure, so here’s 3 quick tips on how to track this: - What percentage of your discussions, meetings, calls, 1-on-1’s did you spend passively listening/taking notes vs. probing, testing your understanding, doing follow-up research etc? This number should be high, >60% minimum. - How many working hours of the week did you spend learning something new and hard, where you can now converse with someone on that topic at an undergrad level? This should be at least 4 hours a week, ideally 8 hours. - What percentage of the week did you spend solving real problems? This is not solving leetcode, but actual bugs and features in products or open source projects, designing scaling frameworks, writing user docs, doing workshops on a specific challenge etc. This should be high, at least 50% of your week.

Setting realistic career goals is like laying down the blueprint for your dream tech career. Here’s some tips to help you navigate this path: 1. Break it Down: Big dreams can feel overwhelming, so break them down into bite-sized chunks. Set short-term goals like learning a new coding language, building a project, or mastering a specific skill. 2. Stay Curious: The tech landscape is constantly evolving, so keep that curiosity alive! Dive into new technologies, explore different domains within IT, and never stop learning. 3. Network, Network, Network: Connect with fellow programmers, mentors, and industry professionals. Networking opens doors to opportunities, valuable advice, and insights that can shape your career journey. 4. Celebrate Your Wins: Take time to celebrate your achievements, no matter how small. Each milestone reached is a testament to your hard work and dedication. You can either be a good programmer or you can be a great programmer The choice is yours 😉

It’s 2018, I interviewed for 70+ product companies, and decide to QUIT! 😔 . . These were the exact thoughts that came up to my mind, when I tried to make a switch from VMware. Almost, after 5 years I decided to make a transition to the product giants like Microsoft or Google. However, after giving interviews at 70+ companies, I had only rejections to face. And here’s the main reason why → → I had forgotten about many of the concepts in DSA. → Had lost touch with tech interviews. Not only this, interviewing for such a big tech giants made me a bit nervous. But, once I realised this is natural and happens with most Software Engineers. I pulled up my sleeves and started preparing hard. Picked up concepts from scratch, made my problem-solving skills top-notch, etc. And eventually I was able to crack Microsoft.❤️ However, I know, it’s really hard for any working professional to make a switch after 6-7 years, due to forgotten concepts, fear, etc. So, if you’re a working professional targeting Senior roles at Top PBC’s, a good position & building a great career in a product company I’d suggest checking Bosscoder Academy. Check them here: https://bit.ly/3Vjd3j5 Enrol in a course that’s specially designed for experienced professionals and get: ✅ Structured curriculum heavily focused on DSA & System Design. ✅ Live Weekend Classes, with Limited Batch Size with only experienced Working Professionals. ✅ Personal Mentorship from Industry Veterans working with MAANG. ✅ 24/7 Doubt Support & Placement Assistance for Senior Roles. #microsoft #sponsoredpost #linkedin

I love easter eggs. Not the big “E” easter eggs, although a peanut butter filled chocolate one is pretty freaking awesome. I mean the ones that get shipped in software by a creative and, perhaps, subversive product team. Anytime I find one, I think, “Yes! Here are some people who enjoy what they do to the point that they’ll spend extra time developing something that maybe no one will ever see, but they will know it’s there, and that’s enough reason to do it.”   Since I’ve worked exclusively in enterprise software for the past good while, with often “mission critical” applications, I have had scant success convincing any of the PMs with whom I’ve collaborated to prioritize the “AS a user I WANT a fun hidden feature SO THAT I can smile a little when I discover it” user story I add to every backlog. Oh well.   That’s why when I read this post on the official Microsoft Dev Blog, I did a little fist pump in honor of this ingenious young person who may, in fact, be the most excellent intern in all of recorded tech history. I am glad they were (eventually) not egregiously punished, and I sincerely hope they continue to thrive in their job. At the very least, they have a phenomenal—and cautionary—tale to tell the next generation of interns on their team. #softwaredevelopment #easterEggs #MicrosoftDevBlog   Link to the post: https://lnkd.in/esYU2cAS

Our DMs are flooded and here's why: 👇 20+ students placed in 3 months, with the highest 9 LPA+ package & Everyone's asking: 'When is the next batch starting? I want to ENROLL.' DevSprint: Building Products ∝ Building Careers. In 8 weeks, learn to build, collaborate, and pitch recruiters and founders for your dream job. You'll have smart people guiding you. Experts who've been there and done that from: - Google - PayPal - Peerlist - Speech to Note - Blinkit - companies' CTOs & founders Why join DevSprint'5? - Abundant learning opportunities - Network with industry insiders - Clear, practical knowledge - Hands-on program focused on workplace skills. Admission Process: 1. Complete the application form below. 2. Attend the call with the Cohort Team. 3. Receive an admissions decision by email. 4. Pay the admission fee of ₹999 if you are selected. The cohort has only 30 seats, so please take some time to fill out your application and answer the questions to the best of your ability. The selection process takes 2 weeks from application. and you will only have to pay cohort fees if you are selected. Registration link in the comments.

4 Rejections, 1 Offer : How I Finally Landed a Job at Microsoft While I was preparing for my switch I interviewed for 6️⃣ top product-based companies. But I faced multiple rejections This was disheartening and it made me feel underconfident. So, I took a little time to process it and found where I was going wrong and how I could improve. Here are my learnings from those rejections: → My inadequate practice with DSA → Not writing clean, well-commented code → Limited exposure to designing scalable, high-performance systems Simply knowing my weak points wasn’t enough. I needed to work on them, but doing it alone didn’t seem feasible, and I struggled to track my progress. That’s when I sought help from my mentor. His support and guidance made all the difference Working on my weaknesses was crucial, but having guidance made the process smoother and saved me a lot of time. Result → I’m today a Microsoftie ❤️ Now, If you're trying to make a switch and need help with guidance and mentorship I’d suggest you checking out Bosscoder Academy. Check here: https://lnkd.in/gQrsVcDV ✨ Also, get a 30% off on all the programs for a limited time ✨ They can help you with → 💡 Structured programs for learning DSA, System Design, and Full Stack Development. 💡 Personal mentorship from industry veterans. 💡 Live classes and 24/7 doubt support. 💡 Real-life, relevant projects with Placement Assistance.

"Just Code" is career suicide. Mastering the latest framework won't guarantee you a promotion. Neither will memorizing every algorithm or optimizing code to the nanosecond. (Though those skills are definitely valuable). The truth is: The path to technical leadership is shockingly non-technical. It's communication, leadership, and building meaningful relationships. It's saying "yes" to that presentation, that cross-functional project, that mentorship opportunity. It's being proactive, taking initiative, and stepping outside your comfort zone. Now, don't get me wrong: Technical skills are essential. Being a coding ninja is awesome. But they're not the golden ticket. The golden ticket is your ability to influence, collaborate, and deliver results. So stop hiding behind your monitor and start building your career capital. It won't happen overnight, but it will happen. And that's a promise. Join 150+ engineers who've transformed their careers with my Top Engineer Method. It's the no-BS blueprint for mastering the must-have skills that get you promoted. Learn more at https://lnkd.in/gMGfmVas

While at Walmart, I cracked Microsoft, and it was all because of this→ My Consistency in DSA! 💪 But most working professionals when they try to make a switch, often end up getting Rejected. 😓 This case was with me, and INCONSISTENCY was one of the major reasons for this. However, I cracked top product companies like MAANG, Microsoft, and this what helped me 😰 📌 I never got demotivated by Rejections. Believe me, I was rejected by my dream company twice. But I cracked it in my third attempt. How? → I didn’t let Rejections get the best of me, instead I used them as a Motivation to understand what mistakes I was making. 💪 📌 Until and unless I achieved my target, I would never stop Chasing it. Since, I was working a full-time job, BALANCE was everything. I made sure to dedicate post work 2-3 hours to DSA. Once, I made my DSA & problem-solving skills top-notch, I didn’t stop. 📌 Lastly, I never lost hope. I kept my eye on the ball. Remember → Never think that you can’t do anything (your mind is a powerful thing) make sure you keep Positive attitude everytime. 🙌 Now, if preparing for tech interviews still feels like a struggle, I’d suggest taking help of industry veterans at Bosscoder Academy. Check them here: https://bit.ly/4a1AOjA They can help you with : ✅ Structured curriculum to learn problem-solving in DSA, System Design, and Full stack development. ✅ Personal Mentorship from industry experts. ✅ Live Classes & 24/7 Doubt Support. ✅ Real-life, relevant projects with Placement Assistance #consistency #collab #linkedin