The Journey
Every role taught me something. Here’s how it all connects.
2017—Where It Started
Customer Service Associate | AT&T | Chicago, IL
This is where I learned what customer service actually means. Not the script — the instinct. I maintained a 92% customer satisfaction rate against an 83% goal, handled billing disputes, and started training new hires before I even had a title for it. I didn’t know it then, but I was already building.
2019 — Learning a Different Kind of Operation
Air Export Agent | Expeditors | Bensenville, IL
A detour that turned into a lesson. Managing international shipments end-to-end taught me that operations without communication breaks down fast. I learned compliance, documentation, urgency — and that every system, no matter the industry, has a gap somewhere.
2020 — High Volume, High Stakes
Customer Service Representative (Live Chat) | Verizon | Rolling Meadows, IL
Verizon was where I leveled up under pressure. Managing up to 7 concurrent escalated live chats simultaneously taught me composure, precision, and how to deliver quality when everything is moving at once.
Before my role ended I was tapped to contribute insights for the company’s new AI-enabled chat system — bringing the thing I knew best to the table: what language, tone, and mindset actually works when a customer is frustrated and trust is on the line. That experience sharpened something I already had — an instinct for spotting where systems are failing customers before anyone else notices.
2023 — Amazon. The Real Turning Point.
Customer Escalation Specialist | Amazon Shipping | Chicago, IL
I joined Amazon Shipping during its launch — surrounded by logistics professionals who had never worked a front line a day in their lives. I brought 8 years of customer instinct into a room that needed it badly. In 11 months I resolved 1,500+ complex escalations with a 1.2-day average time-to-resolve against a 3-day goal. I authored talk tracks, trained 5 new reps, built the offshore training materials, and identified 20 process improvements — every single one approved by leadership.
I wasn’t just resolving cases. I was building the infrastructure behind the team.
2024 — Builder Mode
SDR Team Lead | Amazon Shipping | Chicago, IL
This is where I became undeniable. I built the SDR Playbook from scratch — a living document that mapped the entire customer journey and taught reps how to translate a prospect’s needs into a qualified shipper. Inbound lead conversion went from 24% to 75% under my leadership. I designed Salesforce dashboards, led daily metric analysis, drove cross-functional alignment across Sales, Product, and Marketing, and built an onboarding program that got new hires running solo calls within one week.
When this chapter closed, I didn’t leave with just experience. I left knowing exactly who I am.
Now — The Pink Room
I am a builder. A gap finder. An operator who leads with empathy and backs it up with data.
I’ve spent 8 years learning what makes customer experiences work — and the last few years turning that knowledge into systems, playbooks, and frameworks that outlive the roles I held.
Now, I am awaiting my next team to join.. but in the meantime sharpening my skills and also building contributions of my own.
Job Placement Digest
I systematize complex work at scale. When a process is breaking under volume — escalations piling up, onboarding falling apart, teams working off different playbooks — I find the root cause and build the fix that sticks, not the patch that buys time.
At AT&T, I held CSAT at 92% against an 83% goal and started training new hires before I even had a title for it. At Verizon, I contributed to the design of an AI-enabled chat system that let the team absorb more volume without adding headcount. At Amazon, I built standardized triage blurbs that stabilized team resolution time at 1.5 days, then sustained a 1.2-day average across 1,500+ escalations over 11 months. As an SDR Team Lead there, I took inbound lead conversion from 24% to 75% by building a playbook that got new hires working solo within a week.
I’m targeting support/ops leadership roles, and I’m equally open to AI operations roles — places where I’d design the process first and grow into the automation layer as the team scales. I’ve spent the last several months building AI fluency deliberately (11:11 AI Leaders program, Generative AI micro-credential), not because I’m chasing a trend, but because process design and AI implementation are the same skill applied at different altitudes
If you’re solving a chaos-to-system problem, I want to talk — because I’ve done it three times over, and I know how to move fast once direction clears.