{
  "metadata": {
    "schema_version": "1.0.0",
    "profile_id": "01-01",
    "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": 1,
      "role_title": "Software Engineer"
    },
    "publishing": {
      "search_indexing": false,
      "external_contact_enabled": false,
      "real_credentials_required_before_publication": true
    }
  },
  "basics": {
    "name": "Aarav Mehta",
    "headline": "Software Engineer",
    "specialisation": "TypeScript, Java, Python",
    "location": {
      "city": "Bengaluru",
      "country": "India"
    },
    "contact": {
      "email": "aarav.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": [
    "Software Engineer with an illustrative 13-year career in product engineering and enterprise applications. Combines typescript, java, python 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 order orchestration service, developer release workbench and account permissions refactor. These examples explain the original problem, individual contribution, deliverables, review approach and remaining limitations rather than relying on unsupported headline claims.",
    "Prepared for experienced software engineer opportunities requiring dependable delivery, thoughtful professional judgement and collaboration. The qualification narrative includes M.Tech in Software Engineering. 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 typescript and java, record the evidence and explain the limitations before handover.",
  "core_competencies": [
    {
      "name": "TypeScript",
      "level": "advanced practice - illustrative",
      "application": "Applied to order orchestration service through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "Java",
      "level": "advanced practice - illustrative",
      "application": "Applied to developer release workbench through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "Python",
      "level": "advanced practice - illustrative",
      "application": "Applied to account permissions refactor through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "API design",
      "level": "advanced practice - illustrative",
      "application": "Applied to order orchestration service through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "PostgreSQL",
      "level": "advanced practice - illustrative",
      "application": "Applied to developer release workbench through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "Git",
      "level": "advanced practice - illustrative",
      "application": "Applied to account permissions refactor through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "Docker",
      "level": "advanced practice - illustrative",
      "application": "Applied to order orchestration service through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "automated testing",
      "level": "advanced practice - illustrative",
      "application": "Applied to developer release workbench 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": [
      "TypeScript",
      "Java",
      "Python",
      "API design",
      "PostgreSQL",
      "Git",
      "Docker",
      "automated testing"
    ],
    "professional_scope": "The sample focuses on typescript, java, python. 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": "Order orchestration service",
      "category": "TypeScript",
      "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": "Duplicate events produced inconsistent order states.",
      "objective": "Create a workable response to this issue through typescript, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Software Engineer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Designed idempotent handlers and reconciled order transitions with integration tests.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used typescript to turn the brief into a sequenced work package.",
        "Applied java and python 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": [
        "TypeScript",
        "Java",
        "Python",
        "API design"
      ],
      "deliverables": [
        "Order orchestration service - scoped brief",
        "Order orchestration service - reviewed working package",
        "Order orchestration service - 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 order orchestration service, 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": "Order orchestration service: architecture decision record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.2",
          "title": "Order orchestration service: reviewed pull-request summary",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.3",
          "title": "Order orchestration service: 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": "Developer release workbench",
      "category": "Java",
      "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": "Engineers followed inconsistent release steps.",
      "objective": "Create a workable response to this issue through java, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Software Engineer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Built a versioned release checklist and service health checks.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used python to turn the brief into a sequenced work package.",
        "Applied api design and postgresql 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": [
        "Java",
        "Python",
        "API design",
        "PostgreSQL"
      ],
      "deliverables": [
        "Developer release workbench - scoped brief",
        "Developer release workbench - reviewed working package",
        "Developer release workbench - 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 developer release workbench, 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": "Developer release workbench: architecture decision record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.2",
          "title": "Developer release workbench: reviewed pull-request summary",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.3",
          "title": "Developer release workbench: 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": "Account permissions refactor",
      "category": "Python",
      "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": "Permissions were duplicated across modules.",
      "objective": "Create a workable response to this issue through python, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Software Engineer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Centralised policy evaluation and added negative-access tests.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used postgresql to turn the brief into a sequenced work package.",
        "Applied git 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": [
        "Python",
        "API design",
        "PostgreSQL",
        "Git"
      ],
      "deliverables": [
        "Account permissions refactor - scoped brief",
        "Account permissions refactor - reviewed working package",
        "Account permissions refactor - 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 account permissions refactor, 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": "Account permissions refactor: architecture decision record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.2",
          "title": "Account permissions refactor: reviewed pull-request summary",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.3",
          "title": "Account permissions refactor: 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": "Software Engineer",
      "career_level": "experienced specialist / workstream owner",
      "organisation": "Meridian Digital Systems (fictional)",
      "location": "Bengaluru, India",
      "start_date": "2022-07-01",
      "end_date": null,
      "employment_type": "full-time - fictional record",
      "scope": "Independent ownership of scoped software engineer work, coordinating contributors and making review requirements explicit. Includes the first two selected work examples.",
      "responsibilities": [
        "Designed idempotent handlers and reconciled order transitions with integration tests.",
        "Built a versioned release checklist and service health checks.",
        "Led brief clarification and prioritised work using typescript, java and python. 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 api design 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 Software Engineer",
      "career_level": "senior specialist",
      "organisation": "Northline Digital Systems (fictional)",
      "location": "Bengaluru, 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 python and api design.",
      "responsibilities": [
        "Centralised policy evaluation and added negative-access tests.",
        "Translated incoming requirements into a sequenced plan and aligned responsibilities with the project or service owner.",
        "Applied postgresql and git 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": "Software Engineer",
      "career_level": "independent practitioner",
      "organisation": "Cedarbridge Digital Systems (fictional)",
      "location": "Bengaluru, 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 typescript and java using a documented preparation and review process.",
        "Supported developer release workbench 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": "Associate Software Engineer",
      "career_level": "foundation",
      "organisation": "Cedarbridge Digital Systems (fictional)",
      "location": "Bengaluru, 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 typescript and python 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": "Order orchestration service",
      "description": "Designed idempotent handlers and reconciled order transitions with integration tests. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P1",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Developer release workbench",
      "description": "Built a versioned release checklist and service health checks. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P2",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Account permissions refactor",
      "description": "Centralised policy evaluation and added negative-access tests. 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 Engineering",
      "institution": "Asterbridge Institute of Professional Studies (fictional institution)",
      "start_date": "2011-07-01",
      "end_date": "2013-05-31",
      "status": "completed - fictional record",
      "focus": [
        "TypeScript",
        "Java",
        "API design"
      ],
      "capstone": "Specialist study on order orchestration service; 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": [
        "Python",
        "PostgreSQL",
        "Git"
      ],
      "capstone": "Applied coursework in typescript, 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": "Typescript and api design in the context of software engineer work.",
      "application": "Used reflective exercises and a bounded practice example related to order orchestration service.",
      "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": "Java and postgresql in the context of software engineer work.",
      "application": "Used reflective exercises and a bounded practice example related to developer release workbench.",
      "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": "Python and git in the context of software engineer work.",
      "application": "Used reflective exercises and a bounded practice example related to account permissions refactor.",
      "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 typescript and api design for colleagues. Separated personal preferences from agreed team procedures and recorded useful questions."
    },
    {
      "title": "Review and handover discipline",
      "description": "Facilitated practical reviews of developer release workbench, 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": [
    "TypeScript",
    "Java",
    "Python",
    "API design",
    "PostgreSQL",
    "Git",
    "Docker",
    "automated testing",
    "Software Engineer",
    "Software & Application Development"
  ]
}