This System Requirements Document specifies UX/UI Design Portfolio (project name: cool-senior), a public portfolio website for senior UX/UI designer saikiran saidesigns, based in India. The product's intent is singular and explicit: it is a senior UX/UI design portfolio, and it must help the owner get hired.
The audience is twofold. First, hiring reviewers — recruiters, design leads, and hiring managers — who arrive anonymously, judge craft and evidence quickly, and need to understand who the designer is, what they have shipped, and how to reach them. Second, the portfolio owner, who presents case studies and keeps the portfolio current so that the work itself becomes the hiring argument.
The portfolio is delivered as a public, no-account, first-party web experience. Its visual and interaction direction — "Craft that hires: design and code in split dialogue" — treats the site as proof of both design and engineering capability in a single frame.
The product is a three-destination public portfolio: Landing, Case Studies, and Contact. All three are anonymously reachable; no visitor account, sign-in, or identity establishment exists anywhere in the accepted scope. The hiring reviewer is the primary anonymous visitor; the portfolio owner is the author whose work and contact details the site presents.
Delivery is first-party custom UI backed by a shared application backend and an application database. The backend serves the portfolio's content and the contact handoff; the frontend renders the split design/code composition described in the creative direction. Nothing in the accepted requirements calls for provider-owned surfaces, external destinations, or headless delivery.
The current horizon covers exactly the three accepted pages and the accepted behaviors described below. Future ideas — additional case studies, richer content management, analytics — are not current requirements and are not represented in any page or acceptance criterion.
Removed from scope
clamp(52px, 9vw, 132px) type; subline; ink CTA button (0px radius); code panel with mono rows; hairline divider; tangerine section rule.FR-1 — Public portfolio entry (explicit) As a Hiring Reviewer, I should open the public Landing page and immediately understand who the designer is, what they do, and where to go next, so that I can decide whether to continue.
FR-2 — Senior UX/UI portfolio identity (explicit) As a Portfolio Owner, I should present the portfolio as a senior UX/UI design portfolio, so that the site itself communicates seniority and craft.
FR-3 — Get hired (explicit) As a Portfolio Owner, I should give hiring reviewers the evidence and the contact path they need, so that the portfolio helps me get hired.
FR-4 — Read case studies (required_inference) As a Hiring Reviewer, I should read the designer's case studies and profile, so that I can judge fit for a role.
FR-5 — Contact the designer (required_inference) As a Hiring Reviewer, I should find a way to contact the designer, so that I can start a conversation about a role.
FR-6 — Keep the portfolio current (required_inference) As a Portfolio Owner, I should have the portfolio present my current case studies and contact details, so that reviewers always see accurate work.
Saikiran saidesigns is a senior UX/UI designer based in India. The portfolio is his professional argument: it must feel made by a designer who also builds. His primary goal is to get hired — every page exists to move a hiring reviewer toward that decision. His distinct responsibilities are authoring the hero positioning, publishing case studies with role/year/platform metadata, and keeping contact details accurate. His inputs are his own project work and contact information; his decisions are what to show and how to frame it. He interacts with the Hiring Reviewer only indirectly, through the evidence and contact path the site presents. Observable success: reviewers read case studies and reach out through Contact.
The hiring reviewer is a recruiter, design lead, or hiring manager evaluating the designer for a role. They arrive anonymously, with no account, and judge craft and evidence fast. Their primary goal is to decide whether this designer fits the role. Their distinct responsibilities are scanning the hero for positioning, reading case studies for evidence of shipped work, and using Contact to start a conversation. Their inputs are the hero copy, case study rows, and contact form; their decisions are whether to continue reading and whether to reach out. They interact with the Portfolio Owner through the contact message. Observable success: they understand the designer's work and can contact them without friction.
The creative direction "Craft that hires: design and code in split dialogue" (muse: Adham Dannaway) is authoritative.
clamp(52px, 9vw, 132px).The public entry is a full-height 50/50 split that stages design and code in dialogue. The left half is a warm paper panel carrying an oversized ink headline stacked in three lines, a short subline, and an ink CTA sitting under the headline, left-aligned. The right half is a deep ink code panel with mono metadata rows and a thin tangerine rule. A 1px ink line divides the halves. The headline spans the left panel edge to edge at clamp(52px, 9vw, 132px). One tangerine rule marks the section start. The composition recomposes only the accepted hero copy, CTA, and metadata — it introduces no new behavior or destination.
Interaction Model: Animated Motion Tempo: expressive Hero Dimensionality: layered_2d
Landing Hero Motion Brief
prefers-reduced-motion, a usable static arrangement is provided; all items remain fully readable.backend, database, and frontend services; the backend is extended with routes and modules rather than adding new services.
saikiran saidesignsIndia
I design interfaces and write the code that proves them. Read the case studies.

saikiran saidesignsIndia
I design interfaces and write the code that proves them. Read the case studies.
No comments yet. Be the first!