Staff software engineer for front-end, React Native, and cross-platform product systems
View selected workContactStaff Mobile Engineer · Austin, TX · Apr 2025 – May 2026
Built core scheduling while leading platform modernization.
Built multi-step create, edit, cancel, and delete user journeys that coordinated scheduling data and guided mobile users to completion.
Senior Software Engineer · Remote · Oct 2022 – Feb 2024
Led fintech delivery across React Native payments, native wallet architecture, and app-store constraints.
Evaluated design systems, cost, and legacy architecture to propose pragmatic technical tradeoffs.
Presented Apollo and GraphQL auto-mocking at a React Meetup and trained front-end engineers in React, GraphQL, and TypeScript.
Lighthouse was specified as a release requirement, not treated as a late optimization pass.
Open to Staff or Principal frontend and React Native roles, plus selected senior contract work.
Eight roles show the range. Eight deep records show the method.
Career Register
Eight roles trace a progression from full-stack field systems to staff-level mobile platform ownership.
Staff Mobile Engineer · Austin, TX · Apr 2025 – May 2026
Led mobile-platform modernization across reliability, performance, and delivery confidence.
View case studySenior Software Engineer · Remote · Oct 2022 – Feb 2024
Led fintech delivery across React Native payments, native wallet architecture, and app-store constraints.
View case studySoftware Architect · Remote · Feb 2021 – June 2022
Combined Document Viewer modernization with regression systems, architecture reviews, and cross-team API contracts.
View case studySenior Full Stack Engineer · Austin, TX · Aug 2019 – Aug 2020
Re-platformed product search while evolving GraphQL APIs, testing systems, and front-end engineering practice.
View case studySenior Full Stack Engineer · Austin, TX · May 2018 – July 2019
Led front-end development of the In The Weeds iOS and Android app with React Native, Expo, GraphQL, and Styled Components.
View case studyFull Stack Software Engineer · Austin, TX · Oct 2015 – May 2018
Owned consumer e-commerce delivery across server-rendered React, GraphQL migration, experimentation, production support, and team growth.
View case studyFull Stack Software Engineer · Austin, TX · Oct 2014 – Oct 2015
Architected a real-time chat platform across the agent application, reusable client plugin, services, CRM integration, and test coverage.
View case studyLead Frontend / Full Stack Developer · Austin, TX · Aug 2007 – Oct 2014
Built field-update, real-time analytics, and web reporting systems; led integrations spanning Google APIs, web services, secure authentication, and payment gateways; and introduced Scrum and Kanban practices.
View case studyStaff Mobile Engineer · Austin, TX · Apr 2025 – May 2026
Scope
Led mobile-platform modernization across reliability, performance, and delivery confidence.
Technologies
TypeScript · React Native · Expo · React Query · MobX · Zod · Maestro
Read the Time To Pet case studySenior Software Engineer · Remote · Oct 2022 – Feb 2024
Scope
Led fintech delivery across React Native payments, native wallet architecture, and app-store constraints.
Directed the implementation of Plaid ACH bank transfers in React Native with cross-functional teams.
Architected a native mobile wallet integration with Expo native modules, SwiftUI, and Kotlin partner APIs while maintaining app-store compliance.
Led cross-functional payment architecture from Plaid ACH in React Native to native wallet partner APIs.
Evaluated design systems, cost, and legacy architecture to propose pragmatic technical tradeoffs.
Researched design systems and proposed technical improvements around architectural tradeoffs.
Software Architect · Remote · Feb 2021 – June 2022
Scope
Combined Document Viewer modernization with regression systems, architecture reviews, and cross-team API contracts.
Modernized legacy Document Viewer patterns with React hooks, context, TypeScript, and Storybook.
Led regression testing across front-end applications with Cypress and coordinated manual testing.
Contributed to architecture reviews covering component reuse, state management, and GraphQL schema changes.
Developed API contracts, testing plans, and architectural diagrams with back-end architects.
Senior Full Stack Engineer · Austin, TX · Aug 2019 – Aug 2020
Scope
Re-platformed product search while evolving GraphQL APIs, testing systems, and front-end engineering practice.
Re-platformed product search from Java JSPs to React and GraphQL.
Contributed GraphQL schemas and API unit tests to a Node.js service.
Led an internal application for maintaining product-search data with React Testing Library and GraphQL auto-mocking.
Presented Apollo and GraphQL auto-mocking at a React Meetup and trained front-end engineers in React, GraphQL, and TypeScript.
Senior Full Stack Engineer · Austin, TX · May 2018 – July 2019
Scope
Led front-end development of the In The Weeds iOS and Android app with React Native, Expo, GraphQL, and Styled Components.
Integrated native functionality through Objective-C and Android JVM code while working with designers and stakeholders.
Mentored and onboarded two remote engineers in React Native and GraphQL after the MVP launch.
Contributed to the Node.js, MongoDB, and GraphQL back-end architecture.
Contributed to product roadmapping and planning with stakeholders.
Technologies
React.js · GraphQL · React Native · Expo · Node.js · MongoDB
Read the Seasoned case studyFull Stack Software Engineer · Austin, TX · Oct 2015 – May 2018
Scope
Owned consumer e-commerce delivery across server-rendered React, GraphQL migration, experimentation, production support, and team growth.
Built server-rendered React e-commerce sites with progressive-web-app architecture.
Migrated a React and Redux administration application to GraphQL and Apollo.
Implemented A/B tests, conversion funnels, feature toggles, and email integrations for abandoned-cart and product-retargeting campaigns.
Handled production support, influenced roadmap decisions, and recruited, onboarded, and mentored engineers.
Technologies
React · Redux · Apollo · GraphQL · Node.js · PostgreSQL · AWS · Redis · Docker
Read the Twyla case studyFull Stack Software Engineer · Austin, TX · Oct 2014 – Oct 2015
Scope
Architected a real-time chat platform across the agent application, reusable client plugin, services, CRM integration, and test coverage.
Architected a real-time Ampersand.js and Socket.io application for chat management and analytics.
Built and maintained Node.js microservices for the live-chat system.
Built a reusable website chat plugin and integrated Salesforce data into real-time communication tools.
Maintained Java services, added Mocha integration tests, and performed code reviews.
Technologies
Node.js · Java · PostgreSQL · Redis · Socket.io · Ampersand.js · Browserify · Webpack
Read the Help.com case studyLead Frontend / Full Stack Developer · Austin, TX · Aug 2007 – Oct 2014
Scope
Built field-update, real-time analytics, and web reporting systems; led integrations spanning Google APIs, web services, secure authentication, and payment gateways; and introduced Scrum and Kanban practices.
Built a jQuery Mobile field-update application, an AngularJS real-time analytics dashboard, and a web reporting system with payment gateways.
Led integrations spanning Google APIs, web services, secure authentication, and payment gateways.
Introduced Scrum and Kanban practices and adopted Target Process for project management.
Technologies
PHP · D3 / Pick DBMS · SQL · MongoDB · jQuery · Angular.js · Socket.io · Node.js
Read the Corrections Software case studyBuilt core scheduling while leading platform modernization.
Platform ownership
Primary owner of the React Native/Expo mobile platform.
Workflow depth
Built the Schedule Event workflow end to end.
Native reliability
Led Expo and React Native modernization across GPS, camera, permissions, and crash fixes.
Quality systems
Raised the quality floor through TypeScript cleanup, changed-file lint CI, Storybook, Maestro automation, and mentoring.
Public-safe reconstruction
The evidence narratives exclude employer code, private or internal screenshots, unsupported metrics, and internal identifiers; reviewed historical media is context only.
Led fintech delivery across React Native payments, native wallet architecture, and app-store constraints.
Plaid ACH delivery
Directed the implementation of Plaid ACH bank transfers in React Native with cross-functional teams.
Native wallet architecture
Architected a native mobile wallet integration with Expo native modules, SwiftUI, and Kotlin partner APIs while maintaining app-store compliance.
Cross-functional architecture
Led cross-functional payment architecture from Plaid ACH in React Native to native wallet partner APIs.
Tradeoff discipline
Evaluated design systems, cost, and legacy architecture to propose pragmatic technical tradeoffs.
Public-safe reconstruction
The evidence narratives exclude employer code, private or internal screenshots, unsupported metrics, and internal identifiers; reviewed historical media is context only.
Delivered the In The Weeds mobile product across cross-platform, native, service, roadmap, and team boundaries.
Cross-platform delivery
Led front-end development of the In The Weeds iOS and Android app with React Native, Expo, GraphQL, and Styled Components.
Native boundaries
Integrated native functionality through Objective-C and Android JVM code while working with designers and stakeholders.
Service integration
Contributed to the Node.js, MongoDB, and GraphQL back-end architecture.
Product roadmapping
Contributed to product roadmapping and planning with stakeholders.
Remote team development
Mentored and onboarded two remote engineers in React Native and GraphQL after the MVP launch.
Public-safe reconstruction
The evidence narratives exclude employer code, private or internal screenshots, unsupported metrics, and internal identifiers; reviewed historical media is context only.
Re-platformed product search while evolving GraphQL APIs, testing systems, and front-end engineering practice.
Search re-platform
Re-platformed product search from Java JSPs to React and GraphQL.
Schema and API tests
Contributed GraphQL schemas and API unit tests to a Node.js service.
Data and test tooling
Led an internal application for maintaining product-search data with React Testing Library and GraphQL auto-mocking.
Technical teaching
Presented Apollo and GraphQL auto-mocking at a React Meetup and trained front-end engineers in React, GraphQL, and TypeScript.
Public-safe reconstruction
Public Apollo artifacts verify authored presentation work, not H-E-B product code, adoption, or internal business outcomes.
Combined Document Viewer modernization with regression systems, architecture reviews, and cross-team API contracts.
Document Viewer modernization
Modernized legacy Document Viewer patterns with React hooks, context, TypeScript, and Storybook.
Regression discipline
Led regression testing across front-end applications with Cypress and coordinated manual testing.
Collaborative architecture review
Contributed to architecture reviews covering component reuse, state management, and GraphQL schema changes.
API boundary collaboration
Developed API contracts, testing plans, and architectural diagrams with back-end architects.
Public-safe reconstruction
The evidence narratives exclude employer code, private or internal screenshots, unsupported metrics, and internal identifiers; reviewed historical media is context only.
Owned consumer e-commerce delivery across server-rendered React, GraphQL migration, experimentation, production support, and team growth.
Server-rendered storefronts
Built server-rendered React e-commerce sites with progressive-web-app architecture.
Administration data migration
Migrated a React and Redux administration application to GraphQL and Apollo.
Experimentation and lifecycle
Implemented A/B tests, conversion funnels, feature toggles, and email integrations for abandoned-cart and product-retargeting campaigns.
Production and team support
Handled production support, influenced roadmap decisions, and recruited, onboarded, and mentored engineers.
Public-safe reconstruction
The evidence narratives exclude employer code, private or internal screenshots, unsupported metrics, and internal identifiers; reviewed historical media is context only.
Archive / context only
Archived company material shown for historical context only—not evidence of authorship, ownership, or impact.
Archived Twyla storefront, captured during the reviewed tenure.
Archived Twyla company identity.
Architected a real-time chat platform across the agent application, reusable client plugin, services, CRM integration, and test coverage.
Agent application
Architected a real-time Ampersand.js and Socket.io application for chat management and analytics.
Live-chat services
Built and maintained Node.js microservices for the live-chat system.
Client and CRM boundary
Built a reusable website chat plugin and integrated Salesforce data into real-time communication tools.
Testing and review
Maintained Java services, added Mocha integration tests, and performed code reviews.
Public-safe reconstruction
The evidence narratives exclude employer code, private or internal screenshots, unsupported metrics, and internal identifiers; reviewed historical media is context only.
Built field-update, real-time analytics, and web reporting systems; led integrations spanning Google APIs, web services, secure authentication, and payment gateways; and introduced Scrum and Kanban practices.
Application surfaces
Built a jQuery Mobile field-update application, an AngularJS real-time analytics dashboard, and a web reporting system with payment gateways.
Integration boundaries
Led integrations spanning Google APIs, web services, secure authentication, and payment gateways.
Delivery practices
Introduced Scrum and Kanban practices and adopted Target Process for project management.
Public-safe reconstruction
The evidence narratives exclude employer code, private or internal screenshots, unsupported metrics, and internal identifiers; reviewed historical media is context only.
Employer-linked and personal work stay explicitly separate.
Reviewed public repository evidence
Authored a public H-E-B-era React Apollo deck covering hooks, testing-library, MockedProvider, and GraphQL automocking.
Provenance
Public original repository whose authored deck names Randall Jones, H-E-B Digital, and the reviewed talk topics.
Demonstrated Apollo query hooks, schema automocking, and interaction testing in a public technical example.
Provenance
Public original repository with login-linked authored commits and a separately verified H-E-B presentation pairing.
Contributed a bounded Ampersand filter-control behavior change and version update to a Help.com repository.
Provenance
Public upstream pull request authored by the authenticated account with two pinned contribution commits.
Reviewed public repository evidence
Built a public personal MEAN-stack point-of-sale and inventory prototype with authentication, customer orders, and filtering.
Provenance
Public original repository with login-linked authored commits, published only as a personal time-adjacent artifact.
Lighthouse was specified as a release requirement, not treated as a late optimization pass.
The release gate requires mobile scores of at least 90 for performance, 100 for accessibility, 95 for best practices, and 95 for production SEO, with LCP at or below 2.5 seconds, CLS at or below 0.05, and TBT at or below 200 milliseconds.
Lighthouse runs automatically against the completed production build, while browser tests separately cover the interactive scene, reduced motion, no-JavaScript use, and WebGL failure.
MOBILE / LIGHTHOUSE 12.6.1
The RC01 homepage recorded three consecutive mobile Lighthouse 12.6.1 runs with scores of 100 for performance, accessibility, best practices, and SEO.
Across those runs, LCP ranged from 1.05 to 1.20 seconds, CLS remained at or below 0.00012, and TBT was 0 milliseconds in all three runs.
METHOD / PROOF ARCHITECTURE
A public-safe guide to how reviewed sources become bounded public proof.
Considered during authoring.
Review support, privacy, confidence, and publish status.
Bounded wording under a stable identifier.
Add context without raising confidence.
Route and find the rendered public record.
This static Astro portfolio uses typed claim models, deterministic evidence snapshots, and a fail-closed public-build gate.
Every public claim in this portfolio maps to approved evidence.
The personal wiki stays read-only; the deployed site never reads it.
Browser checks cover no-JavaScript use, mobile geometry, keyboard behavior, accessibility, and visual states.
One isolated WebGL surface keeps the expressive layer separate from the semantic document.
This method describes how this portfolio reviews and presents claims. It does not establish employer outcomes, business impact, adoption, performance, or ownership.
