Skip to content

PRODUCT.md

Latest commit

 

History

History
63 lines (38 loc) · 3.59 KB

PRODUCT.md

File metadata and controls

63 lines (38 loc) · 3.59 KB
Raw

Product

Register

brand

Users

Three co-equal audiences, each with different stakes:

  1. Recruiters & hiring managers — Senior engineers at enterprise financial-tech companies. Scanning for signal on data platform depth, Azure/ETL credibility, and whether this person is a legitimate senior hire or a resume inflater. Time budget: 90 seconds per page.

  2. O1/EB1 reviewers — USCIS officers and immigration attorneys reading the site as a legal exhibit. They scan for: published peer-reviewed work with DOIs, professional memberships (IEEE), academic honors, and institutional affiliations. Extraordinary ability must be visible above the fold.

  3. Research collaborators & academics — PhD supervisors, co-authors, and conference reviewers evaluating publication quality, ORCID linkage, Zenodo indexing, and doctoral trajectory at University of the Cumberlands.

All three audiences arrive skeptical. None has time to dig. The portfolio must surface proof, not promise.

Product Purpose

Alan Palayil's professional portfolio — a persistent, public evidence exhibit that:

  • Establishes enterprise data platform credibility (Genworth Financial, Azure Synapse, investment accounting pipelines)
  • Surfaces 4 Zenodo-published scholarly articles with DOIs as primary academic proof
  • Signals PhD candidacy in Information Technology and IEEE membership
  • Converts recruiter attention into contact with no friction

Success = a skeptical reviewer walks away confident that the claims are real and the person is senior.

Brand Personality

Precise · Rigorous · Credible

Every claim backed by evidence. No vague superlatives. Academic rigor meets enterprise pragmatism. The design should feel like well-engineered infrastructure — purposeful, exact, nothing wasted — wrapped in a distinctive visual identity that communicates ambition without showing off.

Tone: expert-quiet. Doesn't need to shout. The DOIs do the talking.

Anti-references

  • Generic cream/warm-neutral AI-generated portfolios (the 2026 default)
  • Bootstrap-template developer portfolios — dark gray cards, purple gradient hero, generic system font
  • "Space theme as gimmick" — starfields that fight for attention with the content
  • Over-designed without substance — visual complexity that obscures rather than supports credentials
  • Academic CVs that feel bureaucratic and lifeless

Design Principles

  1. Evidence over assertion. Every section should surface a verifiable artifact: DOI, credential URL, IEEE member number, employer name. Claims without proof are noise.

  2. Signal hierarchy. The published papers and Genworth work are the primary credentials. The space aesthetic is atmosphere, not the message.

  3. Ambient distinctiveness. The galaxy background should make the portfolio memorable without making it feel like a game or a demo. Space is a texture that communicates scale and ambition, not a distraction.

  4. Earned restraint. Clean layout and strong typography do the structural work. Decoration appears only where it adds meaning — not as filler.

  5. Credibility at a glance. A recruiter who hits Cmd+Tab after 8 seconds should have absorbed: who this person is, where they work, and that they have published research. The fold is a proof-of-concept.

Accessibility & Inclusion

  • WCAG AA minimum (target AAA on critical text paths: hero, credentials, research)
  • prefers-reduced-motion respected — stars pause, comets stop, no content gated on animation
  • System font stack maintained (speed + legibility over personality)
  • Skip-to-content link present
  • Keyboard-navigable theme popover and work/education tabs