Founder of the Software Engineering Accelerator, a premiere coaching program that helps computer science students, new graduates, and bootcamp graduates land internships and full-time jobs. See amanmanazir.com/coaching.

First hire on the new Support Software Engineering team

The Shop App is a mobile shopping app developed by Shopify that allows users to shop from their favorite brands and stores, track orders, and receive updates on discounts and deals. [Ruby on Rails, GraphQL]I worked on the Shop Cash Buyers team, a division of Shop responsible for developing the Shop Cash Back feature. Shop Cash enables customers to receive a certain percentage back to apply towards future purchases.My contributions included renaming the field Boost Campaign to Offers, removing tech debt that was created months ago. This involved adding a new field, shop_cash_offer, to the shop_type.rb, and rewiring the resolver and calls on the backend of the deprecated field. I also coordinated with the mobile team for the integration of this new field. While working on this field, I encountered an error that occurred after the merge, so I had to coordinated with the on-call team to roll my PR back. Through this experience, I learned the importance of notifying all involved parties before important changes are shipped.Additionally, I implemented a bug fix related to filtering campaigns that are associated with disabled shops in shop-server—this involved filtering campaigns by the shopping_eligible field on the backend to remove disabled shops from our list.

Last summer, I worked on the Catalog Distribution Team at Prime Video Technology in Los Angeles, California [used Java, Git, JUnit, Brazil, AWS].• BACKGROUND: Prime Video Catalog Distribution (PVCD) is a backend team that owns the services related to querying all metadata/offers information related to titles on Prime Video. Basically, PVCD controls the APIs that 3rd-party devices (Samsung, LG, Apple TV, Google) use to get title data, such as descriptions, languages, thumbnail, cover art, etc. • TECH STACK: During my internship, I mainly used Java (as my team was completely backend). I made changes to the codebase, used Git, and pushed to production with Pipelines and Brazil. I also worked with AWS S3 and EMR to test my code by generating a Gamma Integration Feed.• TECHNICAL PROJECT (completed): My project involved adding five new attributes to the Global Metadata/Offers feed along with the Apple feed. • In the past, global partners (such as Samsung, LG, etc.) could not determine in the backend whether titles were Amazon Originals or Amazon Exclusives. Because of this, Prime Video had to manually upload title images that had the ORIGINAL logo burned into it. If Amazon wanted to make updates to the logo, then a full backfill process would need to take place (with every title cover updated and replaced).• I added an API attribute which allows the partners to query a title and find out whether it's an Amazon Original/Exclusive—saving a great deal of Amazon's time/resources, as now there is no need to manually edit the cover images. I also added API attributes for Dolby Atmos, Countries of Origin, and Audio Descriptions.

In the spring, I worked on the Shopify Fulfillment Network (SFN) Inbounding Team, focused on the Rework Project [used Ruby, Ruby on Rails, React, GraphQL, Git].• BACKGROUND: Shopify Fulfillment Network (SFN) is a fulfillment service offered to Shopify merchants—merchants can send their product to a SFN warehouse in North America and Shopify will carry out all logistics related to shipping/handling and order completion.• My team, SFN Inbounding, was responsible for all the software that merchants interact with when sending their supply to the SFN warehouses. We dealt with shipment tracking, transfer creation, etc.• TECH STACK: The framework I used during the majority of my internship was Ruby on Rails, as I mainly worked on the backend of SFN Inbounding. I also used GraphQL for all the API calls, along with a little bit of React when implementing our changes on the frontend.• PROJECT: The Rework initiative is a project centered around creating software to aid the "Rework" of damaged items—during the SFN inbounding process, there are inevitably goods that are either 1) missing information (barcodes, etc.) or 2) have been broken (ie. a hot sauce bottle cracked during shipping). • Our team build software to log damaged items, communicate item status with the merchant, and repair the broken product. The system was created using Ruby on Rails integrated with a React application. We also visited the Ottawa warehouse to educate workers on Rework and run extensive virtual/physical testing.

I worked on the John Deere Expert App/Services backend development team. [used Java, Spring Framework, JUnit, Jenkins, Git]• BACKGROUND: JD Expert Services is a web application based on developing jobs and checklists for JD-certified services technicians to use during repair jobs. The user can create different routines for each kind of repair, along with tools for communication/pricing with the customer.• JD Expert App is a iOS/Android Mobile app used by technicians as they execute repair jobs on JD equipment/machinery. Basically, it contains information on how to complete the repair, and also offers tools for tracking specific notes and communicating with the customer.• My role was on the backend of the expert app/services. Specially, I worked on machine/execution microservice, the areas responsible for managing the API that the program interacts with.• LANGUAGES USED: My primary language used is Java for the backend. Specially, I worked with the Spring Framework to create new features and move from Spring Boot to Native.• TECHNICAL PROJECT #1 (completed): In the past, if technicians using the JD Expert App inputted titles longer than 255 characters in certain fields, an 500-internal server error would be thrown. Because this error is so general, it would always draw the attention of the team due to an AWS alarm.• However, this error should actually be a 400/402 (because it results from an invalid user input) instead of a 500-error. This project was centered around 1) fixing this defect and changing it to the proper 4XX and 2) looking for other defects of this category that result in improper error codes.• I solved this problem by instituting several Spring Boot validation annotations throughout the code to create preliminary checks- if the user inputs something longer than 255, these catch the error and throw a 4XX instead. I also moved past the initial problem and added more annotations to stop future bugs.

I worked on the IT department at Modern Woodmen, a fraternal financial and life insurance company. During my internship, I primarily used C#, but also used SQL and Visual Basic (to work with databases).• TECHNICAL PROJECT: In the past, if an exception in client software occured, it would automatically be logged in an error file deep in a Modern Woodmen database. While the error details were available there, IT would only solve the issue once the client created a support ticket. This meant only problems that the client identified and requested would get resolved.• My project was to find a solution to this problem- to decrease the response time taken to solve issues, and preferably fix bugs without the explicit request of a client. • I solved this problem by creating an MS Teams error card system using Microsoft Azure DevOps Webhooks and Microsoft Teams API. Whenever an error log was created, my code would scrape the file and take all the important details. Then, it formulates the information into an aesthetically-pleasing error card (which is posted in a MS Teams channel).• This allows IT to tackle bugs quickly before the client even realizes something went wrong in the first place, thus drastically decreasing total support tickets.

• Worked under Rita Hart for her democratic campaign for Iowa's 2nd congressional district.• Recruited and trained over 5 new interns to work for Hart in voter engagement.• Phonebanked and canvassed hundreds of people to spread the campaign message and raise support.

• I conducted the research project "Interactive Flood Mapping on Web-Based Systems" under PI Dr. Ibrahim Demir. [used Google Maps API and JavaScript for front-end development]• BACKGROUND: Floods are a major natural disaster in the state of Iowa and cause significant damage to the infrastructure of a city. One factor that directly determines the direction of flood-flow is the elevation gradient throughout the city. If you had a field of elevation data, you could write an algorithm that would predict the flow of water from any discrete point (as water always flows downhill). You could also house this algorithm within a web application that would allow city planners to run flood-simulations to prepare prevention structures such as levees/reservoirs in advance. My project was building this web application, and integrating it with the HAND water-flow algorithm.• METHOD: I used the Google Maps API to create the web application, as it allowed the user to interact with a underlying developed map. Then, I used JavaScript to create a UI over the map with a set of operations that the user could perform. • RESULTS: First, the user can generate an elevation image of an area that they have specified- then, they can draw polygonal structures to simulate flood-defenses (using the Google Maps API). The application also houses the necessary elevation data required to run the HAND algorithm. In the future, this web-application will be connected to the algorithm to fully run flood simulations.(for more information, see the attached research poster)