Software Engineering Career Paths

I Cracked Amazon's New Off-Campus Internship 🎯 (And How You Can Too!) Amazon recently launched a new 6-month internship program—a unique opportunity that runs from July to December, unlike the traditional Jan–June internships. And guess what? I made it in! Here's my journey and some tips for you. Step 1: Resume Shortlisting I applied via the Amazon Jobs Portal, and just two days later, I got an email inviting me to the next step. So, what worked for me? ✅ Unique projects with social impact – These made my profile stand out. ✅ Startup experience – Highlighted my ability to work in dynamic environments. ✅ ATS score of 80+ – A well-optimized resume is critical when dealing with applicant tracking systems! Step 2: Coding Test The 90-minute test on the Mettl platform was intense and covered: - Software Engineering fundamentals (MCQs) - Networking, DBMS, OS, and Linux (MCQs) - One medium DSA coding problem Step 3: Online Assessment The HackerRank round had two parts: - Two medium DSA problems: Problem 1: Solving a greedy algorithm with priority queue logic. Problem 2: String manipulation and logical operations. - Behavioural Assessment: Based on Amazon's Leadership Principles. Step 4: The Interview Nine days later, I received an invite for a 60-minute interview conducted on Amazon Chime with two Amazonians. The question involved solving a stack-based problem. After about 3 weeks of waiting, I got the offer! 🎉 My Advice This new July to December internship program is an exciting opportunity—especially for those who didn’t make it into the 2-month summer internship program. 💡 Focus Areas: Sharpen your DSA skills. Build a solid foundation in core CS concepts. Practice behavioural questions (Amazon values culture fit!). The journey was both challenging and rewarding, and I’m here to say—if I can do it, so can you! Feel free to reach out if you have questions about the process. #Amazon #InterviewExperience #SoftwareEngineering #AWS

The best advice I got as a junior engineer: 1. Make it work: In the initial stages, focus on creating a functional solution. Prioritise getting the core functionality up and running to establish a baseline. 2. Then make it right: Once the basic functionality is achieved, shift your focus to refining the code. Clean up your implementation, improve code structure, and adhere to best practices for better maintainability. 3. Then make it fast & pretty: After achieving functionality and code cleanliness, work on optimizing performance and enhancing the user interface. Ensure that the software runs efficiently and has a polished, user-friendly design. 4. Embrace Continuous Learning: Stay curious and committed to ongoing learning. Keep abreast of new technologies, tools, and methodologies to stay relevant and enhance your skills throughout your career. 5. Seek Feedback and Collaboration: Actively seek feedback from peers and experienced colleagues to improve your skills. Foster a collaborative environment that encourages open communication, leading to innovative solutions and a stronger team dynamic. 6. Prioritize Documentation: Document your code, processes, and decisions clearly. This not only aids in understanding your work later on but also helps team members comprehend and maintain the code, contributing to an efficient workflow. 7. Understand the Business Context: Go beyond technical skills and strive to understand the broader business context. Align your technical efforts with organizational goals to make your contributions more impactful and meaningful. 8. Practice Problem-Solving: Develop a problem-solving mindset by breaking down complex issues into manageable components. This approach not only makes problem-solving feasible but also helps in identifying root causes and fosters resilience in the face of technical challenges. 9. Prioritize Security and Reliability: Emphasize security and reliability in your work. Write secure code, ensure robustness in solutions, and prioritize testing to create software that not only functions well but is also resilient to potential vulnerabilities and failures. Remember, a well-rounded set of skills and attitudes will not only make you a proficient engineer but also contribute to a positive and productive work environment.

Hey everyone! Just wanted to share my interview experience with Microsoft for the Software Engineering Intern position. It was the 𝐯𝐞𝐫𝐲 𝐟𝐢𝐫𝐬𝐭 𝐢𝐧𝐭𝐞𝐫𝐯𝐢𝐞𝐰 𝐨𝐟 𝐦𝐲 𝐥𝐢𝐟𝐞, and I'm thrilled to say it went well! First off, we had a 𝐏𝐫𝐞-𝐏𝐥𝐚𝐜𝐞𝐦𝐞𝐧𝐭 𝐓𝐚𝐥𝐤 (𝐏𝐏𝐓) with Microsoft over MS Teams. They gave us the lowdown on everything from their culture and values to the hiring process. After that, eligible candidates applied through the Microsoft Careers portal using a job ID provided by the company. The 𝐨𝐧𝐥𝐢𝐧𝐞 𝐚𝐩𝐩𝐥𝐢𝐜𝐚𝐭𝐢𝐨𝐧 was pretty standard, asking for basic info like name, address, education, resume etc. Then came the 𝐎𝐧𝐥𝐢𝐧𝐞 𝐀𝐬𝐬𝐞𝐬𝐬𝐦𝐞𝐧𝐭 (𝐎𝐀), which happened the day after applications closed. It had two tough questions(arrays, graphs), really testing your DSA skills. After the Online Assessment (OA), it took about 2-3 days for the shortlisted candidates to receive an email from the Microsoft team regarding the interview. The timings for the interviews were confirmed by our TnP Cell IGDTUW. Once the OA results were declared, the interviews were scheduled for 2 days later than that. Now, onto the interview rounds: 𝐑𝐨𝐮𝐧𝐝 1: During the first round, which took place around 10 am on Microsoft Teams and lasted 45 minutes, my interviewer started with a simple introduction. Then, without wasting any time, he jumped into DSA questions. I was given two medium-level DSA questions focusing on arrays. I explained all possible approaches, from brute force to optimal solutions, along with their time and space complexities. Although there was supposed to be a coding platform for us to use, it wasn't working, so I had to write the entire code from scratch on my laptop's compiler. Despite this hiccup, I managed to tackle the coding part effectively. In addition to the technical questions, the interviewer also delved into my resume, asking about my projects and some core concepts. Fortunately, I was prepared and could answer confidently. The interview ended on a positive note, and the interviewer even asked if I had any questions for him, which showed they valued my input and engagement. 𝐑𝐨𝐮𝐧𝐝 2: After a short wait, I was informed that I passed round one and was onto the next interview, which started just 7 minutes later. It lasted about 45 minutes, and my interviewer began by asking for my introduction. I could tell he was also going through my resume while I spoke. Then came the tough part: a question about Trie data structures. Luckily, I had studied something similar before, so I explained it in detail, including the complexity. After that, the interviewer dove into my core subjects. He asked about everything I'd studied up until that point and even wanted real-life examples of each concept. Thanks to my solid grades and understanding of the subjects, I could answer all his questions confidently. By the end of the interview, I felt really good about how it went. Continued in comments.

Don’t get stuck coding in your software engineer career One of the biggest challenges in a software engineer’s career is learning when and how to grow beyond code. Many engineers enter the field focused entirely on writing syntax, solving algorithmic challenges, and building features. And while these are foundational skills, they’re only the beginning. Yes, code is the entry point. But real career growth comes when you move through the journey: Coding → Development → Software Practices → Software Design → Advanced Tech & Architecture Let me break that down for you Coding You learn syntax. You build features. You fix bugs. This is where we all start and where many choose to stay.But if all you do is write code, you become replaceable by AI easily Development You begin thinking beyond functions and loops. You understand how systems work. You ship products, not just code. You think in terms of impact. Software Practices This is where engineering maturity begins: • Version control • Testing • CI/CD • Documentation • Code reviews You learn to collaborate. To maintain. To improve quality. Software Design Now you’re thinking in patterns, principles, and architecture. You care about scalability, maintainability, and business use cases. You start asking: “Is this the right abstraction?” “How will this scale in 12 months?” You’re not just solving problems — you’re designing systems. Advanced Tech & Architecture At this stage, you’re thinking platform-wide: • Distributed systems • Cloud-native apps • Performance optimization • Security • DevOps You become the one people call when big decisions need to be made. So what’s the point? Don’t stay stuck.Keep growing. Seek knowledge. Build and grow with intention. What’s the next “growth area” you’re focusing on? Other Devs and I can share helpful links or insights to support you.

How I Cracked the Microsoft Summer Internship 2025! 🎉 Hey everyone, I’ve been receiving queries about my recent interview process with Microsoft, so I thought I'd share my experience and what I learned. 📝 ->How did I apply? 🔗 Off-campus with a referral. ->How many rounds were there? After resume shortlisting, I received an online assessment (OA). After clearing that, I had two technical interviews. ->Time taken to solve the online assessment? I solved both questions in about 35 minutes. The problems were easy- medium Leetcode-level problems ->What was asked in the interviews? A single DSA problem was asked in each of the rounds. They were easy to medium problems from arrays and graph. Additionally, the interviewer dove deep into my projects and discussed what I’ve worked on so far. The interviewers were highly experienced professionals who wanted to assess my basic understanding of concepts rather than just problem-solving skills. -> Verdict? Got the offer in 3 days ✅ ->Any tip? Instead of focusing solely on DSA problems, make sure to have a strong grasp of the fundamental concepts of data structures and their internal implementations. Also, be thorough with your projects — you’ll be asked about them in detail! 🔑PS: From what I understood, they don’t have a list of questions prepared! Instead, they build questions from whatever you write in your code or mention during your projects or even introduction. So, it's essential to avoid exaggeration. Speak only about what you truly know . (It completely depends on interviewer as well) Best of luck to everyone preparing for interviews! #MicrosoftInternship #summerinternship #InterviewExperience #TechCareers #SoftwareEngineering #InterviewTips #DSA

10 career rules for software engineers. 1. Think about business impact Your code means nothing if it doesn't solve real problems. I've seen brilliant engineers get stuck: → Writing code that nobody needs → Rewriting systems that work fine → Solving problems the business doesn't care about Focus on the why, not just the how. 2. Be a multiplier The best engineers are multipliers. They: - Share knowledge freely - Help and mentor juniors - Write clear documentation Want to be irreplaceable? Make everyone around you better. 3. Get things done Harsh reality: An unfinished project delivers zero value. I'd rather have working code today than perfect code in 3 months. Be the engineer who: - Solves problems - Gets things done - Ships consistently You're not rewarded for effort. Balance perfection and pragmatism. 4. Don't be a hero Lone developers are a liability. The best engineers collaborate early and often: - Keep people informed - Discuss before coding - Seek diverse perspectives Code is team sport. 5. Take ownership of projects Here's what separates senior engineers from the rest: They keep stakeholders informed before being asked. - Flag blockers early - Communicate clearly - Share progress proactively Communication is your competitive advantage. 6. Guard your focus Your attention is your most valuable asset. Protect it ruthlessly. - Block off deep work time - Say no to unnecessary meetings - Avoid shiny object syndrome One hour of focused work beats eight hours of distracted effort. 7. Embrace feedback Want to grow fast? Treat feedback as free coaching. When I started, I was defensive. Now I know better: - Seek out feedback - Adapt and improve - Ask deeper questions Don’t let ego hold you back. 8. Lead through communication Technical skills get you hired. Communication skills get you promoted. Focus on: - Writing clearly - Explaining complex ideas simply - Leading technical discussions 9. Keep learning The only constant in tech is change. Your learning system matters more than your current knowledge. Build the habit: - Create side projects - Read technical blogs - Contribute to open source 10. Teach others The most successful engineers I know: - Share openly - Teach willingly - Document extensively Teaching is the best way to learn. What principle did I miss? Let me know 👇 ♻️ Repost to share with your team. 👉 Follow Owain Lewis for more.

Your programming career is just like git—full of branches, merges, and occasional conflicts. The difference? You can't just run "git reset --hard" when you make the wrong career move. I've watched dozens of talented engineers struggle with career decisions, and I've come to see our paths like a complex git repository: Some engineers stay on a single branch for 15+ years (I heard of a brilliant dev who remained "junior" by choice despite multiple promotion offers—he valued the lower stress) Others create new feature branches constantly, jumping between specialties without ever merging to main The most successful typically branch strategically and merge value back to their core expertise The most common "merge conflicts" I've observed: 1️⃣ Depth vs. Breadth Paralysis - Getting stuck wondering whether to specialize deeply or expand across multiple domains (hint: T-shaped knowledge usually wins) 2️⃣ Fear of Force-Pushing - Hesitating to commit and push bold ideas due to imposter syndrome, even when they have the right solution 3️⃣ Waiting for Code Review - Expecting someone else to approve your career moves instead of taking ownership of your growth path When I was terrified of taking on a project lead role, I forced myself to commit anyway. That single "merge" accelerated my growth more than months of safe, incremental changes ever could. The engineers who progress fastest are those who: Say yes to projects outside their comfort zone Take ownership even when they're junior Work across the entire SDLC (from PMs to designers to QA to users) Create frequent, meaningful commits (small wins that build credibility) Looking at your career as a git repository, what's been your most successful branch strategy or merge decision?

Hello everyone, I'm thrilled to reflect on my enriching summer internship experience at Amazon as a Software Development Engineer (SDE) intern. Throughout this journey, I've gathered valuable insights and tips that I believe will be instrumental in maximizing internship experience and potentially converting it into a full-time opportunity. The Amazon internship journey is structured with the first and last weeks dedicated to onboarding and offboarding formalities, leaving interns approximately six weeks to showcase their capabilities. Efficient time management becomes vital during this period. Here are some tips to enhance your chances of conversion: 1. Preparation: Familiarize yourself with essential tools and technologies used at Amazon, such as AWS basics and Git. This foundational knowledge will give you a head start during training and project involvement. 2. Set Clear Goals: Establish clear goals from day one and communicate them with your manager and mentor. Understanding the expectations for conversion to a full-time role will guide your efforts throughout the internship period. 3. Embrace Learning: Seize every opportunity to learn. Dedicate time to understanding your team's projects, the codebase, and internal tools. This knowledge will make you a more effective contributor and help you navigate challenges confidently. 4. Structured Approach: When assigned a task or project, engage in high-level design discussions before diving into development. Seek feedback from your mentor or manager to ensure alignment and clarity before proceeding. 5. Regular Updates and Feedback: Maintain open communication with your manager and mentor through regular 1:1 meetings. Keep them informed of your progress and challenges, and seek guidance when needed. 6. Documentation: Document your daily work, as it will be helpful during mid and final reviews. Seek feedback from your mentor before submitting it to your manager. 7. Completion and Closure: Finish your projects effectively within the given timeframe. Ensure that all expected deliverables are met, your work is well-rounded, documented and easily picked up by others if needed. 8. Stay Positive: Remember that an internship is an experience, and whether you get a conversion or not, it's not the end. Keep exploring opportunities, and leverage the experience gained during your internship to open new doors. Understand that external factors beyond your control may influence conversion decisions. A heartfelt thank you to my mentors, teammates, and managers at Amazon for their guidance and support throughout my internship journey. Your mentorship played a pivotal role in my growth as a software engineer. Best of luck to all aspiring interns! #Amazonian #AmazonInternship #SoftwareEngineering #CareerTips #InternshipConversion #ThankYouMentors

No-BS advice for growing and aspiring software engineers from 20 years of lived experiences at Amazon, Google, Paytm, and multiple startups…(this made me who I am today..) 1. Go deep in one programming language, stick with it for 100 days, don’t hop around. 2. Learn at least one strongly typed language, it will teach you to build scalable systems. 3. Master data structures, algorithms, and design patterns, you will use them in real-world systems. 4. Get obsessed with debugging, learn to use logs, tools, and step through unfamiliar code until you find the bug. 5. Think in first principles, don’t take “that’s just how it is” as the answer, go figure out the real reason. 6. When stuck, step away, your best ideas come when you disconnect, not when you force it. 7. Ship an app end-to-end, even if it’s ugly, nothing beats building, deploying, and maintaining your own project. 8. Stay with projects for more than a year, only then will you see the real impact of your design decisions. 9. Don’t chase every shiny new framework, learn the fundamentals and choose tools that stand the test of time. 10. Don’t get intimidated by complexity, every big system is just code written by people like you. 11. Be curious, explore outside your main stack, and learn from every domain you touch. 12. Don’t sleep on AI, start learning and using AI tools, or you’ll be left behind. 13. Crack a FAANG interview at least once, it changes your career, your network, and your earning power. 14. Treat interviews as a learnable skill, practice, mock, and study until you’re good. 15. Don’t job-hop too often, long stints on tough projects get you big-impact, big-trust roles. 16. Learn to spot and grab opportunities, watch for new initiatives, reorgs, or problems no one else wants. 17. Advocate for yourself, document your impact, socialize your wins, and talk about your work. 18. Understand promotions, they’re a game; study how your company does it, and play to win. 19. Keep a brag document, track every win, big or small, and review with your manager regularly. 20. Take control of your career, no one cares about your growth as much as you do.

LinkedIn says I'm a software engineer at Amazon Web Services (AWS). But it doesn't show the rejections and lessons along the way. I was rejected from over 100 companies 7 years ago as a fresh CS grad. It only took one yes to change everything. 7 years ago I started my career at Barclays as an IT Support Engineer. A year later, I landed my first software engineering role at BT Group. Since then I've worked at Gemba Advantage, Trainline and now Amazon. The logos changed. The lessons stayed. Here are 7 lessons I've learned along the way: 0/ You're not expected to know everything. But you're expected to care. So Learn and Be Curious, ask questions and own your work. Growth comes from effort, not from already having the answers. 1/ Design with trade-offs in mind. Work backwards from requirements, and pick the simplest solution that works. Every option has pros and cons, and it's our jobs to factor this into consideration. 2/ Don't suffer in silence. If you've been stuck on a problem for a while, ask for help. Your team wants you to succeed, and no-one wins when you're blocked. 3/ Set boundaries early. There will always be more work. Protect your time and energy. Good managers will also want you at your best, not burned out. 4/ Find mentor and give back. Get yourself a mentor outside your team for objective perspectives. As you grow in your career, give back and mentor others. Pay it forward. 5/ Clarify success early. Ask your manager what success looks like for your role and level. Don't wait until performance reviews to find out you were aiming at the wrong target. 6/ Don't give up. For those looking for their first career job: Remember, rejections are part of the process. Every "no" is an opportunity to take things to the next level. Keep going, and don't give up. Be curious. Be consistent. Be someone others want to work with. #softwareengineering #career #lessons