{
  "metadata": {
    "schema_version": "1.0.0",
    "profile_id": "04-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": 4,
      "name": "Software Testing & Quality",
      "role_index": 1,
      "role_title": "Software Tester"
    },
    "publishing": {
      "search_indexing": false,
      "external_contact_enabled": false,
      "real_credentials_required_before_publication": true
    }
  },
  "basics": {
    "name": "Ishan Mehta",
    "headline": "Software Tester",
    "specialisation": "exploratory testing, test cases, defect reporting",
    "location": {
      "city": "Jaipur",
      "country": "India"
    },
    "contact": {
      "email": "ishan.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 Tester with an illustrative 13-year career in software quality engineering and release assurance. Combines exploratory testing, test cases, defect reporting 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 subscription journey review, cross-browser acceptance suite and test data catalogue. 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 tester opportunities requiring dependable delivery, thoughtful professional judgement and collaboration. The qualification narrative includes Postgraduate diploma in Software Quality. Every named organisation and outcome in this record is fictional; professional eligibility is not independently established."
  ],
  "professional_mission": "Turn a clear brief into dependable software quality engineering and release assurance work: understand the context, apply exploratory testing and test cases, record the evidence and explain the limitations before handover.",
  "core_competencies": [
    {
      "name": "exploratory testing",
      "level": "advanced practice - illustrative",
      "application": "Applied to subscription journey review through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "test cases",
      "level": "advanced practice - illustrative",
      "application": "Applied to cross-browser acceptance suite through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "defect reporting",
      "level": "advanced practice - illustrative",
      "application": "Applied to test data catalogue through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "API checks",
      "level": "advanced practice - illustrative",
      "application": "Applied to subscription journey review through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "SQL",
      "level": "advanced practice - illustrative",
      "application": "Applied to cross-browser acceptance suite through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "browser testing",
      "level": "advanced practice - illustrative",
      "application": "Applied to test data catalogue through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "requirements review",
      "level": "advanced practice - illustrative",
      "application": "Applied to subscription journey review through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "release validation",
      "level": "advanced practice - illustrative",
      "application": "Applied to cross-browser acceptance suite through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    }
  ],
  "specialist_practice": {
    "title": "Quality evidence",
    "summary": "Results refer to a bounded sample system and test window, not a guarantee of defect-free software.",
    "working_principles": [
      "Convert acceptance criteria into risk-based tests with observable expected results.",
      "Keep representative test data separate from confidential production records.",
      "Explain coverage limits and residual risks rather than claiming that testing proves perfection."
    ],
    "tools_and_methods": [
      "exploratory testing",
      "test cases",
      "defect reporting",
      "API checks",
      "SQL",
      "browser testing",
      "requirements review",
      "release validation"
    ],
    "professional_scope": "The sample focuses on exploratory testing, test cases, defect reporting. 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": "Subscription journey review",
      "category": "exploratory testing",
      "organisation": "Meridian Quality Engineering (fictional)",
      "employment_id": "EXP-4",
      "start_date": "2023-01-01",
      "end_date": "2023-06-30",
      "project_context": "Fictional internal work programme in software quality engineering and release assurance; not a real client case study.",
      "problem": "Renewal edge cases were not specified.",
      "objective": "Create a workable response to this issue through exploratory testing, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Software Tester; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Mapped state transitions and reproduced billing-flow defects.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used exploratory testing to turn the brief into a sequenced work package.",
        "Applied test cases and defect reporting 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": [
        "exploratory testing",
        "test cases",
        "defect reporting",
        "API checks"
      ],
      "deliverables": [
        "Subscription journey review - scoped brief",
        "Subscription journey review - reviewed working package",
        "Subscription journey 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 test strategy and coverage map and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for subscription journey 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. Results refer to a bounded sample system and test window, not a guarantee of defect-free software. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E1.1",
          "title": "Subscription journey review: test strategy and coverage map",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.2",
          "title": "Subscription journey review: defect reproduction record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.3",
          "title": "Subscription journey review: release-readiness assessment",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    },
    {
      "id": "P2",
      "title": "Cross-browser acceptance suite",
      "category": "test cases",
      "organisation": "Meridian Quality Engineering (fictional)",
      "employment_id": "EXP-4",
      "start_date": "2024-01-01",
      "end_date": "2024-06-30",
      "project_context": "Fictional internal work programme in software quality engineering and release assurance; not a real client case study.",
      "problem": "Critical forms behaved differently across browsers.",
      "objective": "Create a workable response to this issue through test cases, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Software Tester; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Built a supported-browser matrix and repeatable scenarios.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used defect reporting to turn the brief into a sequenced work package.",
        "Applied api checks and sql 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": [
        "test cases",
        "defect reporting",
        "API checks",
        "SQL"
      ],
      "deliverables": [
        "Cross-browser acceptance suite - scoped brief",
        "Cross-browser acceptance suite - reviewed working package",
        "Cross-browser acceptance suite - 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 defect reproduction record and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for cross-browser acceptance suite, 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. Results refer to a bounded sample system and test window, not a guarantee of defect-free software. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E2.1",
          "title": "Cross-browser acceptance suite: test strategy and coverage map",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.2",
          "title": "Cross-browser acceptance suite: defect reproduction record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.3",
          "title": "Cross-browser acceptance suite: release-readiness assessment",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    },
    {
      "id": "P3",
      "title": "Test data catalogue",
      "category": "defect reporting",
      "organisation": "Northline Quality Engineering (fictional)",
      "employment_id": "EXP-3",
      "start_date": "2019-01-01",
      "end_date": "2019-06-30",
      "project_context": "Fictional internal work programme in software quality engineering and release assurance; not a real client case study.",
      "problem": "Shared accounts caused inconsistent test results.",
      "objective": "Create a workable response to this issue through defect reporting, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Software Tester; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Created isolated personas and reset instructions.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used sql to turn the brief into a sequenced work package.",
        "Applied browser testing and requirements review 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": [
        "defect reporting",
        "API checks",
        "SQL",
        "browser testing"
      ],
      "deliverables": [
        "Test data catalogue - scoped brief",
        "Test data catalogue - reviewed working package",
        "Test data catalogue - 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 release-readiness assessment and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for test data catalogue, 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. Results refer to a bounded sample system and test window, not a guarantee of defect-free software. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E3.1",
          "title": "Test data catalogue: test strategy and coverage map",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.2",
          "title": "Test data catalogue: defect reproduction record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.3",
          "title": "Test data catalogue: release-readiness assessment",
          "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 Tester",
      "career_level": "experienced specialist / workstream owner",
      "organisation": "Meridian Quality Engineering (fictional)",
      "location": "Jaipur, India",
      "start_date": "2022-07-01",
      "end_date": null,
      "employment_type": "full-time - fictional record",
      "scope": "Independent ownership of scoped software tester work, coordinating contributors and making review requirements explicit. Includes the first two selected work examples.",
      "responsibilities": [
        "Mapped state transitions and reproduced billing-flow defects.",
        "Built a supported-browser matrix and repeatable scenarios.",
        "Led brief clarification and prioritised work using exploratory testing, test cases and defect reporting. Raised unresolved constraints before committing to the next stage.",
        "Coordinated peer reviews and handover preparation; used a test strategy and coverage map to distinguish completed work, assumptions and follow-up needs.",
        "Supported colleagues with practical examples of api checks 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 Tester",
      "career_level": "senior specialist",
      "organisation": "Northline Quality Engineering (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 defect reporting and api checks.",
      "responsibilities": [
        "Created isolated personas and reset instructions.",
        "Translated incoming requirements into a sequenced plan and aligned responsibilities with the project or service owner.",
        "Applied sql and browser testing 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 release-readiness assessment 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 Tester",
      "career_level": "independent practitioner",
      "organisation": "Cedarbridge Quality Engineering (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 exploratory testing and test cases using a documented preparation and review process.",
        "Supported cross-browser acceptance suite 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 requirements review 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 Software Tester",
      "career_level": "foundation",
      "organisation": "Cedarbridge Quality Engineering (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 exploratory testing and defect reporting 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": "Subscription journey review",
      "description": "Mapped state transitions and reproduced billing-flow defects. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P1",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Cross-browser acceptance suite",
      "description": "Built a supported-browser matrix and repeatable scenarios. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P2",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Test data catalogue",
      "description": "Created isolated personas and reset instructions. 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": "Postgraduate diploma in Software Quality",
      "institution": "Asterbridge Institute of Professional Studies (fictional institution)",
      "start_date": "2012-07-01",
      "end_date": "2013-05-31",
      "status": "completed - fictional record",
      "focus": [
        "exploratory testing",
        "test cases",
        "API checks"
      ],
      "capstone": "Specialist study on subscription journey review; an illustrative learning project, not a published result.",
      "verification_status": "not_verified"
    },
    {
      "id": "EDU-1",
      "qualification": "B.Sc in Computer Science",
      "institution": "Cedarhaven College of Applied Studies (fictional institution)",
      "start_date": "2009-07-01",
      "end_date": "2012-05-31",
      "status": "completed - fictional record",
      "focus": [
        "defect reporting",
        "SQL",
        "browser testing"
      ],
      "capstone": "Applied coursework in exploratory testing, documentation and reviewed practical assignments.",
      "verification_status": "not_verified"
    }
  ],
  "professional_development": [
    {
      "title": "Risk-based testing workshop",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2023,
      "learning_focus": "Exploratory testing and api checks in the context of software tester work.",
      "application": "Used reflective exercises and a bounded practice example related to subscription journey review.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    },
    {
      "title": "Test-data design practicum",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2024,
      "learning_focus": "Test cases and sql in the context of software tester work.",
      "application": "Used reflective exercises and a bounded practice example related to cross-browser acceptance suite.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    },
    {
      "title": "Defect communication clinic",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2025,
      "learning_focus": "Defect reporting and browser testing in the context of software tester work.",
      "application": "Used reflective exercises and a bounded practice example related to test data catalogue.",
      "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": "Results refer to a bounded sample system and test window, not a guarantee of defect-free software.",
    "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 exploratory testing and api checks for colleagues. Separated personal preferences from agreed team procedures and recorded useful questions."
    },
    {
      "title": "Review and handover discipline",
      "description": "Facilitated practical reviews of cross-browser acceptance suite, 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": [
    "exploratory testing",
    "test cases",
    "defect reporting",
    "API checks",
    "SQL",
    "browser testing",
    "requirements review",
    "release validation",
    "Software Tester",
    "Software Testing & Quality"
  ]
}