Bruno Sarmiento

"Software Engineering is dead there is no more job" Last 24 hours there were more than 8000 new jobs on Linkedin in USA. When you filter further for keywords like junior or senior you will that there are ~1600 jobs for Senior Engineers and ~50 for Juniors. Other roles were for other advanced engineering roles that require 3-10 years of experience. The industry is thriving yet people on reddit and twitter are calling for armageddon. You just got to skill-up and learn how to build software. Don't get intimidated by the keywords and requirement for multi-years it's usually just a filter for 'we want someone who isn't a noob' Senior is just a keyword for someone who understand what he is doing. Honestly i saw people in senior engineering roles that the interns run circle around. This is also fair, you live in the age of LLMs. 2018 grad students only had to show calculators and todo apps because they actually built those app themselves. Copying stack overflow doesn't really work you gotta understand the code and know how to apply it in the context of what you are building. In 2025 you can generate 2018 graduate output in less than 10 minute with a code agent and you are expecting to be measured with the same standard ? You want 6 figures for writing React in 2025? Are you are wrong - why would someone pay you huge sums of money when LLMs can do frontend development better than you (check v0) There are those who understood this and pivoted to becoming a product engineer which incorporate other skills that are valuable to businesses or descended to lower layers of the stack that can't be automated by AI like QA, DevOps, Cloud (Reliability will always have a lot of people working on it) Conditions have changed but the effort required has remained the same. You can do more now so more is expected of you.

430

130 comentarios

Heads up, Android devs! 👋 So I just finished diving deep into Android 15's new 16KB page size requirement, and honestly? It's bigger than most people realize. Starting November 1st 2025, if your app targets API 35+ and uses ANY native libraries (your own .so files or ones from SDKs), you're going to need to rebuild them. No exceptions. I'll be real with you - when I first heard about this, I thought great, another compliance hoop to jump through. But after testing it out, I'm actually excited about the performance improvements. We're talking: - Apps launching 30% faster - Camera opens 4-6% quicker - Way less CPU strain - Better battery life The tricky part? Figuring out if you're even affected. Pure Kotlin/Java apps are mostly fine, but if you're using any third-party SDKs, there's a good chance they bundle native code you don't even know about. I spent the last few weeks testing this migration and put together a complete walkthrough - everything from updating your build tools to testing on actual devices. The deadline feels far away, but trust me on this one: don't leave it until October. I've seen too many last-minute scrambles with Android updates. Full guide is in the comments if you want to get ahead of this 📝 Anyone else already started preparing for this? Would love to hear what challenges you're running into. #AndroidDev #Android15 #MobileDevelopment #android

339

19 comentarios

🎯 Master System Design Interviews: 50 Questions That Separate Junior from Senior Engineers As a technical recruiter, I can tell you that system design knowledge isn't just about getting hired - it's about being prepared for real-world engineering challenges. Today, I'm sharing a game-changing resource that could transform your interview preparation. 🔑 Why This Matters: The difference between a $1XXK and $2XXK+ offer often comes down to system design expertise FAANG companies heavily emphasize system design in their interviews These questions reflect actual scenarios you'll face in production environments 📋 What's Included: 50 carefully curated system design questions Real-world examples from companies like Netflix, Uber, and WhatsApp Detailed solutions and architectural approaches Progressive difficulty levels from foundational to complex systems 🎯 Key Categories: Fundamental Concepts API Gateway vs Load Balancer Microservices vs Monolithic Architecture Horizontal vs Vertical Scaling Popular System Designs URL Shortener Chat Applications Video Streaming Platforms Social Media Feeds Advanced Scenarios Distributed Systems Real-time Processing High-Availability Architecture 💡 Pro Tips: Practice explaining your thought process Focus on scalability and reliability Consider trade-offs in your solutions Master the fundamentals before tackling complex designs 🔍 Resources Included: Detailed explanations Architecture diagrams Best practices Common pitfalls to avoid Ready to level up your system design skills? Download the complete guide (link in comments) 📚 #SystemDesign #SoftwareEngineering #TechInterviews #Engineering #FAANG #TechCareers #SoftwareDevelopment #CodingInterview Call to Action: Like and share if you found this valuable Comment with your favorite system design question Follow for more engineering insights Remember: Great system design skills aren't built overnight. Start practicing today! 💪

52

2 comentarios

I just read "Hire and Train Haskell Junior Developers" by Elvie Ciobanu, and it resonated with my experience. My experience hiring junior developers who didn't even know Haskell coming in and building a system with them showed me that two common statements are clearly mistaken: - it's hard finding developers to work on Haskell - using "fancy" extensions or libraries in Haskell makes it harder to recruit and more uncertain that everything will go according to plan I found out that although teaching myself Haskell had been pretty difficult, and I know one other very smart senior developer who faced similar difficulties, mentoring junior devs to help them learn Haskell was pretty easy. Finding junior devs willing to learn Haskell on the job wasn't difficult either. And I totally agree with her that it's how we mentor them and how we communicate with each other, not only with the junior devs but as a team, that makes it possible to use the fancy parts of Haskell without them making it harder to work on the code (which they can, for sure). It's nothing revolutionary: many people are eager to learn, communicate well, create a safe environment for learning and cooperation, and it will be easy to grow a great team that creates great software.

39

2 comentarios

How to break into software engineering (without a job) (And why you don’t need to wait for someone to give you a shot): I’ve been mentoring aspiring software engineers for years. One of the most frustrating traps they fall into? Thinking they need a job to get experience… But can’t get a job without experience. The classic “experience trap.” Here’s the truth: You don’t need a job to get experience. You just need projects with real-world pressure. Here’s how you break in, without begging for interviews: Let’s assume: • You have foundational coding skills • You’re applying to junior dev roles • And you're stuck in that “no one’s hiring me” loop Here’s how you flip the script in 2025: Build one real product from scratch. Not a tutorial. Not a clone. Not another “to-do app.” Build something that: • Solves a real problem • Gets used by real people (even if it’s 10 users) • Forces you to ship, fix bugs, get feedback, improve That’s real experience. Now do this: • Make it open source • Write a short case study on what you learned • Document the process like a dev blog • Share it on LinkedIn and Twitter • Apply again, with proof of execution Suddenly you’re not a “junior with no experience”... You’re a self-starter with a shipped product, user feedback, and proof you can learn and deliver. Most aspiring devs think they need: • To get picked by recruiters • A lucky internship • Or a CS degree with a referral But let’s be honest. You didn’t get into software to wait for permission. You got into it to build cool stuff and solve real problems. You can: • Build your own product • Ship it • Document everything • Apply with confidence And break the “experience trap” once and for all. It’s not about waiting to get hired. It’s about creating your own experience.

177

42 comentarios