In APA, books are cited with the author's name, publication year, title, and publisher. Journal articles include the author's name, year, article title, journal name, volume(issue), and page range. Websites require the author, date, title of the page, website name, and URL. Videos are cited with the uploader's name, upload date, title, and URL. Each style ensures clarity and proper attribution for the source type.

In-text Citation:

In-text citations provide credit to original sources and guide readers to the full references. They can be formatted parenthetically (Author, Year) or narratively, incorporating the author's name into the text (Author, Year). Parenthetical citations are used when the author's name is not part of the narrative, and narrative citations when it is. For multiple authors, use "(Author1 & Author2, Year)" for two authors, and "(Author1 et al., Year)" for three or more authors.

Formatting

APA Style papers require 1-inch margins, 12-pt Times New Roman font, and double spacing. The title page includes the paper title, author's name, institutional affiliation, course information, instructor's name, and due date. Abstracts provide a brief summary on a separate page. Body paragraphs use headings and subheadings for organization. The reference list starts on a new page. Tables and figures should be placed each on a separate page with titles and numbers.

Reference Drafting

Reference list entries include the author(s), publication year, title, and source details (publisher, journal name, volume/issue, pages, or URL). Each entry is formatted according to the source type (books, articles, websites, etc.). References are listed alphabetically by the author's last name, ensuring easy navigation and consistency.

My learning goals are to master my business skills and use them, together with my technical skills, to get a strategic job on AWS. For example, as a Principal Software Engineer. The objective of AWS is to allow application providers, ISVs, and vendors to quickly and securely host their applications. And I think my abilities and experience can be very relevant in this context.

Important information:

Organization: Amazon Web Services (AWS)

Mission: Strive to be Earth's most customer-centric company

They serve: Application providers, ISVs, and software vendors

Analytical reflection:

I have learned that I love to work in the cloud computing field, as it is so important for modern society. I need to organize my experience and knowledge better so that I can have more opportunities in the job market.

Lessons:

I highly fit the AWS goals and concepts. Their motto (Work hard, have fun, make history) is something I believe in and have brought with me since I started working. This project helped me to understand how to organize my background better to get my desired job on AWS.

Services (AWS). To create this outline, I consulted the following sources:

- AWS Job Description:

- https://www.amazon.jobs/en/jobs/2413193/principal-software-engineer

- https://www.amazon.jobs/en/jobs/2554542/principal-software-engineer-

aurora-storage

- LinkedIn profile of people currently occupying this position:

- https://www.linkedin.com/in/yurizarubin/

- https://www.linkedin.com/in/felipekamakura/

- Strengths: experience in technical team leadership, experience attending

and direct relations to end clients, experience in making product decisions,

experience and ease of solving complex problems, good practice in technical

background, ease of communicating and managing people, and experience in

career development of others, experience in drawing software and cloud

architectures, experience in writing software code, experience with AWS

technology, had worked with an AWS partner, know people inside AWS of sales

and management teams, experience in working close to C-Level, bachelor`s

degree in the Computing field

- Weaknesses: lack of fluent English speaking, less than 5 years of experience

in large-scale distributed system development, no Master's or PhD in Computer

Science, no network with people from the engineering team from AWS, no

large experience in big companies.