โพสต์ของ vito leung

2024 Computer Science Grads this one is for you... ✨📢 Our much anticipated Software Engineering New Grad role is now live! This marks the beginning of our student recruiting season, and the Emerging Talent team over at Netflix couldn't be more excited! ✨ https://lnkd.in/gypRpEmd As you get your applications ready, here are some tips from your friendly neighborhood recruiter: 1. Stand out by sharing any hands-on experiences on your resume, even if it's not formal work experience. Have you built something for a campus club? Wrote a little piece of code as a personal project? Add it to your resume! 2. Responsiveness can set you apart! If and when a recruiter reaches out to you to move you forward in the process, that is not the time to play it cool. We love to hear back from you within 24 hours so that we can take action on your candidacy. 3. Practice practice practice - utilize your resources on campus to practice answering both technical and behavioral interview questions. We're excited to review your applications - drop a like if your planning on applying!

It was just over a year ago that Netflix introduced levels for software engineers - after 25 years of only having one level: senior software engineer. But why did the company not have separate levels for so long? Here are the three biggest reasons: 1. Hiring. Netflix was able to hire people attracted to the idea of a “flat” hierarchy, at least levels-wise. 2. A unique culture. While there are several companies without external levels – like at Facebook – they do have internal ones. Thanks to the absence of internal levels, Netflix created a unique culture, unseen anywhere else at this scale. 3. Always paying the top of the market. By encouraging employees to interview externally, and matching external offers, Netflix kept paying the top of the market. It’s an open secret in the industry that to get the highest cash-only total compensation, you should interview with Netflix. Well, at least until the change. This truism was probably also a victim of the change. And why did the company make this change, and how did it play out? In the free issue of The Pragmatic Engineer, we bring the details Read it here: https://lnkd.in/d9nnkWJq #netflix #softwareengineering #career

a sr software engineering is expensive, a sr product manager is expensive, so as a sr recruiter. because? ✅because they know how to be a bridge between the business, users, tech and candidates (obvious depending on the role) ✅because they are strategists and go beyond the short term ✅Because, and not importantly, they are those who, by mentoring and coaching junior and mid-level students, will create more seniors. What many of us job seekers are experiencing now, with ghosting, lack of organization, messy processes, hiring managers who cannot make decisions, lack of standardization of processes, etc. is just the photograph of the lack of sr and therefore the lack of strategy.

How to be a senior software engineer ? • 𝗡𝗼 𝘀𝗵𝗼𝘄 𝗼𝗳𝗳 - Senior engineers exhibit traits learned over time, emphasizing humility and calmness. • 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝗲𝘀 - Seniors prioritize practical business needs over trendy technologies. • 𝗡𝗼 𝗖𝗼𝗺𝗽𝗲𝗻𝘀𝗮𝘁𝗶𝗼𝗻 𝗮𝗻𝘅𝗶𝗲𝘁𝘆 - Over time, engineers prioritize factors beyond salary, such as work-life balance and equity. • 𝗖𝗮𝗹𝗺 𝗳𝗲𝗲𝗱𝗯𝗮𝗰𝗸 - Senior engineers give feedback calmly and constructively, fostering a positive team dynamic. • 𝗜𝗻𝗰𝗿𝗲𝗱𝗶𝗯𝗮𝗹𝘆 𝗰𝗮𝗹𝗺 𝗱𝘂𝗿𝗶𝗻𝗴 𝗮𝗻 𝗼𝘂𝘁𝗮𝗴𝗲 - During crises/Production-issues, senior engineers remain focused and humorous, contributing positively to problem-solving. • 𝗖𝗼𝗱𝗲 𝗲𝘃𝗲𝗿𝘆𝗱𝗮𝘆 - Senior engineers maintain coding habits, often working quietly but consistently, emphasizing work-life balance.

Opportunity

Well, apparently I have another birthday coming up this week. I'll be turning #!$% years old. I've had a bizarre collection of roles I've (successfully/unsuccessfully) fulfilled in that string of exhausting decades: award-winning painter, brilliant theatre director, failed professional actor (my agent wisely dropped me after 100+ fruitless auditions), much-booed yet sometimes admired standup comic, ruthless published theatre critic, out-of-my-depth ice hockey team captain, loyal friend, committed caretaker of my now-late brother and father, and, for the last two decades, innovative and fiercely diligent technical program manager. It's this last one that I'm most proud of--I was able to compensate for my lack of coding proficiency by embracing an innate capability I seem to have to pilot delivery teams through incredibly complicated missions, often in the choppiest of waters, to  safe landings. Unfortunately, the recent 4-year combination of world health calamities and industry-wide economic disasters have set myself and so many other incredibly capable TPM experts adrift in this current unemployment crisis. Thus, I have decided to make a sweeping and risky career change: Starting this Thursday, I will charge headlong into the practice of stealing my neighbors' mail. Every day, without fail. Just kidding. No, I still have faith in myself as a brilliant Technical Program Manager, a captain who can master a ship of any size and condition, safely delivering her cargo and passengers to any demanded destination. And I will keep my resolve to continue looking for a TPM role aboard an organization that I can provide unique value to. So, in lieu of birthday well-wishes via social media outlets such as this one, I'm going to request that y'all try to lead me to gainful employment somewhere. I can offer a years-long body of work experience, the benefits of my continued self-development in the most relevant technical oceans (Cloud-based development, AI proliferation, "Web 3" expansion, and sophisticated international compliance treaties), and, especially, a tenacious pursuit of my thesis that any technical problem can be solved by flexibly guiding teams of intelligent, wonderful, talented people. In closing: HIRE ME! Thank you! LinkedIn Profile: https://lnkd.in/gAPhfscT Resume available via request at [email protected] 

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.

“Your job title says "software engineer", but you seem to spend most of your time in meetings. You'd like to have time to code, but nobody else is onboarding the junior engineers, updating the roadmap, talking to the users, noticing the things that got dropped, asking questions on design documents, and making sure that everyone's going roughly in the same direction. If you stop doing those things, the team won't be as successful. But now someone's suggesting that you might be happier in a less technical role. If this describes you, congratulations: you're the glue. If it's not, have you thought about who is filling this role on your team? Every senior person in an organisation should be aware of the less glamorous - and often less-promotable - work that needs to happen to make a team successful. Managed deliberately, glue work demonstrates and builds strong technical leadership skills. Left unconscious, it can be career limiting. It can push people into less technical roles and even out of the industry.” https://noidea.dog/glue