toochukwuogbonna

Challenge

[How do I structure portfolio data so hiring managers can quickly see my systems thinking and WordPress capability at the same time without it reading like an engineering resume or a beginner WordPress blog?]

Approach

[I researched TAM role requirements across four real Automattic job postings, extracted the competencies being evaluated, and mapped each portfolio section to a specific hiring signal. I designed a case study structure with four fields — Challenge, Approach, Outcome, Skills Demonstrated — to mirror how a TAM documents a partner engagement. I planned to use ACF for custom fields, then discovered WordPress.com platform constraints limited that option, so I pivoted to native WordPress fields and structured post formatting to achieve the same result without a plugin dependency]

Outcome

[I learned that constraints force pragmatism — architectural elegance matters less than shipping something auditable. The pivot from ACF to native fields was not a compromise, it was a systems decision made under real conditions. That decision process is itself evidence of TAM thinking: identify the constraint, assess the options, choose the path that gets the partner to a working outcome]

WordPress Skills Demonstrated

. Post structuring and content architecture without plugin dependency

. Platform constraint diagnosis and workaround decision-making

. Iterative build process with documented reasoning

. Data field design for structured, queryable content