Production communication workflows supporting critical Walmart Business order-lifecycle notifications across SMS, push, and email.
SmartComms supported more than 100 communication flows across Walmart Business, and I contributed to approximately 98% of the existing flows.
Became the SmartComms SME and primary point of contact within approximately six months.
Received two internal Walmart recognitions for contributions to SmartComms.
Supported communication workflows spanning SMS, push, and email.
Walmart Business customers depend on timely communication throughout the order lifecycle—from order placement through pickup, delivery, cancellation, and changes.
SmartComms supported these workflows through event-driven communication pipelines. Changes had to preserve message correctness across multiple downstream communication channels while remaining reliable in production.
As I gained experience with the system, I became the SmartComms SME and primary point of contact for development requests, production issues, troubleshooting, and knowledge transfer.
An order-lifecycle event occurs, such as order placed, ready for pickup, delivered, cancelled, or changed.
Backend services process the event and prepare the communication data required for the customer notification.
Event schemas and payloads move through Kafka-based event-driven workflows.
Payloads are transformed into the structure required by the downstream communication platform and templates.
The resulting communication is delivered through the appropriate customer channel such as SMS, push, or email.
Became the SmartComms SME and primary point of contact within approximately six months.
Contributed to approximately 98% of the existing SmartComms communication flows, working across event schemas, payload transformations, backend changes, debugging, and production support.
Worked on Kafka event schemas and payload-transformation pipelines supporting customer notifications.
Supported communication scenarios including order placed, ready for pickup, delivered, cancellations, and order changes.
Investigated production issues during recurring on-call rotations.
Used application logs and MySQL diagnostic queries to inspect production state and isolate backend defects.
Wrote shell scripts for database connectivity and CRUD validation during troubleshooting.
Mentored a junior engineer through application architecture, development/deployment flows, troubleshooting, logs, documentation, and production-support practices.
Created and maintained technical documentation to reduce dependency on tribal knowledge.
Worked with Kafka event schemas and payload transformations to keep communication behavior consistent across multiple order-lifecycle scenarios and downstream channels.
Combined application logs with targeted MySQL queries to validate persisted state and distinguish data issues from service or workflow defects during incidents.
Turned recurring troubleshooting knowledge into documentation and mentoring so other engineers could independently understand requests, deployments, logs, and production issues.
SmartComms supported 100+ communication flows across the broader Walmart Business communication ecosystem. The examples below illustrate only a small subset of those workflows.
Customer confirmation after successful order creation.
Notification when an order becomes available for pickup.
Customer communication after successful delivery.
Notifications reflecting cancellation or material changes to an existing order.
These are representative examples only; the platform supported many additional communication scenarios across the customer order lifecycle.
I worked within Walmart's existing communication ecosystem; I did not build the overall enterprise messaging platform from scratch.
Communication delivery and surrounding downstream systems involved additional teams and shared infrastructure.
I worked with Kafka-based event flows at the application/schema/payload level; I did not administer the underlying Kafka infrastructure.
Product and partner teams supplied communication requirements; I translated those requirements into backend workflow changes and production support.
My core ownership: SmartComms SME responsibilities, event-schema and payload-transformation work, production troubleshooting, MySQL state inspection, on-call support, documentation, and mentoring.