iTranslated by AI

The content below is an AI-generated translation. This is an experimental feature, and may contain errors. View original article
🐡

Reflecting on My First Year as an IT Engineer: A Summary of What I Studied

に公開

Overview

This article summarizes what I, now in my second year as a new graduate, studied during my first year.

While this is just one example, here is a brief profile:

  • No prior IT experience (math major, some programming experience)
  • Aiming to become a highly skilled engineer (specialist or architect) in IT technology

Objective

What this article covers

In the spring of 2023, I was hired as a new graduate engineer at an IT company.
In this post, I will write about what I have studied over the past year, as a way of reflecting on my own progress.

Target Audience

  • People considering employment at an IT company
  • Fellow junior IT engineers aiming for skill improvement

What this article does not cover

Since I am writing about what I actually studied in my first year:

  • There are no "how to become a great engineer" stories from the perspective of a veteran.
  • What you should do varies depending on company culture, job type, and desired career path, so this is just one example.

Background

Here is my basic profile:

  • Company I joined
    • A small-to-medium-sized SIer with about 200 employees (somewhat startup-like)
    • Technologies mainly used include cloud platforms (AWS, Salesforce, MuleSoft)
  • Education
    • Master's degree in Mathematics
  • Pre-employment knowledge
    • Though my specialty was mathematics, I had taken several programming courses.
    • Became interested in programming and used C++ at a hobby level.
  • Career goal
    • Aiming to become an engineer with strong IT skills (specialist or architect).

What I Studied

Knowledge required for an IT engineer can be broadly classified along two axes:

  • Applied / Fundamental
  • IT Technology / Management & Business

With that in mind, I have organized what I studied during my first year.
I have selected genres and certifications, classifying them based on my own sense of things!

What I studied in my first year

*A detailed list is included as an appendix at the end of the blog.
*This is just an example. Also, since I want to be strong in technology, there is a lot of focus on IT (especially foundations).

Reflecting on the First Year

Writing this all down, I realize I have studied quite a lot (details of what I did are listed in the latter half of the blog).

Starting with new graduate training, I read many technical and business books.
Thanks to that, I feel I can now keep up with technical discussions, answer technical questions, and have steadily acquired knowledge.

On the other hand, there is still much left to study, and I feel I must work even harder.
(IT technology is so deep and difficult that I feel like I could never finish learning it even in a lifetime.)

By the way, in order to aim to be an engineer strong in IT, I made the following decisions after joining the company:

  • I will study as much as I can during my first year.
  • I will intentionally make time and dedicate it to study.

Towards the Second Year

Starting in my second year, I plan to increase my output.

Reflecting on my first year, I focused solely on study (input).
While input is important, I feel the necessity of output to broaden my perspective and internalize knowledge deeply.

For the time being, I am thinking of an "input:output = 6:4" ratio, with a slightly higher emphasis on input.

To Those Aspiring to Become IT Engineers

At the beginning, I consider fundamentals to be more important than anything else.

In particular, to aim for becoming an engineer or specialist, you need a solid foundation (this is something I heard from senior members of the company).

For example:

  • If you are a student, I think it is fine to focus on your own specialty and dive deep into your research.
  • For those considering employment at IT companies, you do not need to force yourself to start learning IT.
    • *Note: Be aware that there are hiring criteria for each company.
  • For first-year new graduates, while "technologies used in your immediate tasks" are important, I recommend solidifying your foundations so they will be useful in the near future.

Conclusion

I have written about the things I studied in my first year (partly as a reflection for myself).

To summarize, for an IT engineer, I believe:

  • Studying is important.
  • A lot of study is necessary.
  • Acquiring fundamentals is also vital.

[Appendix]
From here on, I will list the things I studied and the books I read since joining the company.

List of What I Studied

New Graduate Training (April to June)

  • Java Training
    • While reading Perfect Java, I worked on original in-house assignments.
    • Both the textbook and assignments were difficult, and I learned thoroughly.
    • Programming, Object-Oriented Programming, Data Structures, etc.
  • RDB Training
  • Web Training
    • While reading Fundamentals of Servlet/JSP, I worked on original in-house assignments.
    • Learned how the Web works, what a Session is, etc.

Reading ~Technical Books~

Certification Study ~Fundamentals~

Low-Level Systems

Certification Study ~Work Related~

Reading ~General Business~

Events

I also look at IT-related events.
In addition to the ones below, I watch online events (searching on sites like connpass).

  • SECCON Beginners CTF
    • A beginner-friendly competition held once a year.
    • *Actually participated in June of my second year.
    • I was studying CTF because I want to learn about security.
  • Object Oriented Conference
    • You can listen to various lectures related to object-oriented programming.
    • It had a large scale and was quite fun.
GitHubで編集を提案

Discussion