American Musical Supply (AMS)
Sr. Adobe Commerce Developer / Backend Lead — full-time
Backend leadership on Adobe Commerce Cloud for the musical-instrument retailer — a Salesforce Marketing Cloud migration to Listrak, Synchrony financing beside Affirm, rewards at catalog scale, and AI coding guardrails for the dev team.
- Salesforce → Listrak cutover
- 20–25 SSIS feeds
- ~25K reward SKUs
- Synchrony financing build
- Architected the move from Salesforce Marketing Cloud to Listrak, owning Adobe Commerce APIs for order-confirmation email, SMS notify-me, checkout opt-in, and hourly bearer-token refresh. Ran the production switch that replaced Salesforce form controllers ahead of the contract end.
- Mentored migration of approximately 20–25 SSIS feeds, including SQL-side JSON grouping previously handled by Salesforce.
- Drove the Synchrony financing build beside Affirm: one promo per order, a custom cipher-token settlement path outside the vendor extension, and rewards exclusion on financed orders. Worked with Synchrony on sandbox, promo-override, and daily funding-report constraints; public launch was targeted for mid-to-late January.
- Set repo standards, managed settings to block secret writes and unapproved commands, and prompt-injection hooks for Claude Code and Cursor. Piloted team rollout to keep AI coding tools available while protecting credentials and production configuration.
- Delivered customer rewards with standardized points, SKU-level ratios, item-level calculations, and checkout integration hardening. Scaled catalog rewards from approximately 5,000 to 25,000 SKUs, using a Fastly purge to keep PDP badges consistent.
- Led feed migration planning for approximately 22,000 SKUs with hourly updates across Google, Bing, and Meta — aligning flat-file/API ingestion and delta strategies with margin tiers, price thresholds, and out-of-stock filtering.
- Partnered with marketing on GA4/GTM and OneTrust compliance audits, investigating consent gating gaps and scoping fixes for tag firing, restricted data processing, cross-domain linking, and conversion inflation risks.
- Owned incident-aware release execution, coordinating monitoring and communications and running time-boxed releases with observability markers and checklists.
- Stabilized staging by isolating branch-related deployment failures and enforcing release-branch baselines to reduce environment churn and accelerate QA.