Salman Bilal Shah

Launching a SaaS is like playing the lottery. Sometimes it works, sometimes it doesn't. Technically, building a SaaS is relatively simple. But from an entrepreneurial perspective, it's much more complicated. More and more people are creating SaaS products. Some say, "I created 5 SaaS in 5 months." Others claim, "12 SaaS in 12 months." That's great, it helps gain experience and learn. But the real value lies in a SaaS that actually works. Finding a SaaS that works is rare, especially in certain African countries. The challenges are numerous. For a SaaS to succeed, you need to go far beyond the code. - Understand marketing to reach the right users. Having a good product is not enough; you need to know how to promote it effectively so it reaches its target audience. - Have a product vision to address a real need. - Build a community: The success of a SaaS depends not only on technology but also on user loyalty. 🙌 If you're looking to build a SaaS that works, reach out to me and let's start the journey together. 🏄‍♂️

21

4 Comments

5 questions in 4 minutes: 1. What does a senior software engineer do? 2. How do you motivate your team? 3. Individual Contributor or Engineering Manager? 4. How do you stand out in Big Tech? 5. Is ChatGPT affecting the job market? Hemant Pandey, senior software engineer at Meta, shares his thoughts. Let me know your thoughts in the comments. Cheers!

1,106

12 Comments

One simple piece of advice that can make your CV stand out is... Instead of just listing what you did in your current or past roles, focus on showcasing the impact your work created. This becomes even more crucial for mid to senior-level positions. Hiring is a two-way street—companies sell their brand, team, quality of work, and growth opportunities, while candidates need to demonstrate what they bring to the table. Your CV and LinkedIn profile are your chances to prove your worth before any real conversation takes place. Make your CV speak for you. If this tip resonated with you, follow along for more such insights ✌ #hiring #resume #cv #job #interview

161

6 Comments

One of the best System Design Mock Interview Videos I ever came across. 1. Effective Communication Skills: • Mark demonstrates exceptional communication skills, a crucial trait for Engineering Managers (EMs), especially when interacting with non-technical stakeholders. His approach—breaking down complex problems, using placeholders, and clearly outlining his thought process—makes technical discussions more accessible and inclusive. 2. Structured Problem-Solving Approach: • Mark doesn’t rush through the problem; instead, he takes deliberate steps, ensuring that each component of the system design is thoroughly explored. His methodical approach highlights the importance of understanding the problem space before jumping into solutions, a valuable lesson for anyone involved in system design. 3. Emphasizing Clarity Over Speed: • Unlike the common pressure to think quickly in interviews, Mark’s strength lies in his clarity and structured thinking. His style—marked by pauses and thoughtful detours—shows that taking time to articulate ideas clearly can be more effective than rapid, but less thoughtful, responses. 4. Importance for Engineering Managers: • As EMs frequently bridge the gap between technical teams and non-technical stakeholders, Mark’s ability to communicate complex concepts in an understandable way is a model for other managers. His style can inspire current and aspiring EMs to focus on clarity, patience, and adaptability in their communication. Key Takeaway: • This mock interview isn’t just a lesson in system design but also in leadership communication. It exemplifies how to navigate complex technical discussions gracefully and effectively—a critical skill for any senior engineering role.

3

Recently I spoke at Lenny Rachitsky's London meetup. Here's a slice of what I shared about hiring in tech: As an Amazon Interview Bar Raiser for 4+ years, I interviewed hundreds of candidates across PM, Marketing, Sales, Engineering, and Design roles for Amazon Web Services (AWS), Devices, and more. There's lots of talk online about the Leadership Principles, I won't rehash that here. 𝘉𝘶𝘵 𝘩𝘦𝘳𝘦'𝘴 𝘸𝘩𝘢𝘵 𝘺𝘰𝘶 𝘮𝘶𝘴𝘵 𝘬𝘯𝘰𝘸 about interviewing methodologies: Some companies evaluate candidates based on individual 𝙘𝙤𝙢𝙥𝙤𝙣𝙚𝙣𝙩𝙨 (this is how Amazon does it). Others evaluate candidates as a 𝙘𝙤𝙢𝙥𝙤𝙨𝙞𝙩𝙚 of competencies, with each interview stage being a re-evaluation, by yet another person, of multiple competencies. Have a look through the slides to see how candidate performance can lead to various hiring outcomes. Navigating this as a candidate can be incredibly challenging and stressful--it's why preparation is key in this current tech job market. Comment "video" below if you'd like a video explaining this in more depth. I'm organising next month's meetup on October 9th, exclusive for subscribers of Lenny's Newsletter. Come say hi 👋🏻

10

2 Comments

I see a lot of career podcasts People always discuss well-being in a common pattern - People worked very hard and prioritized growth and money over well-being in their early years - They got burnt out and then started prioritizing well-being - Now, they put well-being first, leading to better health and a happier life But, If they hadn't focused on growth and money in their early years, would it be possible for them to prioritize well-being later? #wellbeing #career

31

11 Comments

Interviews are an anxious period, and I can't stop refreshing my emails for days. Some of us can turn up and knock it out of the park. For a lot of us, they consume us and take up a large part of our lives. That's just how we get the best results. Interviewing advice is everywhere and I rarely can relate. If I were to take advice from someone about interviewing, I would want it to be more than just tips and tricks I could read online, I would want it to be raw, vulnerable stories and personal anecdotes. This is a clip from a course I have been working on with Nick Cosentino and Nick Chapsas which is going to be released soon called 'Nailing the Behavioural Interview'. As you can see, we have tried to put more than just the obvious, we have tried to inject personality and vulnerability into helping you in this intense part of your life. We want you to connect with us.

29

13 Comments

Where do most of the good Software Engineers apply for jobs? The answer is usually... nowhere Great Engineers are often passive, responding occasionally to messages that really pique their interest, or sometimes reaching out to companies that have great employer branding If you haven't got great employer branding, and you don't work with an external recruitment partner or have an internal talent person doing outbound reach out, really you are settling for who is active and who happens to see your job posting If it was me building my founding engineering team, I would want to know that nearly every Software Engineer that may be relevant to my team (right tech background, worked in the environments I like, location/salary aligned) has been reached out to and knows about what I'm building The value that we can add as recruitment agencies (if a market specialist in what you're recruiting for), we can get your message out to hundreds of relevant Software Engineers in a day Then... We're good at presenting opportunities. Often I'll speak to an Engineer about a role, and they say oh I did see them online but I didn't think it looked that interesting... But we can get them interested in you Maybe you can hire a better-quality Engineer than you ever expected 🤔

22

3 Comments

Since I moved to Mountain View to join the Android OS team, I have walked into a few meeting rooms filled with engineers I’d admired for years - sadly not Jake Wharton as he'd left Google by then :) It was & still is… intimidating. In one of my first meetings, a senior engineer presented a complex architectural solution. Everyone nodded. I hesitated, then raised my hand and asked: "Why don’t we try X instead?" There was silence. Then came a response: "That’s a good point. Let’s explore it." That moment was a turning point. I realized these “brilliant engineers” were just like me—always questioning, always learning, always improving. (not saying that I still don't feel like an imposter sometimes) The biggest perk of working at Google isn’t the free food. It’s the freedom to voice your ideas and grow from the collective knowledge around you. #techcareer #coding #programming #softwareengineering

377

7 Comments

Big tech is trimming the fat🚨 With Google recently planning to axe 10% of its managers and Amazon also planning to flatten its hierarchy—a trend that was started by Meta, interesting times lie ahead in the tech industry. Your career plan might need a pivot if it was to “become a manager, avoid real work, and collect fat paychecks,” as AI and skilled ICs are coming for you. Skilled ICs will thrive, while companies will yearn for faster decision-making and crystal-clear value addition. Middle managers? Just expensive overhead. In this capitalist jungle, you either prove your worth or sadly, pack up. #layoffs #google #amazon #meta

100

2 Comments

When you find yourself with a lot of subclasses often means a data-driven approach is better. Instead of lots of code for defining different subclasses, try finding a way to define that behavior in data instead. #OutFluencer

2

You can’t grow as a software engineer without forming opinions on design decisions. Early in my career, I struggled with this. I’d agree with senior engineers, even when their designs didn’t feel right, because I lacked the confidence to explain my approach. Having opinions shows you’ve thought things through. When you can clearly explain why Design A is better than Design B and highlight potential flaws in Design B, it builds trust and credibility. It’s not just about preferences — it’s about caring enough to dig deep and make informed choices. Without strong opinions, it’s hard to persuade others. But with them, people see you as thoughtful and credible, which builds trust and influence within a team. #softwareengineering

146

7 Comments

At Real Dev Squad, our focus goes beyond just writing code; it’s about building meaningful and robust products. Every feature we work on requires meticulous planning and thoughtful documentation before the first line of code is written. 🚀 Over the weekend, I dived into understanding and creating essential documents for feature development: 1️⃣ PRD (Product Requirement Document) – To ensure clarity and alignment on what we’re building. PRD Link 2️⃣ Went back to basics – Had to learn what things can break with Expo and how to mitigate them effectively. 3️⃣ Design Document – To map out the technical implementation plan comprehensively. One of the key learnings was how to: • Structure a PRD and Design Document from scratch. • Seek reviews effectively by assigning specific sections to team members. Reference 💡 While I initially underestimated the complexity of these tasks, I’ve realized that challenges like these are what push us to grow. A special shoutout to Ankush Dharkar for creating this incredible platform and a supportive community that fosters continuous learning. Also, a big thanks to Prudhvi Reddy for taking out time over the weekend to share valuable insights, it made a huge difference! 🙌 🎯 My weekend was well spent planning the migration to Expo, a developer-friendly framework that will enable more contributors. While it’s been quite the journey (sweaty moments included 😅), at Real Dev Squad, we thrive on pulling off ambitious tasks. And this one will be no exception. 💡 Our app is currently CLI-based, which has its pros and cons just like Expo. What I’m focusing on is making mobile app development exciting and accessible for more developers, not just those working on the backend and frontend. This feels like a real challenge, but it’s one I’m ready to take on. 🎯 My goal for Q1 2025 is to encourage more contributors to get involved in mobile development. Every day here is a chance to learn, grow, and make an impact. Grateful to the team for their guidance and support! 🌱 #RealDevSquad #Learning #Growth #MobileDevelopment #Expo

29

Getting promoted as a senior software engineer does not only involve you being good at what you do, but also how you interact and impact the people around you. 👥 Your technical skills might get you through the door, but your interpersonal skills are what will help you climb the ladder. 🧗‍♂️ It's about fostering relationships, influencing decision-making, and leading with empathy. ❤️ It's also about owning up to your mistakes and turning them into lessons learned. 📚 As a senior, 'fixing the bug', is not where you're expected to shine but rather helping your team to find the 'why' behind it. Take a step beyond coding. Invest time in learning how to communicate effectively, inspire others, and create a positive environment. 🍃 That's how you earn not just a promotion, but respect. 🙏 #inspiringleader #mentoring #coaching #communicationskills -- 👉 Follow me and hit the 🔔 for more value-packed content

6

If you are a junior software engineer/fresh graduate, this is why you should consider working from office instead of working remotely - You get the space to build relationships organically in person with colleagues which is very difficult online. You also get to meet new people and build relationships with them. You get the space to have unplanned conversations and impromptu discussions providing invaluable learnings from senior members of the team. You have discussions which are almost impossible to have online because they are not planned. You observe and learn from behavioral traits of successful senior members of the team; as to how they show up at work, how they promote themselves, what do personalities of successful software engineers look like — thereby developing your own confidence and personality. Learning all of this takes a lot more time remotely. #softwareengineering #workfromoffice

432

38 Comments

Last week at HackMIT, my team (Sanskriti Akhoury, Krish Modi, and Aly Shariff) and I built Runk: an AI-powered e-commerce platform that understands your preferences to display relevant reviews and products. How do we know your taste? Using autoencoders, we assign each user a profile embedding, which our own model updates as you leave more reviews. With these profile embeddings, we rearrange e-commerce search results to display products with the most positive reviews left by people most similar to you first. We also built a Google Chrome extension to interface Runk onto pre-existing sites like Amazon to re-rank these reviews based profile similarity. A huge thank you to HackMIT for making this hackathon an amazing experience. I also enjoyed meeting new people at Massachusetts Institute of Technology, Harvard University and Northeastern University! 👾https://lnkd.in/eyhU3nvK Outside of this hackathon, here’s what I’ve been up to this summer: • Built Guardian at HackThe6ix - an AI wearable for SOS situations. With a Raspberry Pi, Gemini Flash, and Hume AI, it contextually analyzes audio and video of emergencies and sends a summary to first responders. Collaborators: Sanskriti Akhoury, Daniel Hong, and Brian Zhang. 👾https://lnkd.in/ei5-Gu46 • Built Siren - an AI-powered dashcam. It analyzes red light camera runs, illegal turns, speeding, and other driving behaviors using YOLOv8 and algorithms built with reverse geocoding. 👾https://lnkd.in/eKMs2x5t • Joined Mimrr as a Machine Learning Engineer to work on their LLMs for automating code documentation. • Joined WATonomous as an Autonomous Software Engineer to work on self-driving cars. You can view these projects on my new website! 👾https://lnkd.in/e-hWsAxB

982

19 Comments

Take promises about the future with a pinch of salt, weighing up your options carefully. I’ve previously made the mistake of buying into promises of certain job-related prospects, only to have to the rug pulled from underneath my feet once I landed in the role. As such, I will always be more mindful before biting the hands off a company offering lucrative opportunities further down the line. I had also turned down a more substantial role at a well-known company as I really bought into the career opportunities I had dangling in front of my eyes. My situation aside, it all comes down to risk appetite and your own situation. If a role offers prospects of promotions, substantial pay rises, insane opportunities for growth but is also a bit on the risky side (e.g. a startup), you need to make a calculated decision. Don’t disregard the initial offer on the basis that 6-12 months down the line you have been promised the world, it may come back and bite you. Anyway, enough of my scaremongering. You’re all individuals so do as you please 😉 #careeradvice #career

11

3 Comments

In 2024 I've helped more Software Engineers from FANG (is it MANA now?) companies move onto their next challenge than I've done before. Awesome. It always feels great to help people get their new job. I think this is for 4 reasons. 1. These companies have gone through restructuring at a rate they have never been through before. Even if Engineers are still in place, they are concerned about long term job stability. 2. RSU's locked Engineers in on high annual total earnings that no one could compete with. With share prices adjusting to market pressure, Engineers have more options. 3. These businesses are now no longer at the cutting edge of tech, consolidating and focusing on core product lines and killing off new or risky product development they are not the centres of innovation they once were. 4. We had remote working and now there is a big return to the office. This works for some. Not all. If you are in the market for hiring the top tier of Engineering talent (not that this is defined by someone working at Apple/Amazon etc) now is a great time to go to market. If you're looking for a new role, although the market is slower than it was in 2021/2022. There are some great businesses looking to hire, especially so since the start of 2024. Get in touch if you'd like to learn more. Happy jobsearching everyone.

11

It’s been nearly half a year already as a Googler and still loving every minute! Sharing a glimpse into what my SWE work here looks like for the first time. ➤ Like 99% of engineers, I start my day by checking emails and my calendar. ➤ Contrary to what many people think, most of my time goes into writing System Design Docs instead of coding. ➤ Once done, I implement the design docs, run tests, and get my work reviewed. ➤ After the code is pushed to production, I collaborate and assist teams using the service and fix any bugs that arise. Overall, I've found that system design, problem-solving, communication, and collaboration are essential skills in this role. ✅ If you are also preparing for PBCs, I'd recommend focusing on these. You can also reach out to senior engineers who can help you build these skills and prepare for the interviews. They are even offering a FREE trial, so go ahead and book a session: https://lnkd.in/dr3g2X9B These SDEs at Preplaced will take complete responsibility for your preparation - building real-world projects, upskilling, mock interviews, resume creation and more till you reach your goals. 🚀 All the best! #6MonthsAtGoogle #SoftwareEngineer #Collab #PreplacedCollab #InterviewPreparation

165

4 Comments