Merge branch 'main' of ssh://git.sdf.org/axs/website
This commit is contained in:
commit
1290d82752
38
Makefile
Normal file
38
Makefile
Normal file
@ -0,0 +1,38 @@
|
||||
|
||||
DEST ?= axs@sdf.org:html
|
||||
SITE_URL ?= https://axs.sdf.org
|
||||
|
||||
.PHONY: default help publish
|
||||
|
||||
build: #>
|
||||
@echo "\t 🏗️ Building site"
|
||||
@# We call hugo with two options:
|
||||
@# --cleanDestinationDir, to remove deleted files
|
||||
@# --minify, to compress files my removing extra whitespace
|
||||
hugo --cleanDestinationDir --minify
|
||||
|
||||
publish: build #> Publish site
|
||||
@echo "Publishing..."
|
||||
@# rsync options:
|
||||
@# verbose: show each operation
|
||||
@# links: preserve symlinks
|
||||
@# safe-links: ignore symlinks that point outside of tree
|
||||
@# times: preserve modification times
|
||||
@# delete: delete extraneous files, i.e., files on destination
|
||||
@# chmod: set permsions
|
||||
@echo "\t ⛟ Copying from public to ${DEST}"
|
||||
@rsync \
|
||||
--verbose \
|
||||
--recursive \
|
||||
--links \
|
||||
--safe-links \
|
||||
--times \
|
||||
--delete \
|
||||
--cvs-exclude \
|
||||
--chmod=D755,F644 \
|
||||
public/ \
|
||||
${DEST}
|
||||
@echo "\t 🛡️ Setting permissions"
|
||||
@ssh axs@sdf.org 'mkhomepg -p'
|
||||
@echo "✓ Publising complete"
|
||||
@echo "\nThe site should be available on ${SITE_URL}"
|
@ -6,3 +6,7 @@ draft: false
|
||||
|
||||
Maybe I will add a brief bio. Until then, this is just a landing page for
|
||||
information about me.
|
||||
|
||||
{{< rawhtml >}}
|
||||
<a rel="me" href="https://mastodon.sdf.org/@axs">Mastodon</a>
|
||||
{{< /rawhtml >}}
|
||||
|
@ -1,7 +1,107 @@
|
||||
---
|
||||
title: 'Resume'
|
||||
title: Résumé
|
||||
date: 2023-11-08T10:22:23-08:00
|
||||
draft: true
|
||||
draft: false
|
||||
data:
|
||||
jobs:
|
||||
EA:
|
||||
name: Electronic Arts
|
||||
url: 'https://ea.com'
|
||||
Glu:
|
||||
name: Glu Mobile
|
||||
url: 'https://glu.com'
|
||||
---
|
||||
|
||||
Just a placeholder
|
||||
<!--
|
||||
Consider placing data in the YAML block. Then insert this in a way that makes
|
||||
sense, given the output format. The advantage is that it makes parsing easier
|
||||
and more robust. The trade-off is the distance between data and text.
|
||||
-->
|
||||
|
||||
<!-- revise with text from resume writer -->
|
||||
|
||||
Business leader with strong analytics, data, and marketing expertise. I have
|
||||
applied data analytics and programming to deliver results across a wide range
|
||||
of industries, including mobile game marketing, web publishing, the electrical
|
||||
grid, and transportation. As a manager, I uncover opportunities, remove
|
||||
impediments, and guide team members toward professional growth. I am known for
|
||||
developing a strong network within an organization, driving innovative
|
||||
technical solutions, and effectively coaching a diverse set of team members.
|
||||
|
||||
{{< rawhtml >}}
|
||||
<a rel="me" href="https://mastodon.sdf.org/@axs">Mastodon</a>
|
||||
{{< /rawhtml >}}
|
||||
|
||||
## Work Experience
|
||||
|
||||
### [Electronic Arts (EA)](https://ea.com)
|
||||
_Senior Diector of Growth Analytics and Data Science (2020--2023), including
|
||||
[Glu Mobile](https://glu.com)_
|
||||
|
||||
<details>
|
||||
<summary>
|
||||
Building and leading teams with a focus on growth marketing, including
|
||||
a cross-functional business intelligence team (in partnership with
|
||||
engineering), marking analysts (embedded with the Marketing team), and data
|
||||
science with a focus on user acquisition. I define the vision for growth
|
||||
marketing analytics and the execution the plan. As a member of EA Mobile’s
|
||||
Growth Team senior leadership team, I collaborate across teams to more
|
||||
effectively measure the health of players and games, identify differences in
|
||||
our players, and discover new opportunities to grow revenue revenue.
|
||||
</summary>
|
||||
Accomplishments include:
|
||||
|
||||
- *Saving the company \$100 million in marketing expenses when launching a
|
||||
new game.* I surfaced and demonstrated that the incumbent forecasting
|
||||
methodology would lead to bad business decisions prior to game launch. I
|
||||
then convened a cross-functional team to tackle the problem. Additionally,
|
||||
I implemented a transition state model for forecasting cohort growth as an
|
||||
\texttt{R} package. In addition to reducing wasteful spend, the approach I
|
||||
drove enabled informed, constructive conversations between the game
|
||||
development and marketing teams.
|
||||
|
||||
- *Cutting the effort required for analyzing marketing campaigns in half.*
|
||||
Prior to me joining Glu, we stored player activities in terms game events
|
||||
and did not completely track our marketing activities. Furthermore, the
|
||||
tools we were using (Hive and Hadoop) required specialized computing
|
||||
skills. I assembled a cross-functional team effort to modernize our
|
||||
business intelligence practice. We now use a scalable, cloud-based
|
||||
relational data warehouse with analytics friendly tables of key business
|
||||
processes. We are adopting this approach across the entire EA Mobile
|
||||
portfolio.
|
||||
|
||||
</details>
|
||||
<!--
|
||||
\item \emph{Cutting the effort required for analyzing marketing campaigns in
|
||||
half.} Prior to me joining Glu, we stored player activities in terms game
|
||||
events and did not completely track our marketing activities.
|
||||
Furthermore, the tools we were using (Hive and Hadoop) required
|
||||
specialized computing skills. I assembled a cross-functional team effort
|
||||
to modernize our business intelligence practice. We now use a scalable,
|
||||
cloud-based relational data warehouse with analytics friendly tables of
|
||||
key business processes. We are adopting this approach across the entire EA
|
||||
Mobile portfolio.
|
||||
|
||||
\item \emph{Navigating Apple’s App Tracking Transparency initiative to
|
||||
maintain acquisition budgets.} Apple’s
|
||||
\href{https://developer.apple.com/documentation/storekit/skadnetwork}{SKAdNetwork}
|
||||
initiative is a threat to businesses that have relied on performance
|
||||
marketing and use attribution data to manage user acquisition campaigns.
|
||||
I lead our business intelligence and data science teams through our
|
||||
response to this challenge. We built new pipelines and analytical
|
||||
strategies that let us continue advertising budget on iOS while
|
||||
competitors drastically reduced budgets.
|
||||
|
||||
\item \emph{Increasing the returns from product marketing.} Building an
|
||||
embedded marketing analysts team. Our Marketing team had operated without
|
||||
dedicated analytical support prior to my arrival. As a result, the team
|
||||
was limited in its ability to design experiments that would result in
|
||||
unbiased measurements. Our move to an embedded model means that analysts
|
||||
now have the full context of marketing initiatives, the authority to
|
||||
design experiments, and responsibility for interpreting results. We set
|
||||
the combined marketing and marketing analysts team on a path of continuous
|
||||
improvement cycles with clear ties between marketing activities and
|
||||
incremental revenue.
|
||||
|
||||
\end{itemize}
|
||||
-->
|
||||
|
2
layouts/shortcodes/rawhtml.html
Normal file
2
layouts/shortcodes/rawhtml.html
Normal file
@ -0,0 +1,2 @@
|
||||
<!-- raw html -->
|
||||
{{.Inner}}
|
Loading…
Reference in New Issue
Block a user