PE – Intern at Infracloud, Remote

Hey!!! I have made 7 million in US stock investment. Here is how I did it.

Before you apply: Here is an interview Q&A for you: Click here

NOTE: Here is why some companies may not hire you.

What are we looking for?

1. You are an engineer with an eye for constant improvement. You look at improving the code and tooling, the commands you use, the user-facing documentation, and everything that makes great and beautiful products possible.
2. You can talk fluently to computers using Golang. If you know it well, you fit right in. You believe languages are just tools to solve problems.
3. You really like to solve problems, complex engineering problems!
4. You have some exposure/understanding of systems. Out of curiosity, you tried to understand the routing, load balancing in a web server, or how the Linux filesystem was built and structured the way it is. You may not have worked extensively, but you have definitely dabbled with it and can think as well as understand how systems interact with each other.
5. You can express ideas and your opinions, and you aren’t shy to say no if you don’t know something. We are not hiring Wikipedia after all, are we?

What will you be learning and doing?

1. You will be part of a team-building product to solve the next generation of problems in the programmable infrastructure. It’s you who will start by defining the feature and how it will make the life of the end-user better, and then make it into a reality.
2. You will most likely be programming in Golang. Most likely, some part of your work might be open source and worthy of talking and presenting at conferences and meetups.
3. You will work with cloud-native technologies, including Docker, Kubernetes, Prometheus, Service Meshes, and Distributed Tracing, in some form or another.
4. You will also be working with one or more public cloud platforms from AWS/Azure/Google Cloud Platform (again, you may not know any or some of these technologies, and that is not a deal-breaker)
5. Your workflow will be driven by tools such as GitHub, Slack, and a lot of asynchronous communication with distributed teams. “GitHub issues” will be your new reincarnated Jira 😉