Understand the whole system. Not just part of it.
Hi, my name is Jared Sanders, a Software Engineer who currently oversees the design and implementation of internal data software and delivery. Here, I design complete systems - the data model, the services, and the interface - for our Product Info Management system, as well as the pipeline that delivers this data to and from the websites.
Specializing in event-driven microservices, it's my responsibility to not only offer a rich frontend experience for our customers, but also design and architect the backend in a way that is fast, safe, reliable, and cost effective, following the AWS pillars.
While navigating merchandising and vendor relations, building a detailed understanding of the automotive industry, I took an interest in software development. Now, after years of self-development and growth, I can take pride in the accomplishments I've achieved, and build top-tier software that my colleagues benefit from everyday.
I currently work for Realtruck, but I'm always open to collaborate on open-source and side projects with people who care about the details.
Systems that scale from zero to hero.
I design and build event-driven serverless apps on AWS - Lambda, API Gateway, SQS/SNS, EventBridge - that run themselves and scale on their own.
Scales to zero
Idle costs nothing; a traffic spike just scales - no capacity planning, no warm pools to babysit.
Nothing to patch
No servers, no OS updates, no 3am pages. AWS runs the groundwork; I own the logic.
Resilient by default
Queues, retries, and dead-letter handling mean most failures recover on their own.
Notable Achievements
A few of the systems I've designed and built - the kind of work that's invisible when it's done right.
Built the data platform behind every product page
Designed a product information platform that models, stores, and serves a catalog of 1.2M+ products and 15M+ attribute values - the single source of truth feeding every customer-facing storefront.
Engineered the pipeline that feeds every storefront
Built a data-processing pipeline that validates, transforms, and delivers product records to 4 first-party storefronts and major marketplaces like Amazon and eBay - publishing thousands of products in a single asynchronous run, with no timeouts.
Made a distributed system fault-tolerant
Re-architected an event-driven publishing system for resilience - retries, dead-letter recovery, and real-time monitoring - eliminating a class of silent failures, including one quietly breaking 99% of a critical hourly sync.
Made a 21M-row fitment model editable
Designed how the platform knows which parts fit which vehicles - 21M+ fitment records. Editors manage it in compact year ranges, while it's stored denormalized for instant lookups - with validation and deduplication keeping every row accurate and conflict-free.
Engineered full change-tracking across the catalog
Built a versioning and audit system capturing every change at the field, attribute, and relationship level - with full attribution across every catalog entity (product lines, products, brands, and categories) - so the team sees exactly what changed, by whom, and what's live vs. pending.
Led a full rebuild of the team's daily tool
Architected and led the migration of an entire internal application to a modern Vue/Nuxt stack - rebuilding every workflow the catalog team uses daily, with schema-validated forms and full accessibility, and zero feature regressions.
An unusual path - and an edge.
I didn't start in engineering. I came up through merchandising - spreadsheets, product data, and vendor relationships - and that's exactly why I design systems that understand the data and the business they serve.
- Design and build complete systems - from the data model up through the services to the interface.
- Deep work in data modeling and normalization, keeping a large product catalog correct and queryable at scale.
- Work across the stack and the cloud, owning features end to end.
- Led technical projects end to end - scoping, planning, and shipping alongside engineering.
- Owned Jira administration and stakeholder engagement, turning business needs into clear requirements.
- The bridge between the business and the build - where I learned how systems actually come together.
- Managed product data and vendor relationships - the catalog data I now model in code.
- Lived in advanced Excel - then started teaching myself to code, automating reports and building small tools within a few years of being hired.
- Where my fluency with data - and the business behind it - began.
I went back and finished my computer science degree while working full-time - layering formal foundations onto years of self-taught practice, right as I moved into development.
Most engineers learn the system. Fewer understand the business behind it. I've sat on both sides of the table - so I ask the right questions early, model data the way the business actually thinks about it, and talk to non-engineers without a translator.