Skip to main content

First Steps at Amazon: Reflections on My First Month

· 4 min read
Shubham Narkhede
DevOps Engineer @ Robert Bosch GmbH

It's been just over a month since I joined Amazon as an Associate Software Developer, and what a whirlwind it has been! I wanted to take some time to reflect on my experiences so far, the challenges I've faced, and the valuable lessons I've learned in this short but intense period.

The Onboarding Experience

Amazon's onboarding process is comprehensive and well-structured, designed to immerse new employees in the company's culture, principles, and technical ecosystem. From day one, I was introduced to Amazon's famous leadership principles—14 guiding values that shape decision-making across the organization. These principles aren't just wall decorations; they're actively referenced in daily discussions and decision-making processes.

The technical onboarding was equally thorough. I spent my first two weeks navigating through Amazon's vast internal systems, setting up development environments, and completing training modules. The learning curve was steep, but the support from my team and dedicated onboarding buddies made the process manageable.

Amazon's Culture

One of the most striking aspects of working at Amazon is the culture of ownership. Everyone is expected to take responsibility for their work and drive results. The phrase "Day 1" is often mentioned—a reminder to maintain the agility, customer obsession, and innovation of a startup, despite being one of the world's largest companies.

Meetings begin with silent reading of documents (called "narratives") rather than PowerPoint presentations. This approach ensures everyone is on the same page before discussions begin and promotes deeper thinking about complex issues. It was initially jarring but has proven to be an effective way to communicate ideas and make decisions.

Technical Challenges

As a new developer, I've been gradually ramping up on Amazon's technical stack. The scale of the systems here is unlike anything I've worked with before. Even seemingly simple operations need to be designed with massive scale in mind.

I've been assigned to work on internal tools that facilitate business operations. My first project involves enhancing a feature that helps streamline inventory management processes. While the scope is manageable for a newcomer, it touches multiple systems and requires coordination with several teams.

The codebase is primarily Java and Spring Boot, with some Kotlin being introduced for new features. I'm also getting exposure to AWS services like Lambda, DynamoDB, and S3—technologies I had theoretical knowledge of but am now using in production environments.

Lessons Learned

In just one month, I've gained several valuable insights:

  1. Documentation is crucial - In complex systems, thorough documentation is not a luxury but a necessity. I've learned to appreciate well-documented code and to maintain that standard in my own work.

  2. Ask questions early - The complexity of Amazon's systems means that getting stuck without asking for help can waste precious time. I've found that asking targeted, well-researched questions early saves hours of potential frustration.

  3. Think big but start small - While Amazon encourages thinking at scale, practical implementation often begins with small, incremental changes that can be tested and validated before expanding.

  4. Data-driven decisions - Every proposal or solution needs to be backed by data. Anecdotal evidence or gut feelings aren't sufficient for making decisions that could impact millions of customers.

Looking Ahead

As I continue my journey at Amazon, I'm setting several goals for myself:

  • Deepen my understanding of distributed systems architecture
  • Contribute meaningfully to my team's projects
  • Improve my ability to write efficient, scalable code
  • Build relationships across teams to better understand Amazon's ecosystem

The learning curve remains steep, but I'm embracing the challenge. Amazon's environment pushes you to grow rapidly, and I can already see how this experience is accelerating my development as a software engineer.

I plan to share more specific technical learnings in future posts as I gain deeper expertise in particular areas. For now, I'm focused on absorbing as much knowledge as possible and contributing wherever I can.

Here's to the exciting journey ahead at Amazon!

Have you recently started a new role in tech? I'd love to hear about your experiences and how they compare to mine. Share your thoughts in the comments!

My Journey in Software Development

· 3 min read
Shubham Narkhede
DevOps Engineer @ Robert Bosch GmbH

As I begin my professional journey in software development, I wanted to take some time to reflect on the path that led me here and share my thoughts on where I'm headed.

The Beginning

My fascination with computers began early. I remember being captivated by the family computer, wondering how it worked and what made it tick. This curiosity eventually led me to pursue Computer Science and Engineering at Rashtrasant Tukadoji Maharaj Nagpur University.

During my undergraduate studies, I discovered my passion for solving complex problems through code. What started as simple programming assignments quickly evolved into a deep interest in software architecture, algorithms, and system design. I found myself spending extra hours in the computer lab, working on personal projects and exploring technologies beyond our curriculum.

Academic Foundation

My academic journey provided me with a strong foundation in computer science fundamentals. From data structures and algorithms to operating systems and database management, I absorbed everything I could. But I knew that theoretical knowledge alone wouldn't be enough in the fast-paced world of technology.

I sought out internships and practical experiences to complement my studies. These opportunities allowed me to apply classroom concepts to real-world problems and exposed me to professional software development practices. I learned the importance of clean code, version control, testing, and collaboration—skills that aren't always emphasized in academic settings.

Looking Forward

As I embark on my professional career in 2018, I'm excited about the possibilities ahead. The technology landscape is evolving rapidly, with advancements in areas like cloud computing, artificial intelligence, and mobile development creating new opportunities and challenges.

I'm particularly interested in exploring:

  1. Full-stack development - Building end-to-end solutions that deliver value to users
  2. DevOps practices - Streamlining the development-to-deployment pipeline
  3. UI/UX design - Creating intuitive and engaging user experiences

My goal is to become a versatile developer who can contribute across the entire software development lifecycle. I believe that understanding both the technical and human aspects of software is crucial for creating solutions that truly make a difference.

Continuous Learning

One thing I've learned about software development is that learning never stops. New languages, frameworks, and methodologies emerge constantly, and staying relevant requires a commitment to continuous improvement.

I plan to dedicate time each week to learning new skills, whether through online courses, technical books, or personal projects. I'll be documenting my learning journey on this blog, sharing insights and experiences along the way.

Community Engagement

Beyond technical skills, I value the power of community in the software development world. I've already benefited immensely from open-source projects, Stack Overflow discussions, and tech meetups. As I grow in my career, I hope to give back to this community by contributing to open-source projects, mentoring others, and sharing knowledge.

Conclusion

As I stand at the beginning of my professional journey in 2018, I'm filled with excitement and determination. The road ahead will undoubtedly have its challenges, but I'm ready to embrace them as opportunities for growth.

I look forward to sharing my experiences, learnings, and projects on this platform. Here's to the adventures that await in the world of software development!

What areas of software development are you most excited about? Let me know in the comments below!

Former FBI Agent Explains How to Read Body Language

· 4 min read
Shubham Narkhede
DevOps Engineer @ Robert Bosch GmbH

In this video, former FBI agent Joe Navarro shares insights from his 25-year career, focusing on how to interpret nonverbal cues—commonly known as body language. Navarro, who worked in the FBI’s National Security Division, utilized these skills in espionage investigations, highlighting how body language plays a critical role in communication, relationship-building, and, for him, identifying potential threats.

Exploring the Future of Artificial Intelligence

· 5 min read
Shubham Narkhede
DevOps Engineer @ Robert Bosch GmbH

Artificial Intelligence (AI) is not just a technological advancement; it's a revolutionary force reshaping industries, redefining jobs, and sparking ethical debates worldwide. As we enter a new era of intelligent machines, AI promises to enhance productivity and solve complex problems, but it also challenges us to consider its broader implications on society, ethics, and the workforce. In this post, we'll explore the impact of AI on key industries, address pressing ethical considerations, and offer some predictions for where AI might take us by 2025.