I'm currently a frontend engineer for Bitcoin.com, where I work full-time on markets.bitcoin.com, a very slick cryptocurrency market analysis webapp.

TECH: React/Redux, Node.js



From 2013-2018 I worked as a full-stack web developer on an agile product team to maintain and build out new features for mashable.com, a media site with over 45 million monthly unique visitors. Besides developing on the main website, I also worked on adding more bells and whistles to our super sleek CMS, which the editorial team uses to bring you only the freshest of #viral #content.

TECH: Ruby on Rails, Backbone.js, React/Redux



GOOD Magazine was my first real employer out of college, and it was pretty much the best gig I could have hoped for as a new CS grad. I joined the team during their transition from a web magazine to a socially-impactful social network (before they transitioned back to a web magazine), and helped create and develop web applications for them as a junior software engineer.

TECH: Ruby on Rails, Backbone.js


Campus Events Commission

While I was a wee comp-sci student I worked on the online marketing team at Campus Events Commission, a student-run organization which brought awesome screenings, concerts and speaker events to UCLA. I built their main events site and various minisites for events like the Shorttakes Film Festival and Bruin Bash. To this day CEC remains the most high-perk gig I've ever held (no shade to GOOD or Mashable but they didn't give me front-row at Kendrick or a chance to meet Betty White).



mushaboom v.1

The previous iteration of this site was a very whimsical portfolio I built during my senior year at UCLA for my Design & Media Arts final project. I'm embarrassed of most of the work I had on there now, but it served me well for over 6 years.

TECH: HTML5, CSS3, jQuery


mushaboom v.dead

This was a redesigned version of my folio that I abandoned when it was at 90% completion. I can't really figure out why I never deemed it launch-worthy, but I'm glad it gets to be of use now, as a slot in the 'work' section of the portfolio I ended up using.