Adam Afify

Project coordination and operations. Computer Science student, graduating July 2027.

Houston, TexasAvailable for internships now
Southern New Hampshire UniversityB.S. Computer Science, July 2027
Target, since June 2024Merchandising, receiving, logistics
See my work

About

I keep work organized and moving. At Target I've trained new teammates, presented floor strategy to store leadership, and worked with vendors to fix shipping problems.

My degree classes in Systems Analysis and Design and the Software Development Lifecycle gave me a way to describe how projects get planned and delivered. Store work showed me what that looks like on a real floor, with real deadlines and people who depend on each other.

Looking for: internships now, and early-career roles after I graduate in July 2027, in project coordination, operations, logistics, or associate project management.

Experience at Target

  1. June 2024 to present

    General Merchandise Expert

    • Train and onboard new team members on inventory tools, store protocols, and guest service standards.
    • Coordinate daily inventory replenishment and adjust merchandise layouts to keep the sales floor clear and organized.
    • Help guests with product questions and recommendations.
  2. June to August 2026

    Receiver and Logistics Expert

    • Managed backroom logistics and receiving, checking accuracy across high-volume inbound and outbound freight.
    • Worked with store leadership and vendor representatives to resolve shipping and delivery issues.
    • Used handheld inventory systems to track stock, organize storage, and prevent discrepancies.

    When a process changed. Target added a salvage process. Before, damaged items were scanned into one barcode that counted against the store's performance numbers. After the change, team members had to scan salvage items a different way. I made sure the team scanned them correctly so items were tracked properly and didn't hurt the store's numbers by mistake. A change isn't finished when it's announced. It's finished when everyone is following it.

  3. October 2025 to June 2026

    Style Consultant and Merchandising Specialist

    • Prepared and delivered floor strategy updates and visual merchandising presentations to store leadership during team huddles.
    • Kept visual merchandising standards across high-traffic departments so the store looked right and guests could find what they needed.

How a store reset runs like a project

When a store changes an aisle, the presentation team resets it to a new plan. Product has to arrive on time, the work has to fit a window, and several people have to finish their parts in the right order. I've worked on both sides of it: on the floor where sets go in, and in the backroom where product flows.

  1. 1

    Scope

    Read the set instructions and planogram that say what goes where.

  2. 2

    Prep

    Line up people, tools, signage, and product before the window opens.

  3. 3

    Execute

    Clear the old layout, move fixtures and product, and work to the schedule.

  4. 4

    Check

    Walk the aisle against the plan and fix any gaps.

  5. 5

    Handoff

    Give the floor team a ready aisle and tell leadership what's left.

What this teaches: managing dependencies between teams, checking finished work against a plan, reporting to stakeholders, and training people into a process.

Design case study

Concept project

Daybreak, a coffee ordering app

A busy regular should be able to reorder their usual drink in a few taps. I started from a first draft made by Figma's AI, kept it as the original, and built my own version next to it so I could compare the two.

Made with Figma and Figma AI. First version finished; not yet tested with users.

The starting point: Figma AI draft

  1. AI draft home screen: greeting, usual oat latte with a Reorder now button
    Home
  2. AI draft customize screen: size, milk and extras
    Customize drink
  3. AI draft pickup screen: café and pickup time options
    Pickup time
  4. AI draft payment screen with saved card and price breakdown
    Payment
  5. AI draft order confirmation with pickup time and progress
    Order confirmation

My version: Daybreak

  1. Daybreak home screen: greeting, usual oat latte with Reorder button, new drink banner and a recommendation
    Home
  2. Daybreak customize screen: size, milk and extras
    Customize drink
  3. Daybreak pickup screen: map of the café and pickup time options
    Pickup time
  4. Daybreak payment screen with saved card and price breakdown
    Payment
  5. Daybreak order confirmation with pickup time and progress
    Order confirmation

Tap a screen to see it full size.

What I changed from the AI draft

  • Rebranded the draft's "Juniper" as Daybreak, with a new name and a brown and tan palette.
  • Gave it more personality with a bold, playful headline font in place of a plain serif.
  • Rewrote the copy in a friendlier voice: "Make it yours," "Coffee on your time," "We're on it, Adam."
  • Added a map and walk time to the pickup screen.
  • Added a new-drink banner and a recommendation to the home screen.

What I'd improve next

  • Make Reorder the one main button on Home. The recommendation's Order button competes with it.
  • Simplify Home by cutting the new-drink banner, so the usual order stands out.
  • Make the small text bigger and easier to read.
  • Have two or three people try to order their usual coffee, and note where they get stuck.

How I used AI. The first draft is Figma AI's work, and I label it that way. I used it as a starting point, made the brand, type, copy, and layout choices in my own version, and compared the two to see what still needed work.

Coding project

Course project

Corner Grocer item tracker, in C++

A command-line program for a grocery store. It reads a list of purchases from a file and shows how often each item was bought. I built it for my CS 210 class.

Written in C++. Built with help from an AI assistant; I reviewed the code and can explain how it works.

What it does

  • Reads the purchase file and counts each item using a C++ map.
  • Saves the counts to a backup file, frequency.dat, as soon as the program starts.
  • Offers a menu: look up one item, list every count, or show a histogram.
  • Treats "garlic" and "Garlic" as the same item.
  • Checks the menu input, so a wrong entry doesn't crash the program.

What I practiced

  • Reading and writing files.
  • Counting and summarizing records, the same idea behind SQL queries.
  • Splitting a program into a class, a header file, and a main file.
  • Handling bad input.

Sample output: histogram option, using the class's sample file

Broccoli        *
Garlic          ***
Papayas         *
Peaches         **
Radishes        *
Spinach         ***
Watermelon      *

Data project

Personal project

Online retail sales analysis, in SQL

I analyzed about 540,000 real purchase records from a UK online store. I used a free public dataset and SQLite, and I wrote queries to find the top products, top customers, and revenue by country.

Written in SQL (SQLite). Built with help from an AI assistant; I ran every query myself and checked the results against the raw rows.

What I found

  • My first results looked wrong. I checked the raw rows and found one order of 80,995 units that was cancelled 12 minutes later. I rewrote my queries to count returns, so cancelled orders cancel out.
  • Counting returns cut UK revenue from £9.0M to £8.19M.
  • The UK is by far the biggest market. The next country, the Netherlands, brought in about £285 thousand.
  • The top product by net units was World War 2 Gliders (53,847 units).
  • The top customer spent about £279 thousand.

What I practiced

  • Loading a large CSV file into a database.
  • Grouping and summing data with GROUP BY and SUM.
  • Sorting and limiting results to get a top 10.
  • Checking that a result makes sense before trusting it.

Example query: top products, with returns counted

SELECT Description, SUM(Quantity) AS net_sold
FROM sales
GROUP BY Description
ORDER BY net_sold DESC
LIMIT 10;

Coordination

  • Cross-functional communication
  • Process and workflow improvement
  • Training and onboarding
  • Inventory and receiving
  • Presenting to leadership
  • Customer service

Technical foundations

  • Systems analysis and design
  • SQL and database basics (coursework and a hands-on project)
  • Software development lifecycle
  • Using AI tools to draft, then checking the result
  • C++ (coursework)
  • Figma (learning)

Education

Southern New Hampshire University

B.S. Computer Science, July 2027

  • Systems Analysis and Design how requirements become a plan
  • Software Development Lifecycle how a project moves from idea to delivery
  • Database Management and SQL organizing and querying data
  • Data Structures and Computer Science Fundamentals