MoneyGram Haas F1 Team’s Post

if you are in a company building a product, then, it's a necessity to understand the sole purpose and to an extent the business logic behind that product. Here is why, Sometimes, you might just be the one to discover a flaw behind the implementation and the business logic of that product. Your aim is not only to make a functional product but to also make the product realisable and coding won't do just that. I've seen products whose code base are 🤮🤮 yet the company is making lots of money from it. and I've seen products with great functional implementation (in the code) yet they make no money. So, try to know if what you are developing will be recognisable both in the view of your codebase and business logic. Come to think of it, as an engineer or a developer, you find more pride when what you've developed is recognisable and trending positively.

You're a great software engineer if you: 1. Focus on the problems and not the tech 2. Help others around you move faster 3. You're the go-to person for some of your team's scope 4. Are a strong communicator both in speaking and writing 5. You're influence others to go in the most impactful direction 6. Proactively identify and address issues slowing engineers down 7. Focus on implementation quality and writing code that is easier to maintain 8. Know how to drive your projects across teams/functions What else makes a great engineer?

You're a great software engineer if you: 1. Focus on the problems and not the tech 2. Help others around you move faster 3. You're the go-to person for some of your team's scope 4. Are a strong communicator both in speaking and writing 5. You influence others to go in the most impactful direction 6. Proactively identify and address issues slowing engineers down 7. Focus on implementation quality and writing code that is easier to maintain 8. Know how to drive projects across teams/functions What else makes a great engineer?

As a software engineer, I thrive at the intersection of innovation and problem-solving. Each line of code represents an opportunity to build something impactful and transformative. In the realm of technology, we have the power to shape the future through our creativity and dedication. I am passionate about crafting solutions that not only function flawlessly but also elevate user experiences. Every project is a chance to learn, adapt, and push boundaries. Let's embrace this journey of continuous improvement and embrace the challenges that come our way. Together, we can harness the potential of technology to solve real-world problems and make a meaningful difference. Here's to building a tomorrow that is smarter, more efficient, and full of endless possibilities.

Can’t figure out how to hit that next level in your engineering career? Try these 10 things 👇🏼 1/ Be consistent in your learning 2/ Volunteer for challenging projects 3/ Operate at the next level in your head 4/ Get in the driver’s seat of your skills/career. 5/ Manage up in your communication and projects. 6/ Become the go-to person for your product area. 7/ Keep a brag doc of your mistakes/learnings/wins. 8/ Make friends and work with folks 1-2 levels above you. 9/ Join the oncall rotation and work hard to make things better. 10/ Share your goals with your manager and work on them together. Apply this principles now, and when the next promotion cycle comes around, your promotion will be a no-brainer. 🧠 They’ve helped me get unstuck and go from mid-level to senior engineer to tech lead, and now manager / team lead. Let’s all help each other and level up together 🚀 Share your favorite tip, or something else that’s helped you 🙋♀️🙋♂️ - - - - - - - - - - - - - - - - - - - - - - - - - - - - If you liked this post, you’ll probably love my weekly newsletter: https://lnkd.in/e8d5ymr3 

Getting into the tech industry sounds like a solid goal. But once you get closer to actually applying for a job, you realize that you have a lot of options — which means that you also have to make a lot of decisions. Even as a junior dev, you’ll choose among a wide variety of roles, areas of expertise and types of companies to work for. To help you make a choice that works for you, you need to consider what you want from your career and what brings you satisfaction in a job.

🍪 You are about to step up your engineering game? Read this great list assembled by Caleb Mellas! Recommend following him! #softwareengineering #developer

You have to do something very impressive to: a) get the attention of a Software Engineer (usually money or projects) b) keep the attention of a Software Engineer (usually money or projects) In today's landscape, the battle to attract and retain top software engineering talent is fiercer than ever. Imagine working on something that could redefine the industry or revolutionise the way we live. That's the kind of challenge that draws in engineers. However, if the ground-breaking project fades, so does the talent. In an era where skills trump tenure, loyalty is closely tied to how intellectually stimulating and interesting the work is. And if your projects are complete and they move onto BAU - the last thing you want is an unhappy engineer hanging around. We are djr 🔵⚪

If you're a software engineer working on a product, you are doing yourself no favors if you're disconnected from what it takes to deliver a feature to customers and what it takes to sell and support that feature. I wouldn't have listened to my own advice about this in the past, but the reality is that there's a world of fascinating, high-value problems that you otherwise aren't going to be exposed to — perhaps more interesting than building Yet Another Product Feature. The work to deliver customer value doesn't end just because you deployed the code — indeed, your work can make everything that comes after that MORE difficult if you aren't attuned to the broader process. Without this context, you're never going to truly understand how to deliver value to customers — and if you aren't deeply interested in that, then I'm not sure you want to be working as a software engineer?