Vincenzo Acunzo’s Post

What does Amanda Willard MBA, SPHR, SHRM-SCP of Amazon’s Strategic Workforce Development, Worldwide Talent Development Team have to say about Amazon Shreveport's Reliability & Maintenance Tech Positions? Read on....! External job seekers can enroll in one of a handful of online courses through Unmudl including Introduction to Mechatronics, Mechatronics for Equipment Maintenance and Principles of Control Systems. Courses require about 4-6 hours per week of study over an 8-10 week period. The courses are self-paced, allowing job seekers to juggle other obligations.   “These modules help a job seeker increase their depth of knowledge of all things mechatronics,” Willard says. “The completion of Introduction to Mechatronics and Mechatronics for Equipment Maintenance together allows individuals to better align to our hiring bar and meet our requirements.” Central New Mexico Community College | CNM Ingenuity |

I work in a team in Amazon which manages tax identity collection and lifecycle management of Millions of payees of ~80 businesses belonging to ~75 countries. The team has to deal frequently with the changing tax rules in 75 countries, customization requests from clients, etc. The key thing that I have learnt working in this team is that the engineering team should write as minimum as possible business logic. Instead, engineering team should invest on creating foundational services which enable treating business logic as configuration. This helps to achieve business goals in reduced time and less operational burden.

https://lnkd.in/eq9mEf6R #265 Amazon Mechanical Turk Amazon Mechanical Turk, often referred to as MTurk, is an online platform operated by Amazon that allows individuals and businesses to access a large and distributed workforce to perform various tasks, typically referred to as Human Intelligence Tasks (HITs). These tasks are usually small and straightforward and can include data entry, image recognition, content moderation, survey participation, and more. Here's how Amazon Mechanical Turk works: Requesters: These are the individuals or organizations who have tasks that they want to be completed. Requesters create HITs, set the price they are willing to pay for each task, and specify the qualifications and requirements for the workers who can perform these tasks. Workers (Turkers): Workers are individuals who sign up on the platform to complete tasks in exchange for payment. They can browse available HITs and choose the ones that match their skills and interests. Workers are typically paid for each task they complete, with the payment determined by the requester. HITs: Human Intelligence Tasks are the jobs or tasks that requesters create and post on the platform. These tasks can be simple or complex, and they vary widely in terms of difficulty and time required. Approval and Rejection: Requesters review and approve the work submitted by workers. If they find the work satisfactory, they approve it, and the worker is paid. If not, they can reject the work, and the worker won't be compensated. Payment: Workers accumulate earnings from completing tasks, and requesters are billed by Amazon Mechanical Turk for the work performed by the workers. Requesters can choose to pay workers in cash, Amazon gift cards, or other forms of compensation. Amazon Mechanical Turk is often used for tasks that require human judgment, input, or verification and cannot easily be automated by computer algorithms. It is commonly employed for research, data collection, content moderation, and other tasks that benefit from human intelligence. However, it's important to note that the platform has received criticism for low pay rates and potential exploitation of workers, which has led to discussions about worker rights and fair compensation. www.antharas.co.uk/ companies website or top book distributors! #BusinessStrategy #Entrepreneurship #Leadership #Management #Marketing #Finance #Startups #Innovation #Sales #SmallBusiness #CorporateCulture #Productivity #SelfDevelopment #SuccessStories #PersonalBranding #Networking #Negotiation #BusinessEthics #TimeManagement #GrowthStrategies #MarketAnalysis #BusinessPlanning #FinancialManagement #HumanResources #CustomerExperience #DigitalTransformation #Ecommerce #SocialMediaMarketing

The Amazon EU Design and Construction (Amazon D&C) team is the engineering team designing and constructing Amazon Warehouses across Europe and the MENA region. The design and deployment processes of projects involve many types of Requests for Information (RFIs) about engineering requirements regarding Amazon and project-specific guidelines. These requests range from simple retrieval of baseline design values, to review of value engineering proposals, to analysis of reports and compliance checks. In this post, we not only provide the solution, but also discuss the lessons learned and best practices when implementing the solution in real-world use cases. We compare and contrast how different methodologies and open-source LLMs performed in our use case and discuss how to find the trade-off between model performance and compute resource costs. With the RAG framework and fine-tuned LLMs on SageMaker, we are able to provide human-like responses to users’ questions and prompts, thereby enabling users to efficiently retrieve accurate information from a large volume of highly unstructured and unorganized documents. #Amazon #SageMaker #JumpStart #BestPractices #CustomerSolutions #GenerativeAI

The first step in gauging the efficacy of the action plan is assessing how well the problem statement has been understood. Aided by the technical virtues and deep understanding of the warehousing process, our Solution Design Engineering (SDE) Team at 3SC prioritizes customer parameters with their engineering know-how. From assessing requirements through core data to finalizing the design in the paradigm of technical feasibility, cost, and future scalability, our SDE team's prowess focuses on functionality that benefits our clients immensely such as by enhancing efficiency, reducing labor costs, improving inventory management etc. In addition, our proactive communication always forms the perfect channel to loop in any meticulous input our customers have in mind. Contact us now to know how 3SC’s SDE team will elevate your journey ahead. Vikas Bhadana Sourav Acharya Shubham Patil Ankit Tripathi K S SRIRAM #3SC #Solutiondesign #Networkdesign #Customervalue #Supplychain #Logistics #India #Scalable #Process #Engineers #Warehousing #Management

In 2018, Reuters reported that Amazon engineers had, starting in 2014, been developing a machine-learning tool to sift through online résumés and rank possible job candidates from one to five stars—just like Amazon products themselves—based on how promising they seemed, and that Amazon recruiters would focus their efforts accordingly. “They literally wanted it to be an engine where I’m going to give you a hundred résumés, it will spit out the top five, and we’ll hire those,” as one source told reporters. The measure of that star rating? Similarity—using a word representation model—to résumés of previous Amazon hires in the preceding ten years. By 2015, however, Amazon began noticing problems. Most of those previous engineering hires were men. The model, they realized, was assigning a negative score to the word “women’s”—for instance, in describing extracurriculars. They edited the model to remove this bias. They also noticed, however, that it was assigning a negative score to the names of all-women’s colleges. They edited the model to remove this bias. Still, the model found a way to hear the shoes. Engineers noticed that the model was assigning positive scores to seemingly all vocabulary choices—for instance, words like “executed” and “captured”—more prevalent among male résumés than female ones. https://amzn.in/fmyDSQc

I just read an article about smart Amazon company thinking. They call it "Working Backwards" process. The main components of this unique way of thinking are: a) Work backwards from there to determine what solutions could meet those needs. b) Identify if and how the solutions can be achieved based on Amazon's capabilities. c) Finally, a written narrative is created to pitch the idea to leadership for approval. To my mind, there are very useful pieces of advice inside this article. To develop a successful product, you need to know your client. Solving real problems for real people requires starting with an understanding of their needs. By working backwards, feasibility can be tested early on, aligning with the vision and implementation. Clearly defined goals and approaches result when a narrative is produced. Even those with fewer resources and the scale of Amazon could apply elements of Working Backwards for success. Successful new product launches require a deep understanding of customers, a clear vision, and effective communication skills. While meaningful and differentiated solutions require time and diligence, this process has the potential to revolutionize an organization's ability to bring them to market. For professionals and leaders alike, these principles offer valuable insights into successful innovation within organizations. While adapting to specific contexts is necessary, focusing first on customer needs, working backwards, and clearly articulating plans are timeless insights for fostering transformative growth. Check this article: https://lnkd.in/e4AvP7N8

When an organization's structure is no longer optimized for technical delivery due to fundamental technology changes, this opens up more opportunities to introduce accidental complexity leading to production issues. I think Amazon's Working Backwards principle should always be applied to organizations with a heavy focus in software development. If your key product is the software, everything else needs to be designed and built around it. But let's be real, this approach creates significant challenges to budgeting, resource allocation modeling and forecasting for enterprises. Accountability models need to be updated to the latest operating model from the core of the technologies utilized by your applications. Where do we start? To me, the answer is in application design. We first need to get the application design right, by the standards of high cohesion and loose coupling. Then, ideally we work outwardly and iteratively to create the support organizational layers. We need to follow the inverse of Conway's Law. The center of the onion needs to be the software. #operatingmodel #softwaredesign #softwaredevelopment #technicaldebt #organizationaldebt #BuildWithDC