🕵️IC1 Engineer (Code Cadet)

"I'm in the early stages of my engineering journey, but I'm eager to learn, write code, and make a difference one issue at a time."

  • Role: Junior engineers are essential to our engineering team and play a major role in developing and maintaining our software.

  • Responsibilities:

    • Contribute to code development, adding new features to the software.

    • Review Pull Requests

    • Fix bugs and contribute across various functionalities.

    • Contribute to our team's goal of increasing automated tests (unit, integration and E2E).

  • Ownership: While IC1s make significant contributions, they have limited formal responsibility of the design and longevity of the software. They sometimes work closely under the guidance of more experienced engineers.

  • Learning:

    • You should be hungry to learn and grow in the software engineering field. This includes lots of research, reading, building PoCs and exploration so you are exposed to new ideas.

    • It's ok to ask questions. In fact, we want you to! This is a sign that you are trying to take in as much information as possible to get better.

    • Don't wait hours to ask for help if you are stuck on a problem. It will not be looked down upon. Instead, jot down a list of things you've tried so far so you have this to present to the person who are asking help from.

  • Path to IC2 Engineer:

    • Typical timeframe

      • 1-2 years

      • You need to consistently demonstrate skills of an IC2 in order to be promoted.

    • Expand your skill set

      • Become more of an expert in the code base and contribute to larger projects.

      • Write code that is solid. No obvious bugs should come out of your code.

    • Show initiative

      • Demonstrate your ability to tackle more complex problems and take on leadership responsibilities within your team. This might involve mentoring other junior engineers, providing technical guidance, or helping with project planning.

Last updated