Burag Cetinkaya’s Post

My team is hiring a Staff engineer to focus on our B2B content marketing work stream. Come join our talented team. Best part, you get to work with an amazing manager Praveen Boddu Please don't DM me. If interested, apply directly on LinkedIn. #linkedin #opportunity

If you are looking to grow the engineering leaders on your team, consider signing them up for this insight crammed short program.

If you want to work in tech but come from a non traditional background, check out LinkedIn’s technical apprenticeship program. I personally work with many talented graduates of this program and would love to see more people take advantage of it.

We are #hiring, come work with me at #LinkedIn

Embarking on a new engineering leadership journey? The cornerstone: deep understanding of context 🧐. As an engineering leader, you are expected to drive stellar products, set up efficient operations and cultivate thriving teams. However each company, product and team is unique. How do you get started in the most efficient way? It is easy to lose track of time as you dive deep into product specs, design documents, or team wikis. But, at the end of the day these are just outputs that were generated for a conext, at a certain point in time. Thus, your focus should be to understand the reasons more so than the obvious results. ❓ More often than not the context is distributed over a long time across multiple people & teams and is seldom written down. Best way to gather this context is to methodically look at the industry, the company, the team, and the product. As there are multiple outside sources to gather industry and company context, I will focus on the latter two. Best way to get the team and product context is by taking in different perspectives and synthesizing it based on your experiences. This is usally best done in a 1-1 setting. I have found that getting a sample cohort comprised of engineering squads, product partners, customer service reps, and key executive stakeholders covers a variety of dimensions to give a good average. In your 1-1s, focus on discussing the non-obvious such as what was not built correctly, what was decided against, what featureset was completely revamped, which teams were disassembled or which charters were moved and combined. Once equipped with the context, remember that it isn't static. As our teams and tech landscapes shift, our understanding of context and subsequent decisions must evolve. As a new member of the team you will have the luxury of having a fresh perspective and can be in a position to identify shifts in context that others are to close to see. This will allow you to make decisions that fit your team & product's unique needs, leading to enhanced outcomes and morale. #EngineeringLeadership #MasteringContext #EngineeringLeadershipOnboarding