Amazon Relay (Feb 2022 - Feb 2024)
Minneapolis, MN / Tempe, AZ
Software Development Engineer, Full-time
- Contributed to Amazon Relay, the product used by carriers and drivers to manage onboarding, verification, support, driver assignments, and load-related workflows.
- Built across user-facing driver/carrier flows and backend services, with projects spanning mobile changes, backend migrations, metrics, feature flags, and partner-team integrations.
Relay work
Driver Phone Number Validation
Added phone number validation for drivers requesting phone support, where incorrect contact numbers caused support calls to fail.
- Built Android and iOS phone-number input components around Google's phone number validation library.
- Added in-app prompts that asked drivers to update contact information when their saved number failed validation.
- Created a daily Lambda job that checked validation status over time so the team could confirm the rollout was improving phone-number quality.
- Observed verified phone numbers increase from about 15% to about 40% during the first month of the North America rollout.
Mexico Expansion
Added Mexico support to Relay account setup and the backend services that processed country-specific driver information.
- Added Mexico as a selectable country during account creation and wired that selection into the app's localized copy.
- Configured internal translation mappings so Mexico-specific app text resolved through the correct language resources.
- Updated backend country handling so account and verification services recognized Mexico-specific driver records.
Carrier Validation
Implemented Relay carrier-verification flows for account-specific document requirements.
- Built carrier-facing verification screens that listed required documents, missing submissions, and the next steps before account validation.
- Added backend APIs that read carrier requirements from a partner team's source of truth and normalized the data for Relay clients.
- Updated Relay to react to upstream changes in document rules and carrier status.
- Kept carrier verification progress consistent between backend services and the carrier-facing screens.
Data Privacy Identifier Migration
Implemented part of a GDPR/CCPA-motivated identity model that reduced how widely long-lived driver identifiers were stored across Relay services.
- The new model mapped permanent driver identities to expiring temporary IDs so downstream systems could store temporary references while a source-of-truth service controlled deletion and anonymization.
- Updated roughly six backend services to read and write the new identifiers while legacy persistent references were migrated.
- Changed DynamoDB access patterns from a one-to-many shape built around persistent IDs toward lookups that supported the temporary-ID model.
- Used feature flags, migration logic, metrics, and rollback paths because the rollout touched multiple services and partner-team integrations.
- Supported partner teams that called Relay services as they updated their integrations to use the new identifier model.
Multi-Region Driver Assignment Service
Prepared a Relay service responsible for driver assignments to run in a multi-region setup.
- Updated service behavior for regional operation, where assignment creation had to remain reliable if traffic or dependencies moved between regions.
- Validated configuration, deployment behavior, and service assumptions that were previously built around a single-region setup.
- Used metrics and rollout checks to confirm the service continued creating assignments correctly during the migration.
Driver Identity Verification
Integrated Relay's driver identity verification backend with the mobile gateway used by iOS and Android clients.
- Added backend translation support for the verification flow.
- Connected the mobile gateway to new backend APIs so iOS and Android clients could start and complete verification through the Relay app.
DynamoDB API Latency Fix
Fixed a backend API that became slower as more DynamoDB records were associated with a driver.
- Replaced an inefficient DynamoDB read pattern with a targeted get/query lookup for the affected driver records.
- Reduced worst-case request latency from about two seconds to roughly five milliseconds for the affected single-page lookup.
Legacy Carrier Cache Design
Wrote a design document for a legacy carrier cache that struggled as carriers added more drivers.
- Investigated DynamoDB row-limit pressure caused by the existing data shape.
- Proposed data-model options, documented tradeoffs, and presented a path that another developer later used to implement the fix.
Operations and On-Call Support
Supported Relay services in production through on-call work, bug fixes, metrics review, and customer-impact investigations.
- Investigated support escalations and customer complaints by tracing behavior across mobile clients, backend services, logs, and metrics.
- Monitored service health, reviewed alarms and dashboards, and fixed defects found through production metrics or support reports.
- Delivered smaller mobile and backend fixes that improved reliability, correctness, or performance outside of larger project work.