Trade checkout migration
Worked on moving trade-in checkout functionality out of a legacy flow and into the modern checkout platform, including support for customers completing a trade-in without an existing account.
← Back to homepage work
Recent role · Software Engineer
musicMagpie.
Product engineering across checkout and trade-in journeys, combining backend/API work with customer-facing changes and the production responsibility that comes with shipping into a live ecommerce platform.
- When
- Oct 2023 – Jul 2026
- Team
- Checkout
- Focus
- Trade-in · customer validation · express checkout · production support
- Stack
- .NET · C# · APIs · React · TypeScript · Azure · SQL
Context
Engineering a live customer journey.
Checkout sat at the intersection of customer journeys, APIs, session state, payments and multiple supporting services, so even apparently small changes often crossed system boundaries.
I worked within musicMagpie's Checkout team on the customer journeys around buying and trading in technology. The role covered new features, defects, code review, QA, deployment and production investigation, so the work did not end when a pull request was merged.
The strongest examples are the changes that crossed system boundaries: moving legacy trade-in behaviour into the newer checkout codebase, evolving customer validation, and supporting authenticated express-checkout journeys where API behaviour, session state and payments all have to agree.
Selected engineering work
Three examples from Checkout.
Three pieces of work that show the mix of migration, backend services and customer-facing product engineering involved.
Customer validation
Developed and evolved customer-validation behaviour used by checkout and trade journeys, including API-contract and versioning work where compatibility mattered to callers.
Logged-in express checkout
Worked on authenticated express-checkout journeys, dealing with the interaction between customer/session state, checkout behaviour and payment integrations.
Production engineering
Shipping was part of the job.
01
Refinement & delivery
Worked with product owners and engineers to refine backlog items, estimate work and establish acceptance criteria before implementation.
02
Peer review & QA
Reviewed code and carried out QA against acceptance criteria for changes developed across the team.
03
Deployments
Handled Checkout deployments, taking features and fixes through into production rather than treating merge as the finish line.
04
Monitoring & incidents
Monitored Azure alerts and investigated triggered errors to understand production impact and distinguish regressions from wider operational issues.
Capabilities demonstrated
Product engineering that continued into production.
The role strengthened the parts of engineering that are difficult to show with a technology list: changing established customer journeys safely, working across multiple services, preserving API compatibility, collaborating with frontend/product work and staying responsible for what happens after deployment.
.NETC#ASP.NETREST APIsReactTypeScriptAzureSQLPaymentsCI/CD