Defining a good engineer

  

Source: Medium

Working in a startup environment for almost a decade has given me privileged access to a fast-paced culture of innovation, exploration, and a fail-fast approach. I followed the standard progression ladder: intern, junior, mid, senior, and eventually moved to the engineering management track. Over time, many people I grew with later moved on to work at other companies, becoming highly-respected contributors there. It would be fair to say they are good engineers.

Looking back at the journey of my peers, mentees, and my own, it seems harder than ever to be a good engineer.

Defining a good engineer

What does it mean to be an engineer? As software engineers, we are:

  • Responsible for translating complex problems into efficient and scalable solutions
  • Tasked with analyzing user requirements, designing software architecture, writing code, and testing and debugging software
  • Expected to stay on top of trends, seeking new business opportunities and ways to improve existing products

So no — engineering doesn’t equal programming. Sometimes, that is the smallest part. It definitely appears so as one acquires more experience, as shown in the figure below.

Baca Juga