How to Advance as a Software Engineer

I'm a Software Engineer working at AWS, with over 7 years experience. The last few years of my life has taught me a lot. If I could talk to my younger self or any other junior engineer for that matter, here's what I would tell them:  [1] Learn fundamentals, not frameworks. Frameworks change quickly, but core concepts stay with you your whole career. Strong fundamentals make you adaptable, confident, and effective anywhere. [2] Design before coding. If you can’t explain your solution clearly, then the implementation will be unclear too. Draw it. Write it. Challenge it. Then build it. Good design reduces rework and gives you a direction worth building. [3] Read code, not just write it. Study the systems you work in and understand why things were built the way they are. Reading code builds real context — and context makes you faster, wiser, and more effective. [4] Write for humans first, computers second. Choose clear names, small functions, and simple logic, and follow the practices set by your team and engineers before you. Maintainable code makes everyone’s job easier. [5] Know when not to build. Not everything needs more code, sometimes the best solution is removing or reusing what already exists. Favour simplicity, avoid premature abstractions, and keep your systems lean. Code is a liability. [6] Write things down. Design docs, architecture notes, and thoughtful PR descriptions show your thinking. Writing brings clarity, and clarity helps the entire team move faster. [7] Don’t shy away from operations / devops. Many engineers avoid this work, but understanding how your code runs in production is one of the most important parts of the job — build it, own it, run it. It leads to safer judgement. [8] Become great at debugging. Most engineers can build features, but not many fewer can fix issues under pressure. Learn how to troubleshoot calmly using logs, tracing and systematic problem solving. [9] Own your career path. If you’re in a job that doesn’t help you grow, work with your manager to change that. If things still don’t improve, find a place that supports your goals. Your career is yours to steer. [10] Communicate clearly and earn trust. Be honest about what you know and what you don’t. Listen carefully, share progress early, and follow through on what you promise. [11] Keep pushing yourself and don’t give up too quickly. There will be tough days and difficult problems. Stay patient, and keep pushing through. Growth often happens right after things start feeling uncomfortable. Resources to level up as software engineer: → The Pragmatic Engineer with Gergely Orosz for industry insights. → System Design One by Neo Kim for system design fundamentals. → Coding Challenges with John Crickett for real world project ideas. → Connect with engineers like Anton Martyniuk, saed, Alexandre Zajac, Demitri Swan, Sanchit Narula, Daniel and Mohamed A. for daily engineering wisdom. #softwareengineering

I am a Software Engineer at Meta with almost 2 decades of experience. Here’re the 5 learnings if you want to grow faster as a SWE: 1. Know the next level before promotion After you are performing well at your current role expectations, start approaching the next level. - Learn from seniors, understand their perspective - Look for areas you can help & can get noticed In short, prove that you deserve the promotion before you ask for it. 2. Become your own user - go on reddit or twitter threads - read through the users feedbacks and conversations - be empathetic & maybe have a conversation with few users This shift helped me move beyond just shipping features to actually improving the experience. 3. Data is your saviour Start diving into logs, events, and exceptions more deeply. - Where are users spending the most time?  - What’s making them drop off? - What are the most common exceptions?  - Which workflows are unintuitive? You can make better engineering decisions if you spend some time consuming the data 4. Every problem is not yours to solve Ask yourself: - Is this issue truly high-impact, or am I just trying to get it off my plate? - Is this a problem I should solve, or is it better to guide someone else to take it on? - Delegating was tough at first. But it’s crucial to identify your problems and delegate rest. The best engineers I’ve worked with aren’t the ones who take on the most work—they’re the ones who ensure the right work gets done by the right people. 5. Be a force multiplier - document more to save others time - build tools and scripts that automate tedious tasks - Guide others to help achieve their goals   Your team will move faster, and you will become more valuable—not just as an engineer but as a force multiplier. => Final Thought: The biggest shifts in my career didn’t come from just writing better code—they came from these small shifts. If you’re looking to grow as an engineer, try incorporating some of these steps into your own journey. Raman Walia

7 pieces of advice from a Senior software engineer (me) for software developers in their 20s who want to grow fast to the next level: I learned this after effing up 10s of times, attending postmortem & observing my seniors, follow this and it will fast-track your career growth: 1// Know the next level before promotion   - study the expectations of the next level early.   - observe senior engineers, ask questions, and understand their thought process.   - prove you’re already operating at the next level before asking for a promotion.  2// Become the user & engineer - read Reddit, X, and user forums, see what real users complain about.   - go beyond just shipping features, improve the experience.   - if possible, talk to users. the best engineers are empathetic.   3// Data = Cheat Code - check logs, events, and exceptions, where are users struggling?   - identify drop-offs, slow workflows, and unintuitive flows.   - let data guide your decisions, not just assumptions.   4// Not every problem is yours to solve   - ask: should I solve this, or guide someone else?   - learn to delegate, it’s not about doing more; - it’s about making sure the right things get done.   - the best engineers aren’t workhorses; they’re strategic.   5// Write code that saves time for others   - automate boring, repetitive tasks.   - document your work so others don’t struggle.   - invest in tools and scripts, it pays off exponentially.   6// Build strong relationships   - your career will grow faster if you have good mentors and peers.   - learn to communicate clearly, especially in writing.   - people don’t just promote great coders, they promote great collaborators.   7// Think like an owner, not just an engineer   - don’t just wait for tasks, proactively find ways to add value.   - be someone who sees problems before they become blockers.   - own your impact, not just your code.  The biggest jumps in my career came from changing how I think, prioritize, and collaborate.  If you’re in your 20s and serious about growing fast, start applying these today.

A collection of learnings from my 15-year Software Engineering career at companies like Meta, Pinterest, and Walmart. 1. To learn how to code, you must write code in an unstructured environment. Tutorials can help initially, but don't get stuck in tutorial hell: these engineers can't actually solve problems. 2. The only way to learn how to write good code is to write a bunch of terrible code first. It is fundamentally about the struggle. 3. Debugging is effectively playing a game of detective. Becoming an expert debugger in a large, complex codebase will make you extremely valuable to any company. 4. For software engineers, most of what you learn in school won't be relevant on the job. The biggest value of a university education is your network. Invest in getting to know students and faculty. Don't worry too much about grades. 5. Networking is about building long-term relationships built on trust and value. Give more than you take and your network will grow rapidly. Remember this phrase: "Your net worth is your network." 6. Everyone in tech faces imposter syndrome. Consider imposter syndrome as an opportunity to learn from people who are further along. Actively seek out feedback and talk to people. 7. Tech interviews are immensely broken and your interviews will probably differ from your job. View interviews as a learning opportunity where you get to meet some other cool, smart people. 8. Realize that the average person will spend < 10 seconds scanning your resume. No one is as interested in you as you, so you need to keep things short. Your resume should be 1 page long. 9. Feedback is the secret to rapid career growth. Make it easy for others to give feedback by introspecting and asking for specific parts of your behavior. A lazy “Do you have any feedback for me?” will often be met with a similarly lazy “Nope, you’re doing great!” 10. If you're not sure what company to join, go to a larger, well-respected company (FAANG) as your first job. Junior engineers benefit from the consistency and stability of Big Tech. 11. Onboarding is a magical time when you get a free pass to ask as many questions as possible, request people's time, and build foundational relationships. Work with a sense of urgency when you're new to a company. 12. The relationship with your manager is the most important relationship you'll have in the workplace. You should proactively drive meetings and feedback with your manager; don't wait for them. 13. Getting promoted as an engineer is not just about skill or output. You also need scope and trust. Most promotions are deliberately planned months in advance. If a promotion is important for you, bring it up with your manager well in advance. 14. Most engineers don't negotiate their offers, but they should. The most important tool for negotiation is leverage. This means competing offers. I put this all together in a 1.5-hour video here: https://lnkd.in/gAH4Q2pD

In the last 15 years of my career, I’ve worked as a software engineer across Google, Paytm, Amazon, and multiple startups.  Here are the most impactful lessons I’ve learned that will help you become a better developer and perform better in your career:  1//  Good Code Can’t Fix a Bad Product   ↳ You can write the cleanest, most optimized code ↳ But if the product doesn’t solve a real problem, it won’t matter.   ↳ Understand the business impact behind what you build.  2//  Be the Most Helpful Person on the Team   ↳ The best engineers aren’t just technically strong, they enable others to do their best work.   ↳ Help teammates debug issues, improve designs, and write better code. It pays off.  3//  Look for Simple Solutions to Complex Problems   ↳ Complexity is easy. Simplicity is hard.   ↳ The best engineers know that less code = fewer bugs.  4//  Success is Probability—Show Up More Often   ↳ A big part of success is just being present, trying, and iterating.   ↳ The more you put yourself out there, the luckier you get.   5// Ask Why? More Often—It Creates Clarity   ↳ Most technical problems are not about the best solution—they’re about the right problem to solve.   ↳ Keep asking why until you truly understand the root issue.  6//  There Is No Best Tech Stack—It’s All Trade-offs   ↳ Every tool, framework, and architecture decision comes with pros and cons.   ↳ The best engineers make informed decisions, not emotional ones.  7// You Are Rewarded for Creating Value, Not Just Writing Code   ↳ You don’t get promoted for just writing more code.   ↳ You get promoted for solving real problems, improving systems, and making the team better.   8// Writing is How You Clarify Your Thinking   ↳ Engineers who write well communicate better, influence better, and get promoted faster.   ↳ Start by writing better PR descriptions, design docs, and technical explanations.  9// Understand the Business, Not Just the Tech   ↳ The best engineers don’t just focus on code—they understand why the business needs it.   ↳ Learn how your company makes money and how your work impacts that.  10// Find a Mentor or Coach—Don’t Struggle Alone   ↳ The fastest way to grow is to learn from someone ahead of you.   ↳ Don’t wait, reach out to senior engineers, ask questions, and get feedback.   11// Imposter Syndrome Never Goes Away—Keep Learning   ↳ Even the best engineers feel like they don’t know enough.   ↳ The difference? They keep learning, keep building, and don’t let fear stop them.  Your career is built through small, consistent improvements over years.   Apply these 11 principles, and you’ll move ahead…  

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.

✅𝐖𝐨𝐧𝐝𝐞𝐫𝐢𝐧𝐠 𝐡𝐨𝐰 𝐭𝐨 𝐠𝐞𝐭 𝐭𝐡𝐚𝐭 𝐧𝐞𝐱𝐭 𝐩𝐫𝐨𝐦𝐨𝐭𝐢𝐨𝐧 𝐢𝐧 𝐬𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐢𝐧𝐠❓ After 7 years in this industry, I've spent a lot of time reflecting on career growth, and it's definitely not just about lines of code. For me, and from what I've observed in successful colleagues, it's about... 1️⃣Deep Impact Beyond Code: It's foundational to write clean code, but connecting your work to product roadmaps and business impact is what truly makes you indispensable. Be a problem-solver, not just a task-completer. 2️⃣Master Communication: Your technical skills are vital, but so is clearly articulating ideas, progress, and challenges to both technical and non-technical stakeholders. Communication is massively underrated. 3️⃣Proactive Ownership: Don't wait for tasks. See a gap or an inefficiency? Take the initiative to propose solutions and drive improvements. Demonstrating ownership shows you're ready for more. 4️⃣Embrace Feedback: Actively seek feedback from your manager and peers, and be willing to give constructive feedback yourself. Feedback is your fuel for growth and leadership. 5️⃣Document Your Wins: Keep a running log of your accomplishments, quantifying impact whenever possible. Having tangible examples makes promotion conversations much stronger. Ultimately, 𝐔𝐥𝐭𝐢𝐦𝐚𝐭𝐞𝐥𝐲, 𝐩𝐫𝐨𝐦𝐨𝐭𝐢𝐨𝐧𝐬 𝐨𝐟𝐭𝐞𝐧 𝐜𝐨𝐦𝐞 𝐰𝐡𝐞𝐧 𝐲𝐨𝐮'𝐫𝐞 𝐚𝐥𝐫𝐞𝐚𝐝𝐲 𝐧𝐚𝐭𝐮𝐫𝐚𝐥𝐥𝐲 𝐨𝐩𝐞𝐫𝐚𝐭𝐢𝐧𝐠 𝐚𝐭 𝐭𝐡𝐞 𝐧𝐞𝐱𝐭 𝐥𝐞𝐯𝐞𝐥. It's about consistently demonstrating you're ready for more, even before the official title change. What are your thoughts? What has truly helped you (or someone you know) get to the next level in software engineering? Would love to hear other perspectives! 👇 ✅Consider connecting on more platforms with me: 📍Instagram - https://lnkd.in/gN35u52q 📍Whatsapp - https://lnkd.in/gJjXjDSm 📍Telegram - https://t.me/techwitharchy 📍YouTube - https://lnkd.in/gu9UJJcB #SoftwareEngineering #CareerGrowth #TechLife #Promotions #EngineeringLeadership #CareerAdvice #TechIndustry