{
  "metadata": {
    "schema_version": "1.0.0",
    "profile_id": "01-04",
    "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": 1,
      "name": "Software & Application Development",
      "role_index": 4,
      "role_title": "Full-Stack Developer"
    },
    "publishing": {
      "search_indexing": false,
      "external_contact_enabled": false,
      "real_credentials_required_before_publication": true
    }
  },
  "basics": {
    "name": "Meera Mehta",
    "headline": "Full-Stack Developer",
    "specialisation": "Angular, React, Node.js",
    "location": {
      "city": "Jaipur",
      "country": "India"
    },
    "contact": {
      "email": "meera.mehta@example.com",
      "phone": null,
      "website": null,
      "linkedin": null,
      "portfolio_url": null,
      "contact_status": "placeholder_not_for_contact"
    },
    "career_start_date": "2013-07-01",
    "experience_years": 13,
    "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": [
    "Full-Stack Developer with an illustrative 13-year career in product engineering and enterprise applications. Combines angular, react, node.js 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 service operations workspace, customer onboarding flow and inventory event dashboard. These examples explain the original problem, individual contribution, deliverables, review approach and remaining limitations rather than relying on unsupported headline claims.",
    "Prepared for experienced full-stack developer opportunities requiring dependable delivery, thoughtful professional judgement and collaboration. The qualification narrative includes M.Tech in Software Systems. 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 engineering and enterprise applications work: understand the context, apply angular and react, record the evidence and explain the limitations before handover.",
  "core_competencies": [
    {
      "name": "Angular",
      "level": "advanced practice - illustrative",
      "application": "Applied to service operations workspace through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "React",
      "level": "advanced practice - illustrative",
      "application": "Applied to customer onboarding flow through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "Node.js",
      "level": "advanced practice - illustrative",
      "application": "Applied to inventory event dashboard through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "NestJS",
      "level": "advanced practice - illustrative",
      "application": "Applied to service operations workspace through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "TypeScript",
      "level": "advanced practice - illustrative",
      "application": "Applied to customer onboarding flow through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "PostgreSQL",
      "level": "advanced practice - illustrative",
      "application": "Applied to inventory event dashboard through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "Docker",
      "level": "advanced practice - illustrative",
      "application": "Applied to service operations workspace through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "CI/CD",
      "level": "advanced practice - illustrative",
      "application": "Applied to customer onboarding flow through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    }
  ],
  "specialist_practice": {
    "title": "Engineering judgement",
    "summary": "API boundaries, recovery behaviour, access control and release ownership are documented with each work example.",
    "working_principles": [
      "Trace user journeys through interface, service and data boundaries before implementation.",
      "Use small reviewable changes, automated checks and explicit rollback decisions.",
      "Separate personal contribution from team delivery and record operational limitations."
    ],
    "tools_and_methods": [
      "Angular",
      "React",
      "Node.js",
      "NestJS",
      "TypeScript",
      "PostgreSQL",
      "Docker",
      "CI/CD"
    ],
    "professional_scope": "The sample focuses on angular, react, node.js. 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": "Service operations workspace",
      "category": "Angular",
      "organisation": "Meridian Digital Systems (fictional)",
      "employment_id": "EXP-4",
      "start_date": "2023-01-01",
      "end_date": "2023-06-30",
      "project_context": "Fictional internal work programme in product engineering and enterprise applications; not a real client case study.",
      "problem": "Teams tracked requests in disconnected spreadsheets.",
      "objective": "Create a workable response to this issue through angular, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Full-Stack Developer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Built a tenant-aware portal with request routing and audit history.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used angular to turn the brief into a sequenced work package.",
        "Applied react and node.js 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": [
        "Angular",
        "React",
        "Node.js",
        "NestJS"
      ],
      "deliverables": [
        "Service operations workspace - scoped brief",
        "Service operations workspace - reviewed working package",
        "Service operations workspace - 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 architecture decision record and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for service operations workspace, 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. API boundaries, recovery behaviour, access control and release ownership are documented with each work example. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E1.1",
          "title": "Service operations workspace: architecture decision record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.2",
          "title": "Service operations workspace: reviewed pull-request summary",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.3",
          "title": "Service operations workspace: test and release checklist",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    },
    {
      "id": "P2",
      "title": "Customer onboarding flow",
      "category": "React",
      "organisation": "Meridian Digital Systems (fictional)",
      "employment_id": "EXP-4",
      "start_date": "2024-01-01",
      "end_date": "2024-06-30",
      "project_context": "Fictional internal work programme in product engineering and enterprise applications; not a real client case study.",
      "problem": "Incomplete submissions required repeated follow-up.",
      "objective": "Create a workable response to this issue through react, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Full-Stack Developer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Implemented validated forms and resumable onboarding APIs.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used node.js to turn the brief into a sequenced work package.",
        "Applied nestjs and typescript 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": [
        "React",
        "Node.js",
        "NestJS",
        "TypeScript"
      ],
      "deliverables": [
        "Customer onboarding flow - scoped brief",
        "Customer onboarding flow - reviewed working package",
        "Customer onboarding flow - 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 reviewed pull-request summary and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for customer onboarding flow, 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. API boundaries, recovery behaviour, access control and release ownership are documented with each work example. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E2.1",
          "title": "Customer onboarding flow: architecture decision record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.2",
          "title": "Customer onboarding flow: reviewed pull-request summary",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.3",
          "title": "Customer onboarding flow: test and release checklist",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    },
    {
      "id": "P3",
      "title": "Inventory event dashboard",
      "category": "Node.js",
      "organisation": "Northline Digital Systems (fictional)",
      "employment_id": "EXP-3",
      "start_date": "2019-01-01",
      "end_date": "2019-06-30",
      "project_context": "Fictional internal work programme in product engineering and enterprise applications; not a real client case study.",
      "problem": "Users could not explain stock adjustments.",
      "objective": "Create a workable response to this issue through node.js, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Full-Stack Developer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Connected an event ledger to searchable transaction timelines.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used typescript to turn the brief into a sequenced work package.",
        "Applied postgresql and docker 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": [
        "Node.js",
        "NestJS",
        "TypeScript",
        "PostgreSQL"
      ],
      "deliverables": [
        "Inventory event dashboard - scoped brief",
        "Inventory event dashboard - reviewed working package",
        "Inventory event dashboard - 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 test and release checklist and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for inventory event dashboard, 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. API boundaries, recovery behaviour, access control and release ownership are documented with each work example. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E3.1",
          "title": "Inventory event dashboard: architecture decision record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.2",
          "title": "Inventory event dashboard: reviewed pull-request summary",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.3",
          "title": "Inventory event dashboard: test and release checklist",
          "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": "Full-Stack Developer",
      "career_level": "experienced specialist / workstream owner",
      "organisation": "Meridian Digital Systems (fictional)",
      "location": "Jaipur, India",
      "start_date": "2022-07-01",
      "end_date": null,
      "employment_type": "full-time - fictional record",
      "scope": "Independent ownership of scoped full-stack developer work, coordinating contributors and making review requirements explicit. Includes the first two selected work examples.",
      "responsibilities": [
        "Built a tenant-aware portal with request routing and audit history.",
        "Implemented validated forms and resumable onboarding APIs.",
        "Led brief clarification and prioritised work using angular, react and node.js. Raised unresolved constraints before committing to the next stage.",
        "Coordinated peer reviews and handover preparation; used a architecture decision record to distinguish completed work, assumptions and follow-up needs.",
        "Supported colleagues with practical examples of nestjs 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 Full-Stack Developer",
      "career_level": "senior specialist",
      "organisation": "Northline Digital Systems (fictional)",
      "location": "Jaipur, India",
      "start_date": "2018-07-01",
      "end_date": "2022-06-30",
      "employment_type": "full-time - fictional record",
      "scope": "Owned defined assignments and supported cross-functional coordination. Developed deeper practice in node.js and nestjs.",
      "responsibilities": [
        "Connected an event ledger to searchable transaction timelines.",
        "Translated incoming requirements into a sequenced plan and aligned responsibilities with the project or service owner.",
        "Applied typescript and postgresql 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 test and release checklist 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": "Full-Stack Developer",
      "career_level": "independent practitioner",
      "organisation": "Cedarbridge Digital Systems (fictional)",
      "location": "Jaipur, India",
      "start_date": "2015-07-01",
      "end_date": "2018-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 angular and react using a documented preparation and review process.",
        "Supported customer onboarding flow 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 docker 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": "Junior Application Developer",
      "career_level": "foundation",
      "organisation": "Cedarbridge Digital Systems (fictional)",
      "location": "Jaipur, India",
      "start_date": "2013-07-01",
      "end_date": "2015-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 angular and node.js 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": "Service operations workspace",
      "description": "Built a tenant-aware portal with request routing and audit history. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P1",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Customer onboarding flow",
      "description": "Implemented validated forms and resumable onboarding APIs. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P2",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Inventory event dashboard",
      "description": "Connected an event ledger to searchable transaction timelines. 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": "M.Tech in Software Systems",
      "institution": "Asterbridge Institute of Professional Studies (fictional institution)",
      "start_date": "2011-07-01",
      "end_date": "2013-05-31",
      "status": "completed - fictional record",
      "focus": [
        "Angular",
        "React",
        "NestJS"
      ],
      "capstone": "Specialist study on service operations workspace; an illustrative learning project, not a published result.",
      "verification_status": "not_verified"
    },
    {
      "id": "EDU-1",
      "qualification": "B.Tech in Computer Science",
      "institution": "Cedarhaven College of Applied Studies (fictional institution)",
      "start_date": "2007-07-01",
      "end_date": "2011-05-31",
      "status": "completed - fictional record",
      "focus": [
        "Node.js",
        "TypeScript",
        "PostgreSQL"
      ],
      "capstone": "Applied coursework in angular, documentation and reviewed practical assignments.",
      "verification_status": "not_verified"
    }
  ],
  "professional_development": [
    {
      "title": "Distributed systems design studio",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2023,
      "learning_focus": "Angular and nestjs in the context of full-stack developer work.",
      "application": "Used reflective exercises and a bounded practice example related to service operations workspace.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    },
    {
      "title": "Secure application delivery workshop",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2024,
      "learning_focus": "React and typescript in the context of full-stack developer work.",
      "application": "Used reflective exercises and a bounded practice example related to customer onboarding flow.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    },
    {
      "title": "Accessible interface review",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2025,
      "learning_focus": "Node.js and postgresql in the context of full-stack developer work.",
      "application": "Used reflective exercises and a bounded practice example related to inventory event dashboard.",
      "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": "API boundaries, recovery behaviour, access control and release ownership are documented with each work 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 angular and nestjs for colleagues. Separated personal preferences from agreed team procedures and recorded useful questions."
    },
    {
      "title": "Review and handover discipline",
      "description": "Facilitated practical reviews of customer onboarding flow, 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": [
    "Angular",
    "React",
    "Node.js",
    "NestJS",
    "TypeScript",
    "PostgreSQL",
    "Docker",
    "CI/CD",
    "Full-Stack Developer",
    "Software & Application Development"
  ]
}