A Junior Cloud Engineer's Quest to Gain Knowledge to Learn More

As a junior cloud engineer at a fast-paced tech startup I often found myself immersed in refactoring, scripting, CI/CD and a multitude of other acronyms. The world of cloud technology was both captivating and intimidating. Especially when I didn’t understand the applications in depth nor the how to work around the infrastructure. When I got stuck I had to ask and it wasn’t always that I got the answers I needed.

It was during this time that I began to understand the importance of acquiring the skill of asking exceptional questions.

“Listen first, inquire later.”

The essence of asking great questions is rooted in active listening. Don’t interrupt, but confirm and note your questions based on the answer you get. The five W’s: Who, What, When, Where, and Why is the best way of start questioning. These question words allowed me to understand the full scope of the topic being discussed before diving deeper.

Using the above questions when I inquired about a colleague’s point of view or expressed a sincere interest in their input, it led to more productive discussions and enhanced teamwork.

Things are the way they are but don’t assume why

There is always a reason why things are the way they are. But don’t assume why, confirm it. It can be an enlightening experience to understand that assumptions could hinder progress.

This meant asking questions like “Why was this architecture chosen?” or “What is the rationale behind this configuration?” before jumping to conclusions. By doing so, I not only gained a better understanding of the systems I was working with but also fostered more effective communication and collaboration with my colleagues.

Context matters

It’s essential to ask contextual questions that dive deep into the specific problem or situation. These questions go beyond the surface and help you gain a more comprehensive understanding of the issues at hand.

For instance, when troubleshooting, asking questions like “When did this problem first occur?” or “What changes were made?” can provide critical context that is invaluable for problem-solving. The more context you have, the better equipped you are to identify the root cause and find effective solutions.

Asking contextual questions not only helps you in your technical work but also demonstrates your commitment to understanding the bigger picture. It shows that you’re not just focused on solving the immediate problem but also interested in how it fits into the broader ecosystem of your organization’s infrastructure.

The more you learn the less you know

Technology is ever-evolving, and there’s always something new to learn. By constantly seeking to expand your knowledge and understanding, you position yourself as a lifelong learner. You become the kind of engineer who is not just content with the status quo but is always looking for ways to improve and innovate.

Asking questions is a skill that goes beyond merely solving technical problems. Remember, “Listen first, inquire later.”

Back to Home