Data Scientist · Strategic Analytics Partner

I find what drives business performance, test where a change could make a difference, and use the results to shape the roadmap.

Cecilia Chen

I define up front how much improvement would justify action, then weigh the measured gains against the costs for each stakeholder before recommending what to do next.

How I think

Five questions I ask before recommending a change.

  1. What moved, and by how much?

    I start with magnitude and scope. A large percentage change on a small base can affect fewer people than a modest shift across the whole marketplace.

  2. Did the underlying behavior change?

    A metric can move because the audience changed, an event stopped firing, or people behaved differently. Each explanation calls for a different response.

  3. When did it start, and did it last?

    Timing helps narrow the explanations. Durability determines how much weight I give the signal once seasonality, novelty and reporting delays have had time to play out.

  4. Who felt the impact?

    I look for differences across customers, partners and channels. A local gain can shift attention, cost or opportunity elsewhere. I judge that trade-off against the objective for the marketplace as a whole.

  5. What if we acted? What if we waited?

    I weigh the expected gain against the cost of being wrong, the cost of delay and how easily we could reverse course. That tells me how much evidence the decision needs.

How I work

How I put those questions to the test.

  1. Frame a testable hypothesis.

    With the decision owner, I name the behavior we expect to change, the population at stake and the smallest effect worth acting on. I report both the rate change and the number affected.

  2. Validate the comparison.

    I check event coverage, identity and denominators. I compare like groups and choose a credible baseline or control before attributing movement to an intervention.

  3. Set the observation window.

    I align exposure and outcome dates, allow time for outcomes to mature, and check whether the effect persists across periods.

  4. Read the distribution and the trade-offs.

    I examine the overall estimate alongside segment results and guardrails. I identify who benefits, where uncertainty is greatest and whether a gain in one part of the business comes at another’s expense.

  5. Recommend an action and a review point.

    I specify what to change, who owns the decision and what evidence would justify expanding, revising or stopping it.

Selected work

Five projects. The decision behind each one.

Product Experiment · CRM return journey

What happens after a customer comes back?

Customers returning after CRM outreach spent just 20 to 30 seconds in the app. I recommended testing the return experience while CRM kept email and push outreach consistent.

Read the case

Audience and assignment

I clustered customers by recency, frequency and engagement using K-means. One previously active group had gone 30 days without opening the app. On their first eligible return, we randomized customers 50/50 to the existing personalized experience or the same experience with a Spotlight prompt. Each customer kept their assignment.

Readout and decision

Valid-lead conversion reached about 2.3% against a 1.5% baseline. The six-week test was designed to detect a one-percentage-point lift. I treated the observed 0.8-point difference as directional. Regular-listing click-through fell, so Product and Analytics reviewed browsing and quality measures as exposure expanded to 80%, then 100% of eligible returners. The test supported a rollout decision for the bundled experience. It could not isolate personalization or the effect of outreach.

Product Experiment · Search ranking

Would ranking for lead intent improve search?

A listing-level comparison showed no clear increase in lead submission as click-through rose. That gave us a reason to test a different ranking objective and a reason to keep watching clicks.

Read the case

Model and experiment

I defined the valid-lead target and designed the user-level randomized A/B test. ML owned training and deployment. Historical listing exposures and lead outcomes produced one propensity score per active listing within its market. With Engineering, I checked that impression, click and lead events reflected the order customers actually saw.

Readout and decision

After four weeks, click-through was down and lead submission trended up. The lead effect was statistically inconclusive. The click decline stayed within the agreed tolerance and page views per customer held steady. I recommended keeping the reversible change with 30-, 60- and 90-day value reviews. Product and Marketing retained the ranking and continued iterating.

Causal Inference · SEM incrementality

Would more paid search create demand we would otherwise miss?

New-construction visitors were progressing from browsing to inquiries. Before recommending more non-branded search spend, I wanted to know how many additional leads it would generate across channels, including organic.

Read the case

Choose the market as the unit of intervention

I built a ZIP-by-week panel and matched roughly 100 ZIP codes into 50 pairs using historical leads, traffic and available inventory. I checked balance and pre-test trends, then randomized one ZIP in each pair to receive about 20% more spend. The other continued at its usual level.

Estimate incremental demand

My primary estimate was a preregistered difference-in-differences comparison of total leads. I used CausalImpact as a robustness check and examined spend delivery, organic displacement and lead quality before interpreting the result.

Change the mix, then review

The estimated lift was positive but statistically inconclusive. I recommended shifting the existing search mix toward non-branded terms while monitoring cost, quality and market capacity. Marketing changed the allocation. A larger total budget would require stronger evidence of incremental return.

Modeling · Marketplace value

When more customers reach out, who benefits?

A customer contacting an agent signals intent. The agent still has to decide where to spend time. I helped our teams evaluate both perspectives before expanding a change that generated more inquiries.

Read the case

Measure each side of the exchange

On the customer side, I examined whether people progressed from browsing to a valid inquiry. On the agent side, I estimated the value of the opportunities those inquiries created. In Snowflake, I aggregated opportunity value across each experiment group and divided by everyone assigned, including customers who never submitted an inquiry. That kept the comparison meaningful even when the change affected who reached out.

Use disagreement to guide the decision

I compared each outcome with its own control baseline. If inquiries increased while expected value per assigned customer fell, my recommendation was to examine which listings gained exposure before expanding the change. Marketing used the agent-side measure to refine targeting. An inquiry showed customer intent, and estimated opportunity value helped assess the agent’s prospects. Neither established that a transaction closed.

Embracing AI · Analytics assistant

Which parts of a KPI investigation should an assistant own?

Analysts repeatedly rebuilt the same weekly comparisons before investigating a change. I built the reusable measurement layer and the rules for when a person should take a closer look.

Read the case

Data and review workflow

Versioned dbt models defined the grain, time window and denominator for each KPI. Historical ranges flagged unusual movement. Freshness and tracking checks came first. The assistant drafted a summary with the observation, plausible explanations, next check and responsible team. Analysts reviewed root-cause claims and business recommendations.

Pilot and evidence

We reconciled outputs with BI dashboards and Amplitude, then compared assistant drafts with manual analyst readouts across verticals. Noisy alerts and missing context informed threshold and routing revisions. Usage logs showed roughly 80% to 90% of the analytics team had tried the workflow. Pilot comparisons and team feedback suggested around 30% less preparation and coordination effort. That figure was an operational estimate.

Career arc

A nonlinear path with a consistent purpose.

I have kept moving closer to the moment where evidence becomes a decision.

01

AWS

Project management in a legal and commercial environment, including RFP work, contracts, and operational education.

02

Georgetown

Built the analytical foundation to connect technology, customer behavior, and business judgment.

03

American Chemical Society

Applied analytics to real business questions and strengthened the discipline of translating data clearly.

04

NetApp

In a strategy consulting program, I estimated country-level demand for enterprise storage and ranked markets by opportunity and distributor readiness. I presented a phased entry recommendation to the team in Spain.

05

Realtor.com

Partnered with Product, Marketing, and CRM teams across measurement, experimentation, and customer economics.

My view of data science

I see data science as a way to bring scientific rigor to decisions with lasting consequences.

In any industry, strategy helps us ask which outcomes matter. Data lets us test our assumptions, and critical judgment helps us weigh the evidence and choose where to invest for the long term.

Let’s connect on LinkedIn