Jon Wang Email & Phone Number

Beijing, China

I formulate and execute product strategy for our golf data analytics app, 洞见18, for the Chinese market. With my domain knowledge, I identify key customer pain points to tailor our stat engine development to. Using my experience with tracking golf stats, I also work with the UX team to optimize user flow, stat display, and smart UI for data entry.I develop Java backend code to power our data analytics engine and databases. As an architect, I drive componentized suites of services, integrated using APIs, that can be implemented/deployed independently and by different development teams. I implemented microservice design to accelerate our development speed, allow for greater agility, and support scalability changes or updates in the future. Most notably, I have:• Developed a new strokes gained algorithm that further divides “Strokes Gained: Off the Tee” into a component of distance and accuracy. This helps players identify more specific weaknesses.• Developed a new algorithm that converts traditional metrics, like “Greens in Regulation” and “Fairways Hit”, to a strokes gained value to provide better explanations of these statistics.

San Mateo, California, United States

Responsible for building a functional testing framework on top of our low-code data pipelines DSL.

Responsible for rearchitecting legacy GPS/GNSS testing and user interface suite for a modern tech stack with a focus on scalability & performance as well as maintainability & extensibility. Reduced codebase size by 40%, improved feature turnaround time by 30%, and sped up data ingestion by 20%.• Proposed and implemented new architecture that’s aligned with business goals through collaboration with stakeholders. Replaced existing monolithic desktop app architecture with a 3-tier architecture, consisting of a database store, business logic, and UI layer. Met the business requirements of still running everything locally.• Employed agile methodology to perform tradeoff analyses, refine design, and get buy in from stakeholders. 1) 3-tier vs monolithic pros: better reliability (UI failures do not affect data ingestion), better maintainability (modules are less coupled), newer technologies (easier to learn/use), horizontal scalability (services can be scaled if business needs change). cons: slower to develop (more technologies involved, IPC, harder to test), tougher to deploy (need to manage all services separately). decision: moved to 3-tier architecture after estimating time to completion was fine. 2) SQLite vs OpenSearch pros: embedded (same process as ingestion), less overhead (less time spent indexing, less file space, less memory), faster ingestion when data is split amongst multiple database files cons: more complex querying (databases are split up), less analytics (need to write in house) decision: chose SQLite because OpenSearch's slower ingestion time and increased resource usage would degrade user experience.• Configured OpenSearch & SQLite database, designed GraphQL schema, implemented application server using Node.js and Express.js + frontend with React, Redux, electron.js, d3.js, and material-UI

Computer Science, 2Nd Year

Activities and Societies: GT Trading Club, Researching Quantum Info Theory with Rogues Gallery, Club GolfComputer Science (THREADS.

High School Diploma, 4.65 Gpa

Activities and Societies: Academic/QuizBowl Team Captain; Varsity Golf Captain; Math, Arts, Science Achievement Center (Summer Camp.