Remove Engineering Culture Remove Engineering Management Remove Groups Remove Performance
article thumbnail

A Software Engineering Career Ladder

James Shore

Enough that I don’t do any coding myself, and the managers that report to me don’t have time to do much either.) What I’m really doing is changing the engineering culture at OpenSesame. Culture doesn’t change easily. How It Works Each title has certain skill requirements, which are grouped into skill sets.

article thumbnail

What it’s like to be a backend engineer at Netlify

Netlify

People often end up pairing when there’s a need, or a desire for social contact, and sometimes these turn into huge group sessions that last for hours when nobody watches time , with everybody doing their thing and working almost as if we were sitting right next to each other. Learning on the job is a great part of why I love Netlify.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Leading Remote and Distributed Engineering Teams – Top Takeaways from the Panel

Gitprime

Neither extreme allowed her teams to perform consistently or efficiently. “I And the same goes for distributed managers, as well—particularly when an organization is starting to go remote. We have an engineering manager in Colorado, who was a remote manager before, who helped us understand remote strategies.

article thumbnail

The Rise of the Front-End Developer

LaunchDarkly

Prior to taking on the tactical project manager role, I was in a senior engineering manager role. The technical project manager role was actually pretty new. But as the engineering manager there, I grew a team from zero. A team of me to a team of about somewhere between 20 and 25 software engineers.

article thumbnail

On Becoming a VP of Engineering, Part 2: Doing the Job

Honeycomb

This is particularly hard on engineering teams, where we always have to balance multiple priorities: security, reliability, performance, UX, shipping new features, iterating on existing features, internal developer experience, maintainability/tech debt, quality, scaling, etc.