{
  "metadata": {
    "schema_version": "1.0.0",
    "profile_id": "09-05",
    "created_at": "2026-09-22",
    "as_of_date": "2026-09-22",
    "record_kind": "fictional_sample",
    "verification_status": "not_verified",
    "is_real_person_record": false,
    "disclaimer": "Fictional demonstration candidate. All employers, education, projects, achievements and outcomes are illustrative and unverified. Not a real application or licence record.",
    "source_basis": {
      "biography": "original synthetic example",
      "structure_reference": "sr-software-engineer-fullstack-angular-react-nodejs.pdf",
      "reference_used_for": "section hierarchy and visual direction only; no Ajay Prajapat biographical claims copied",
      "web_reference": "https://kyros.on3-step.com/homereveal",
      "web_reference_status": "requested inspiration; live JavaScript visual layout could not be independently rendered"
    },
    "category": {
      "id": 9,
      "name": "Product & Project Management",
      "role_index": 5,
      "role_title": "Business Analyst"
    },
    "publishing": {
      "search_indexing": false,
      "external_contact_enabled": false,
      "real_credentials_required_before_publication": true
    }
  },
  "basics": {
    "name": "Dev Rao",
    "headline": "Business Analyst",
    "specialisation": "requirements elicitation, process modelling, data analysis",
    "location": {
      "city": "Ahmedabad",
      "country": "India"
    },
    "contact": {
      "email": "dev.rao@example.com",
      "phone": null,
      "website": null,
      "linkedin": null,
      "portfolio_url": null,
      "contact_status": "placeholder_not_for_contact"
    },
    "career_start_date": "2014-07-01",
    "experience_years": 12,
    "seniority": "experienced specialist",
    "languages": [
      {
        "language": "English",
        "proficiency": "professional working - fictional sample"
      },
      {
        "language": "Hindi",
        "proficiency": "professional working - fictional sample"
      }
    ],
    "work_preferences": {
      "arrangement": "hybrid; remote feasibility discussed per role",
      "relocation": "open to discussion - sample preference",
      "availability": "not confirmed; discuss before an interview",
      "employment_interest": [
        "full-time",
        "defined project or fixed-term work where appropriate"
      ]
    }
  },
  "executive_summary": [
    "Business Analyst with an illustrative 12-year career in product strategy, programme delivery and team coordination. Combines requirements elicitation, process modelling, data analysis with disciplined documentation, practical coordination and clear communication. The sample career progresses from focused execution to independent workstream ownership, with responsibilities and boundaries described for each appointment.",
    "Selected work includes operations process redesign, requirements traceability and reporting definition review. These examples explain the original problem, individual contribution, deliverables, review approach and remaining limitations rather than relying on unsupported headline claims.",
    "Prepared for experienced business analyst opportunities requiring dependable delivery, thoughtful professional judgement and collaboration. The qualification narrative includes MBA in Business Analysis. Every named organisation and outcome in this record is fictional; professional eligibility is not independently established."
  ],
  "professional_mission": "Turn a clear brief into dependable product strategy, programme delivery and team coordination work: understand the context, apply requirements elicitation and process modelling, record the evidence and explain the limitations before handover.",
  "core_competencies": [
    {
      "name": "requirements elicitation",
      "level": "advanced practice - illustrative",
      "application": "Applied to operations process redesign through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "process modelling",
      "level": "advanced practice - illustrative",
      "application": "Applied to requirements traceability through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "data analysis",
      "level": "advanced practice - illustrative",
      "application": "Applied to reporting definition review through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "acceptance criteria",
      "level": "advanced practice - illustrative",
      "application": "Applied to operations process redesign through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "workshop facilitation",
      "level": "advanced practice - illustrative",
      "application": "Applied to requirements traceability through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "traceability",
      "level": "advanced practice - illustrative",
      "application": "Applied to reporting definition review through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "gap analysis",
      "level": "advanced practice - illustrative",
      "application": "Applied to operations process redesign through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "documentation",
      "level": "advanced practice - illustrative",
      "application": "Applied to requirements traceability through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    }
  ],
  "specialist_practice": {
    "title": "Delivery accountability",
    "summary": "Commercial authority and acceptance decisions remain with the designated human owners in each example.",
    "working_principles": [
      "Define outcomes, decision owners and constraints before committing to a delivery plan.",
      "Make dependencies, changes and trade-offs visible to stakeholders.",
      "Distinguish observed results from forecasts and keep a traceable decision history."
    ],
    "tools_and_methods": [
      "requirements elicitation",
      "process modelling",
      "data analysis",
      "acceptance criteria",
      "workshop facilitation",
      "traceability",
      "gap analysis",
      "documentation"
    ],
    "professional_scope": "The sample focuses on requirements elicitation, process modelling, data analysis. Approvals, supervision and specialist input are identified in each work package; work outside this scope is referred to the designated responsible person."
  },
  "projects": [
    {
      "id": "P1",
      "title": "Operations process redesign",
      "category": "requirements elicitation",
      "organisation": "Meridian Product Advisory (fictional)",
      "employment_id": "EXP-4",
      "start_date": "2024-01-01",
      "end_date": "2024-06-30",
      "project_context": "Fictional internal work programme in product strategy, programme delivery and team coordination; not a real client case study.",
      "problem": "Manual handoffs created inconsistent case states.",
      "objective": "Create a workable response to this issue through requirements elicitation, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Business Analyst; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Modelled the current process and agreed target requirements.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used requirements elicitation to turn the brief into a sequenced work package.",
        "Applied process modelling and data analysis while coordinating reviews with the designated owner. Kept decision notes so collaborators could separate facts, assumptions and changes.",
        "Assembled the handover material, explained open limitations and agreed which items needed further review rather than presenting them as completed."
      ],
      "methods": [
        "requirements elicitation",
        "process modelling",
        "data analysis",
        "acceptance criteria"
      ],
      "deliverables": [
        "Operations process redesign - scoped brief",
        "Operations process redesign - reviewed working package",
        "Operations process redesign - handover and learning summary"
      ],
      "review_method": "Reviewed the scoped output against the agreed brief, recorded exceptions and checked that key conclusions could be traced to observations. The review package calls for a outcome and scope brief and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for operations process redesign, with clearer ownership and reviewable records. This is a fictional qualitative result; no real performance measurement or external acceptance evidence is supplied."
      ],
      "metrics": [],
      "limitations": "Synthetic demonstration only. Commercial authority and acceptance decisions remain with the designated human owners in each example. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E1.1",
          "title": "Operations process redesign: outcome and scope brief",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.2",
          "title": "Operations process redesign: prioritised delivery or discovery plan",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.3",
          "title": "Operations process redesign: decision and retrospective record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    },
    {
      "id": "P2",
      "title": "Requirements traceability",
      "category": "process modelling",
      "organisation": "Meridian Product Advisory (fictional)",
      "employment_id": "EXP-4",
      "start_date": "2025-01-01",
      "end_date": "2025-06-30",
      "project_context": "Fictional internal work programme in product strategy, programme delivery and team coordination; not a real client case study.",
      "problem": "Changes reached development without context.",
      "objective": "Create a workable response to this issue through process modelling, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Business Analyst; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Linked needs to scenarios and acceptance evidence.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used data analysis to turn the brief into a sequenced work package.",
        "Applied acceptance criteria and workshop facilitation while coordinating reviews with the designated owner. Kept decision notes so collaborators could separate facts, assumptions and changes.",
        "Assembled the handover material, explained open limitations and agreed which items needed further review rather than presenting them as completed."
      ],
      "methods": [
        "process modelling",
        "data analysis",
        "acceptance criteria",
        "workshop facilitation"
      ],
      "deliverables": [
        "Requirements traceability - scoped brief",
        "Requirements traceability - reviewed working package",
        "Requirements traceability - handover and learning summary"
      ],
      "review_method": "Reviewed the scoped output against the agreed brief, recorded exceptions and checked that key conclusions could be traced to observations. The review package calls for a prioritised delivery or discovery plan and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for requirements traceability, with clearer ownership and reviewable records. This is a fictional qualitative result; no real performance measurement or external acceptance evidence is supplied."
      ],
      "metrics": [],
      "limitations": "Synthetic demonstration only. Commercial authority and acceptance decisions remain with the designated human owners in each example. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E2.1",
          "title": "Requirements traceability: outcome and scope brief",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.2",
          "title": "Requirements traceability: prioritised delivery or discovery plan",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.3",
          "title": "Requirements traceability: decision and retrospective record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    },
    {
      "id": "P3",
      "title": "Reporting definition review",
      "category": "data analysis",
      "organisation": "Northline Product Advisory (fictional)",
      "employment_id": "EXP-3",
      "start_date": "2020-01-01",
      "end_date": "2020-06-30",
      "project_context": "Fictional internal work programme in product strategy, programme delivery and team coordination; not a real client case study.",
      "problem": "Business measures used conflicting rules.",
      "objective": "Create a workable response to this issue through data analysis, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Business Analyst; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Facilitated metric definitions and sample reconciliation.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used workshop facilitation to turn the brief into a sequenced work package.",
        "Applied traceability and gap analysis while coordinating reviews with the designated owner. Kept decision notes so collaborators could separate facts, assumptions and changes.",
        "Assembled the handover material, explained open limitations and agreed which items needed further review rather than presenting them as completed."
      ],
      "methods": [
        "data analysis",
        "acceptance criteria",
        "workshop facilitation",
        "traceability"
      ],
      "deliverables": [
        "Reporting definition review - scoped brief",
        "Reporting definition review - reviewed working package",
        "Reporting definition review - handover and learning summary"
      ],
      "review_method": "Reviewed the scoped output against the agreed brief, recorded exceptions and checked that key conclusions could be traced to observations. The review package calls for a decision and retrospective record and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for reporting definition review, with clearer ownership and reviewable records. This is a fictional qualitative result; no real performance measurement or external acceptance evidence is supplied."
      ],
      "metrics": [],
      "limitations": "Synthetic demonstration only. Commercial authority and acceptance decisions remain with the designated human owners in each example. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E3.1",
          "title": "Reporting definition review: outcome and scope brief",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.2",
          "title": "Reporting definition review: prioritised delivery or discovery plan",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.3",
          "title": "Reporting definition review: decision and retrospective record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    }
  ],
  "experience": [
    {
      "id": "EXP-4",
      "position": "Business Analyst",
      "career_level": "experienced specialist / workstream owner",
      "organisation": "Meridian Product Advisory (fictional)",
      "location": "Ahmedabad, India",
      "start_date": "2023-07-01",
      "end_date": null,
      "employment_type": "full-time - fictional record",
      "scope": "Independent ownership of scoped business analyst work, coordinating contributors and making review requirements explicit. Includes the first two selected work examples.",
      "responsibilities": [
        "Modelled the current process and agreed target requirements.",
        "Linked needs to scenarios and acceptance evidence.",
        "Led brief clarification and prioritised work using requirements elicitation, process modelling and data analysis. Raised unresolved constraints before committing to the next stage.",
        "Coordinated peer reviews and handover preparation; used a outcome and scope brief to distinguish completed work, assumptions and follow-up needs.",
        "Supported colleagues with practical examples of acceptance criteria and maintained a concise learning record after important assignments."
      ],
      "selected_project_ids": [
        "P1",
        "P2"
      ],
      "result_context": "Illustrative career responsibilities. Employer confirmation and underlying work records are not supplied.",
      "verification_status": "not_verified"
    },
    {
      "id": "EXP-3",
      "position": "Senior Business Analyst",
      "career_level": "senior specialist",
      "organisation": "Northline Product Advisory (fictional)",
      "location": "Ahmedabad, India",
      "start_date": "2019-07-01",
      "end_date": "2023-06-30",
      "employment_type": "full-time - fictional record",
      "scope": "Owned defined assignments and supported cross-functional coordination. Developed deeper practice in data analysis and acceptance criteria.",
      "responsibilities": [
        "Facilitated metric definitions and sample reconciliation.",
        "Translated incoming requirements into a sequenced plan and aligned responsibilities with the project or service owner.",
        "Applied workshop facilitation and traceability to resolve delivery questions while maintaining source and decision notes.",
        "Introduced reusable working documents and reviewed exceptions with the responsible specialist rather than silently changing scope.",
        "Prepared a decision and retrospective record so the next team could understand the work and remaining questions."
      ],
      "selected_project_ids": [
        "P3"
      ],
      "result_context": "Illustrative career responsibilities. Employer confirmation and underlying work records are not supplied.",
      "verification_status": "not_verified"
    },
    {
      "id": "EXP-2",
      "position": "Business Analyst",
      "career_level": "independent practitioner",
      "organisation": "Cedarbridge Product Advisory (fictional)",
      "location": "Ahmedabad, India",
      "start_date": "2016-07-01",
      "end_date": "2019-06-30",
      "employment_type": "full-time - fictional record",
      "scope": "Progressed from supported tasks to independently managed assignments, with review available for unfamiliar or higher-risk decisions.",
      "responsibilities": [
        "Handled recurring work involving requirements elicitation and process modelling using a documented preparation and review process.",
        "Supported requirements traceability by organising inputs, maintaining issue notes and incorporating reviewer feedback.",
        "Coordinated colleagues and internal stakeholders using concise status updates, clear questions and agreed next steps.",
        "Improved record consistency through gap analysis and documented handover expectations."
      ],
      "selected_project_ids": [],
      "result_context": "Illustrative career responsibilities. Employer confirmation and underlying work records are not supplied.",
      "verification_status": "not_verified"
    },
    {
      "id": "EXP-1",
      "position": "Assistant Business Analyst",
      "career_level": "foundation",
      "organisation": "Cedarbridge Product Advisory (fictional)",
      "location": "Ahmedabad, India",
      "start_date": "2014-07-01",
      "end_date": "2016-06-30",
      "employment_type": "full-time - fictional record",
      "scope": "Built practical foundations through supervised assignments, routine documentation and feedback from experienced colleagues.",
      "responsibilities": [
        "Assisted with requirements elicitation and data analysis within an agreed scope and escalated unfamiliar work.",
        "Prepared inputs and checked completeness before passing work to the responsible reviewer.",
        "Maintained task records and learned to communicate assumptions, constraints and observed problems clearly.",
        "Applied review feedback to subsequent assignments and developed a dependable working routine."
      ],
      "selected_project_ids": [],
      "result_context": "Illustrative career responsibilities. Employer confirmation and underlying work records are not supplied.",
      "verification_status": "not_verified"
    }
  ],
  "career_achievements": [
    {
      "title": "Operations process redesign",
      "description": "Modelled the current process and agreed target requirements. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P1",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Requirements traceability",
      "description": "Linked needs to scenarios and acceptance evidence. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P2",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Reporting definition review",
      "description": "Facilitated metric definitions and sample reconciliation. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P3",
      "verification_status": "not_verified",
      "metrics": []
    }
  ],
  "education": [
    {
      "id": "EDU-2",
      "qualification": "MBA in Business Analysis",
      "institution": "Asterbridge Institute of Professional Studies (fictional institution)",
      "start_date": "2012-07-01",
      "end_date": "2014-05-31",
      "status": "completed - fictional record",
      "focus": [
        "requirements elicitation",
        "process modelling",
        "acceptance criteria"
      ],
      "capstone": "Specialist study on operations process redesign; an illustrative learning project, not a published result.",
      "verification_status": "not_verified"
    },
    {
      "id": "EDU-1",
      "qualification": "B.Com in Business Administration",
      "institution": "Cedarhaven College of Applied Studies (fictional institution)",
      "start_date": "2009-07-01",
      "end_date": "2012-05-31",
      "status": "completed - fictional record",
      "focus": [
        "data analysis",
        "workshop facilitation",
        "traceability"
      ],
      "capstone": "Applied coursework in requirements elicitation, documentation and reviewed practical assignments.",
      "verification_status": "not_verified"
    }
  ],
  "professional_development": [
    {
      "title": "Stakeholder facilitation workshop",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2023,
      "learning_focus": "Requirements elicitation and acceptance criteria in the context of business analyst work.",
      "application": "Used reflective exercises and a bounded practice example related to operations process redesign.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    },
    {
      "title": "Outcome measurement practicum",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2024,
      "learning_focus": "Process modelling and workshop facilitation in the context of business analyst work.",
      "application": "Used reflective exercises and a bounded practice example related to requirements traceability.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    },
    {
      "title": "Dependency and risk planning",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2025,
      "learning_focus": "Data analysis and traceability in the context of business analyst work.",
      "application": "Used reflective exercises and a bounded practice example related to reporting definition review.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    }
  ],
  "credentials": {
    "professional_registration": null,
    "licence_number": null,
    "issuing_authority": null,
    "credential_documents": [],
    "status": "not_provided",
    "scope_note": "Commercial authority and acceptance decisions remain with the designated human owners in each example.",
    "education_note": "Synthetic qualification and institution names illustrate profile fields only; they are not a validated qualification route or recognised accreditation claim."
  },
  "leadership_and_knowledge_sharing": [
    {
      "title": "Peer learning and practical guidance",
      "description": "Created short examples on requirements elicitation and acceptance criteria for colleagues. Separated personal preferences from agreed team procedures and recorded useful questions."
    },
    {
      "title": "Review and handover discipline",
      "description": "Facilitated practical reviews of requirements traceability, ensuring that unresolved issues retained a named owner rather than disappearing from final presentations."
    }
  ],
  "record_integrity": {
    "source_status": "synthetic_and_unverified",
    "actual_outcome_metrics_supplied": false,
    "references": [],
    "references_note": "No real referee, endorsement, award, publication, membership or licence is supplied.",
    "permission_note": "Use for templates, product demonstrations and test data only. Replace fictional claims and remove the demo label only after approval of real candidate information.",
    "privacy_note": "No actual birth date, street address, government identifier, patient record or private third-party information is included."
  },
  "search_keywords": [
    "requirements elicitation",
    "process modelling",
    "data analysis",
    "acceptance criteria",
    "workshop facilitation",
    "traceability",
    "gap analysis",
    "documentation",
    "Business Analyst",
    "Product & Project Management"
  ]
}