Shivam Panwar’s Post

Have you ever dreamed of working at top tech companies like Google and Atlassian, imagining the incredible perks and prestige? 🌟 Let's uncover recent events in a clear and accessible way: #Google: - Entire Python team layoffs to reduce costs. #Tesla: - Recently conducted significant layoffs, impacting many employees. #Atlassian: - Revoked PPOs of students while still hiring other software engineers. Fond memories of idolizing companies like Google and Atlassian, inspired by their renowned culture and grandeur. With these companies prioritizing profits over their workforce, the concept of a "dream company" is challenged. 🎉 Despite these shifts, exciting opportunities and innovative cultures continue to emerge, reshaping the idea of an ideal workplace. Always stay open to new dreams and possibilities!  

Behind every line of code lies a story of innovation, but sometimes, even the brightest projects face the shadow of layoffs. From shifting market demands to company restructurings, discover the dynamic landscape of software engineering where resilience meets reinvention. 💻✨ #TechTales #AdaptOrAdvance

Folks, another opportunity. Again, I want to share some tips to help improve your hustle. 1. Notice how he's willing to put in a referral? This is the new currency. Don't blind apply, get a referral. 2. Many don't advertise, but lots of folks are willing to refer you if you simply ask. Strike up conversation, come prepared with some questions about the company, and ask for their personal take on working there. Ask and ye shall receive! 3. Comment! I bet there will be a ton of eyes on that post. Commenting will expose those eyes to you too. Just a few things to help tweak the hustle 🫡

Hiring Alert!! Atlassian builds various products enabling teams from all over the world to collaborate and work together. The Anti-Abuse team is primarily tasked with keeping abuse at bay across all of Atlassian's products. An abuse is a costly affair for any company not just in terms of reputation, brand damage, deterioration of customer trust but also in terms of rapid spike in infra cost which underlies all the abuse attacks. The bad actors are only becoming more sophisticated with every passing day and this team needs to be a step ahead to detect, mitigate, prevent and respond to any such attacks. The team operates at massive scale providing guidance and implementing guardrails to drive standardisations and governance thus keeping Atlassian products safe from malicious activities, fraud, impersonation, objectionable content etc. If you are driven by platform thinking, identifying optimisations to bring a step change via AI, building and owning complex ML models, operating at neck breaking scale (Eg: processing millions of events/day) and making the internet better for everyone, this role is for you. Please apply with this link. https://lnkd.in/geiT6zvg Gabor Flamis Enrique P. Calot Martin Heinrich Darshit Kanani Anuj Kohli (he/him)

What surprised me at #LeadDevBerlin? What didn't surprise me: ✅ many conversations about layoffs and "doing more with less" ✅ valuable activities, sessions and exchanges ✅ meeting many former colleagues ✅ excellent organization ✅ spacious venue ✅ great talks Overall it was very energizing and inspiring! What did surprise me? I talked to tens of people and most described their (agile) ways of working quite similarly: 🫨 Product (team or manager) gathers requirements and hands over a solution to the developers to implement. Engineers do not talk to customers and sometimes don't know why they work on things, because things come from senior management or a project team without adequate context. 🫨 No pairing - each person works alone in order to maximize throughput. 🫨 Radical estimations of stories, projects and features in order to communicate a business plan, usually a roadmap as a Gantt chart. Some projects are months long before they are released. A lot of effort goes into making the estimations "correct". 🫨 Manual testing by default, either tester roles or separate teams. 🫨 Refactoring is a special activity that requires approval and scheduling. 🫨 Reliance on others for infrastructure modifications, observability and alerting, such as a platform team. Why is this surprising? There is a lot of literature about ownership, effective product discovery and delivery, about agile and about effectiveness and efficiency, like "Extreme Programming Explained" by Jent Beck, "Empowered" by Marty Cagan and many more. I am not "Mr. know it all". I understand that there is no "one size fits all" and the context can be wildly different, but it seems like in many places things are done the way they are because they were always done this way, or because of misinterpretations or lack of knowledge and leadership to push them. I have recently blogged exactly about this topic: https://lnkd.in/dyqigNsU The futility of estimations: https://lnkd.in/dU9dkZgB And principles for effective teams: https://lnkd.in/dgZq8cMJ

I've been at HashiCorp for 3 months now 🥳 Here's a few tips for getting up to speed in a new role from my first few months: 🙋🏻♀️ Ask for tickets! Tickets will force you to learn your new codebase and make you a productive team member quickly...but make sure to ask for tickets that aren't super time sensitive and won't block another team member's work. 👀 Ask to pair! Your team can help you, but it's up to you to show initiative and ask for help. Asking to pair program on a teammate's current ticket allows them to keep getting work done, gives your teammate a rubber ducky with fresh eyes, and helps you learn. 🏄🏻♀️ Go with the flow! Some days you'll feel like an imposter that is dragging your team down...and other days you'll feel like all the new information is clicking. In the days of self-doubt, remind yourself that you're new and it's okay to take time to get up to speed. #newrole #90daysin #sre

Being comfortable with chaos is a great skill for a software engineer There is always uncertainity - Changing requirements - Changing priorities - Re-orgs - Layoffs - Changing timelines The art is to keep moving and keeping your sane. Chaos is where growth happens. #softwareengineering #chaos

It's Friday, so time for another Fun Friday post! (I need to come up with a better alliterative word as sometimes it's not so "fun"). Layoffs seemed to be slowing in the middle of February. They were still happening but massive numbers didn't seem to be out there, or perhaps the news articles weren't sent to my phone. I found myself so productive, and almost finished the homepage of my website (layout wise). I learned a lot and left off excited to get back into it. Then ... this week happened. More massive, massive layoffs. And I got demoralized and demotivated. Sometimes I start to think "what's the point" and want to give up on my SECOND dream career. And so, back to Baldur's Gate 3 I went. You'll be happy to know I cheesed the Gauntlet of Shar, one of my least favorite parts of the game. 😁 It's okay to engage in this self care, and it absolutely helped me work through an issue and realize WHY I'm having such struggles with my productivity. At my job, I normally have productivity software. I haven't been using any and mistakenly thought I'd have to pay for JIRA. Guess what?! It's free for a limited number of seats! So yesterday, I created a JIRA project for tracking my tasks to complete the website. So far I have around 50 tasks to complete, but they are much more manageable than looking at a blank slate and hoping one day something will be complete. Going forward, I plan to use JIRA for anything I want to accomplish. When I dive into more thorough learning of Unreal 5, I will JIRA that. When I dive into learning generative AI (if ya can't beat 'em, join 'em), I will JIRA that. When I begin learning Blender again, I will JIRA that. Small goals are more approachable than looking at a massive project and hoping one day it will somehow be finished. BG3, and a small break helped me work through this issue, and I plan to start March off next week much more organized and focused. Happy Friday and I hope you engaged in some self care this week, and maybe worked through an issue that was vexing you. ✨

Recently my feed poured with bulk offer revokes from Atlassian. What will you choose? - Attention Required. Imagine a situation, 🔸Country 1: - If a company is laying off or revokes offers then they need to give job assistance and 60 days notice in advance. - If they fail to give notice prior then, they need to give salary for the next 2 months. 🔸Country 2: - If a company is laying off or revokes offers then they need to say thank you for the services. - Now you are a stranger to them. Let me know your comments about which countries I'm referring to. Shouldn't we also deserve such laws to protect us against these mass layoffs. Is it our fault to contribute to evolve tech and then get laid off once your work is done? What do you think about it? Comment to reach wider audiance.

💡 The Real Cost of Layoffs: What We Must Consider 💡 In 2024, over 100,000 tech roles have been cut, hitting even industry giants like Microsoft Dell Technologies, and Intuit. While layoffs might seem like a quick fix for business stability, the long-term effects on engagement and morale can be devastating. (Tell us about it! 🤯) Our community sadly understands the human cost behind these numbers. Research shows rebuilding trust and morale can take up to 2 years... and we think longer with the state of the world. We must approach these decisions with empathy and transparency. Let’s support each other through these transitions. Read more over at the Harvard Business School report. https://lnkd.in/eetfHYQJ #layoffs #communitysupport #redundants #empathyatwork