{
  "metadata": {
    "schema_version": "1.0.0",
    "profile_id": "03-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": 3,
      "name": "Cloud, IT Infrastructure & Cybersecurity",
      "role_index": 1,
      "role_title": "Cloud Engineer"
    },
    "publishing": {
      "search_indexing": false,
      "external_contact_enabled": false,
      "real_credentials_required_before_publication": true
    }
  },
  "basics": {
    "name": "Dev Mehta",
    "headline": "Cloud Engineer",
    "specialisation": "AWS, Azure, Terraform",
    "location": {
      "city": "Ahmedabad",
      "country": "India"
    },
    "contact": {
      "email": "dev.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": [
    "Cloud Engineer with an illustrative 13-year career in enterprise technology operations and infrastructure. Combines aws, azure, terraform 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 governed cloud foundation, backup recovery exercise and cloud cost visibility. These examples explain the original problem, individual contribution, deliverables, review approach and remaining limitations rather than relying on unsupported headline claims.",
    "Prepared for experienced cloud engineer opportunities requiring dependable delivery, thoughtful professional judgement and collaboration. The qualification narrative includes M.Tech in Cloud Computing. Every named organisation and outcome in this record is fictional; professional eligibility is not independently established."
  ],
  "professional_mission": "Turn a clear brief into dependable enterprise technology operations and infrastructure work: understand the context, apply aws and azure, record the evidence and explain the limitations before handover.",
  "core_competencies": [
    {
      "name": "AWS",
      "level": "advanced practice - illustrative",
      "application": "Applied to governed cloud foundation through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "Azure",
      "level": "advanced practice - illustrative",
      "application": "Applied to backup recovery exercise through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "Terraform",
      "level": "advanced practice - illustrative",
      "application": "Applied to cloud cost visibility through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "networking",
      "level": "advanced practice - illustrative",
      "application": "Applied to governed cloud foundation through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "identity management",
      "level": "advanced practice - illustrative",
      "application": "Applied to backup recovery exercise through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    },
    {
      "name": "Linux",
      "level": "advanced practice - illustrative",
      "application": "Applied to cloud cost visibility through documented preparation, execution and review.",
      "evidence_project_id": "P3"
    },
    {
      "name": "monitoring",
      "level": "advanced practice - illustrative",
      "application": "Applied to governed cloud foundation through documented preparation, execution and review.",
      "evidence_project_id": "P1"
    },
    {
      "name": "cost allocation",
      "level": "advanced practice - illustrative",
      "application": "Applied to backup recovery exercise through documented preparation, execution and review.",
      "evidence_project_id": "P2"
    }
  ],
  "specialist_practice": {
    "title": "Operational safeguards",
    "summary": "Testing is performed in authorised environments; security examples contain no real secrets or exploit instructions.",
    "working_principles": [
      "Map dependencies, permissions and ownership before changing a live environment.",
      "Use change windows, peer review and tested recovery paths for operational work.",
      "Record service observations, exceptions and follow-up without exposing credentials."
    ],
    "tools_and_methods": [
      "AWS",
      "Azure",
      "Terraform",
      "networking",
      "identity management",
      "Linux",
      "monitoring",
      "cost allocation"
    ],
    "professional_scope": "The sample focuses on aws, azure, terraform. 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": "Governed cloud foundation",
      "category": "AWS",
      "organisation": "Meridian Technology Operations (fictional)",
      "employment_id": "EXP-4",
      "start_date": "2023-01-01",
      "end_date": "2023-06-30",
      "project_context": "Fictional internal work programme in enterprise technology operations and infrastructure; not a real client case study.",
      "problem": "Teams provisioned inconsistent isolated environments.",
      "objective": "Create a workable response to this issue through aws, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Cloud Engineer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Created reusable network and identity modules with review gates.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used aws to turn the brief into a sequenced work package.",
        "Applied azure and terraform 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": [
        "AWS",
        "Azure",
        "Terraform",
        "networking"
      ],
      "deliverables": [
        "Governed cloud foundation - scoped brief",
        "Governed cloud foundation - reviewed working package",
        "Governed cloud foundation - 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 sanitised configuration review and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for governed cloud foundation, 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. Testing is performed in authorised environments; security examples contain no real secrets or exploit instructions. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E1.1",
          "title": "Governed cloud foundation: sanitised configuration review",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.2",
          "title": "Governed cloud foundation: change and rollback record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E1.3",
          "title": "Governed cloud foundation: incident learning summary",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    },
    {
      "id": "P2",
      "title": "Backup recovery exercise",
      "category": "Azure",
      "organisation": "Meridian Technology Operations (fictional)",
      "employment_id": "EXP-4",
      "start_date": "2024-01-01",
      "end_date": "2024-06-30",
      "project_context": "Fictional internal work programme in enterprise technology operations and infrastructure; not a real client case study.",
      "problem": "Recovery assumptions had not been tested.",
      "objective": "Create a workable response to this issue through azure, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Cloud Engineer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Documented restore dependencies and rehearsed a representative recovery.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used terraform to turn the brief into a sequenced work package.",
        "Applied networking and identity management 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": [
        "Azure",
        "Terraform",
        "networking",
        "identity management"
      ],
      "deliverables": [
        "Backup recovery exercise - scoped brief",
        "Backup recovery exercise - reviewed working package",
        "Backup recovery exercise - 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 change and rollback record and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for backup recovery exercise, 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. Testing is performed in authorised environments; security examples contain no real secrets or exploit instructions. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E2.1",
          "title": "Backup recovery exercise: sanitised configuration review",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.2",
          "title": "Backup recovery exercise: change and rollback record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E2.3",
          "title": "Backup recovery exercise: incident learning summary",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        }
      ],
      "verification_status": "not_verified"
    },
    {
      "id": "P3",
      "title": "Cloud cost visibility",
      "category": "Terraform",
      "organisation": "Northline Technology Operations (fictional)",
      "employment_id": "EXP-3",
      "start_date": "2019-01-01",
      "end_date": "2019-06-30",
      "project_context": "Fictional internal work programme in enterprise technology operations and infrastructure; not a real client case study.",
      "problem": "Shared resource bills lacked service ownership.",
      "objective": "Create a workable response to this issue through terraform, explicit review criteria and practical documentation. Agree the boundaries before execution and retain unresolved points for follow-up.",
      "role_and_ownership": "Cloud Engineer; owned the stated workstream, not the full organisation or every collaborator contribution.",
      "contribution": [
        "Implemented tagging checks and owner-level cost views.",
        "Prepared the scope with the commissioning team, identified unresolved inputs and used identity management to turn the brief into a sequenced work package.",
        "Applied linux and monitoring 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": [
        "Terraform",
        "networking",
        "identity management",
        "Linux"
      ],
      "deliverables": [
        "Cloud cost visibility - scoped brief",
        "Cloud cost visibility - reviewed working package",
        "Cloud cost visibility - 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 incident learning summary and a named human reviewer.",
      "outcomes": [
        "Illustrative outcome: the team adopted a repeatable approach for cloud cost visibility, 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. Testing is performed in authorised environments; security examples contain no real secrets or exploit instructions. No underlying client documents, independently verified measurements or signed approval records are attached.",
      "evidence": [
        {
          "id": "E3.1",
          "title": "Cloud cost visibility: sanitised configuration review",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.2",
          "title": "Cloud cost visibility: change and rollback record",
          "type": "suggested_supporting_artifact",
          "status": "not_supplied",
          "url": null,
          "publication_permission": "not_applicable_to_synthetic_sample"
        },
        {
          "id": "E3.3",
          "title": "Cloud cost visibility: incident learning summary",
          "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": "Cloud Engineer",
      "career_level": "experienced specialist / workstream owner",
      "organisation": "Meridian Technology Operations (fictional)",
      "location": "Ahmedabad, India",
      "start_date": "2022-07-01",
      "end_date": null,
      "employment_type": "full-time - fictional record",
      "scope": "Independent ownership of scoped cloud engineer work, coordinating contributors and making review requirements explicit. Includes the first two selected work examples.",
      "responsibilities": [
        "Created reusable network and identity modules with review gates.",
        "Documented restore dependencies and rehearsed a representative recovery.",
        "Led brief clarification and prioritised work using aws, azure and terraform. Raised unresolved constraints before committing to the next stage.",
        "Coordinated peer reviews and handover preparation; used a sanitised configuration review to distinguish completed work, assumptions and follow-up needs.",
        "Supported colleagues with practical examples of networking 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 Cloud Engineer",
      "career_level": "senior specialist",
      "organisation": "Northline Technology Operations (fictional)",
      "location": "Ahmedabad, 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 terraform and networking.",
      "responsibilities": [
        "Implemented tagging checks and owner-level cost views.",
        "Translated incoming requirements into a sequenced plan and aligned responsibilities with the project or service owner.",
        "Applied identity management and linux 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 incident learning summary 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": "Cloud Engineer",
      "career_level": "independent practitioner",
      "organisation": "Cedarbridge Technology Operations (fictional)",
      "location": "Ahmedabad, 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 aws and azure using a documented preparation and review process.",
        "Supported backup recovery exercise 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 monitoring 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 Cloud Engineer",
      "career_level": "foundation",
      "organisation": "Cedarbridge Technology Operations (fictional)",
      "location": "Ahmedabad, 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 aws and terraform 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": "Governed cloud foundation",
      "description": "Created reusable network and identity modules with review gates. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P1",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Backup recovery exercise",
      "description": "Documented restore dependencies and rehearsed a representative recovery. The achievement is the described workstream contribution; independent outcome evidence is not supplied.",
      "project_id": "P2",
      "verification_status": "not_verified",
      "metrics": []
    },
    {
      "title": "Cloud cost visibility",
      "description": "Implemented tagging checks and owner-level cost views. 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 Cloud Computing",
      "institution": "Asterbridge Institute of Professional Studies (fictional institution)",
      "start_date": "2011-07-01",
      "end_date": "2013-05-31",
      "status": "completed - fictional record",
      "focus": [
        "AWS",
        "Azure",
        "networking"
      ],
      "capstone": "Specialist study on governed cloud foundation; an illustrative learning project, not a published result.",
      "verification_status": "not_verified"
    },
    {
      "id": "EDU-1",
      "qualification": "B.Tech in Information Technology",
      "institution": "Cedarhaven College of Applied Studies (fictional institution)",
      "start_date": "2007-07-01",
      "end_date": "2011-05-31",
      "status": "completed - fictional record",
      "focus": [
        "Terraform",
        "identity management",
        "Linux"
      ],
      "capstone": "Applied coursework in aws, documentation and reviewed practical assignments.",
      "verification_status": "not_verified"
    }
  ],
  "professional_development": [
    {
      "title": "Incident response exercise",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2023,
      "learning_focus": "Aws and networking in the context of cloud engineer work.",
      "application": "Used reflective exercises and a bounded practice example related to governed cloud foundation.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    },
    {
      "title": "Infrastructure change-control lab",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2024,
      "learning_focus": "Azure and identity management in the context of cloud engineer work.",
      "application": "Used reflective exercises and a bounded practice example related to backup recovery exercise.",
      "type": "continuing learning - not a licence or certification",
      "verification_status": "not_verified"
    },
    {
      "title": "Access review workshop",
      "provider": "Meridian Professional Learning Studio (fictional)",
      "year": 2025,
      "learning_focus": "Terraform and linux in the context of cloud engineer work.",
      "application": "Used reflective exercises and a bounded practice example related to cloud cost visibility.",
      "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": "Testing is performed in authorised environments; security examples contain no real secrets or exploit instructions.",
    "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 aws and networking for colleagues. Separated personal preferences from agreed team procedures and recorded useful questions."
    },
    {
      "title": "Review and handover discipline",
      "description": "Facilitated practical reviews of backup recovery exercise, 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": [
    "AWS",
    "Azure",
    "Terraform",
    "networking",
    "identity management",
    "Linux",
    "monitoring",
    "cost allocation",
    "Cloud Engineer",
    "Cloud, IT Infrastructure & Cybersecurity"
  ]
}