# Navigating the First Month as a Data Engineer at Amazon: Lessons Learned
In my first month at Amazon as a full-time data engineer, I've noticed that the experience at 30 years old differs significantly from when I was 22.

### 1. Be Organized by Taking Notes

The key here is to write everything down. During this initial period, it's acceptable to ask questions, as people don't expect you to know everything. Whenever I receive answers from my coworkers, I make it a habit to jot them down, with the aim of transforming the unknown into knowledge.

This practice has proven to be unexpectedly beneficial. In a meeting with a senior engineer, I inquired about his approach to a project, and he turned the question back on me, asking about my approach. Thanks to my note-taking habit, I was able to showcase how I'd broken down the project into actionable steps, detailed my assumptions, and outlined the actions I'd taken. This approach streamlined our discussion and made his feedback highly relevant to me.

### 2. Set Up 1:1 Meetings – Incredibly Helpful

As part of the new hire onboarding plan, I was advised to arrange 1:1 meetings with key team members, colleagues from sister teams, and my reporting line. Last summer, the prospect of meeting so many people initially made me want to avoid it. I didn't relish engaging with numerous individuals, and I worried they might view their time with me (an intern) as unproductive.

However, this year, I approached the task differently. I researched what questions to ask and prepared a self-introduction. To my surprise, all the meetings went smoothly. Being genuinely curious about people's backgrounds and current work, and seeing them as individuals rather than just coworkers, made a significant difference.

Why is this important? Despite Amazon's thorough documentation, valuable knowledge and experience are often held by individuals, akin to relying on tribal elders for wisdom in ancient times. By introducing myself and building connections, I gained a solid foundation for understanding their roles, experiences, and projects. This made it easier to reconnect or seek guidance during my time here.

### 3. Actively Engage in Meetings

Last summer, I often found myself drifting during meetings because I struggled to comprehend many topics that weren't related to my projects. This time, I set specific goals for each meeting: asking 1-2 questions, noting unfamiliar terms or projects, and researching them afterward. Not only did this keep me engaged, but it also increased my visibility within the teams.

### 4. Ask Questions – The Most Important Skill
Above all else, asking questions is the most crucial skill. Reflecting on my career, I realized I learned how to search effectively after becoming a software engineer and how to ask questions throughout my journey.

Consider these key points:

1. General Questions vs. Specific Questions
Recognize when to ask broad, general questions and when to be as specific as possible. While I don't have a definitive answer, keeping this in mind can be valuable.

2. What Questions to Ask and Whom to Approach
I've occasionally posed the same question to different people, only to receive varying interpretations. Over time, you'll develop a sense of which type of question is best suited to each individual. This approach is also endorsed by my manager, as learning from everyone allows me to shape my own perspective and style.

### 5. Know Your Value

What value can a new hire bring to the team? Here are a couple of points:

1. Fresh Perspective on Workflow:
My manager has emphasized that as I become more familiar with the team and the work, I may lose this valuable fresh perspective, which allows me to identify potential improvements in our workstyle.

2. Documentation Correction and Suggestions:
Providing insights and recommendations for refining documentation can play a pivotal role in enhancing the team's overall success.

3. Continuous Learning:
Another important contribution a new hire can make is a commitment to ongoing learning. Sharing knowledge gained from external sources or experiences beyond the team can introduce novel insights and perspectives, enriching the collective knowledge of the team."