Build Your Cybersecurity Career Kit

Create a GitHub and LinkedIn career kit for an infrastructure-to-security path.

Introduction

30 Second Summary

Recruiters often meet your online profile before they meet you. If each profile tells a different story, your career direction becomes hard to understand.

In this project, you will build a career launch kit across GitHub, LinkedIn, and two focused documents. It connects an India-first infrastructure support target to a longer-term information security goal in the United States.

What You'll Build

When a recruiter opens your finished profiles, they see one consistent story covering your degree, immediate role target, long-term direction, current evidence, and next proof projects.

By the end of this project, you'll have:

A public GitHub introduction that shows your exact degree wording, immediate infrastructure-support target, current learning focus, and longer-term security direction.
A 12-week evidence plan in career-gap.md that turns networking, Windows troubleshooting, Linux, ticket documentation, cloud identity, and security gaps into an ordered build sequence.
An evidence-first professional story across resume-draft.md and LinkedIn that includes only skills or achievements you can support with coursework or visible work.
Secret Mission: Turn your profile README into a portfolio dashboard that links your career plan, resume draft, and next proof projects.

Are there any prerequisites?

You need a Windows laptop, internet access, plus existing GitHub and LinkedIn accounts that you own. The first step confirms that Microsoft Edge is current before you start editing your professional profiles.

Before We Start

Before the hands-on work begins, lock in the career path you are building and why it matters to you. This commitment keeps every profile update and evidence project focused on the same destination.

Verify Your Browser and Accounts

Your career launch kit lives on public profiles. A browser-only workflow gets you to a visible result without command-line setup.

Microsoft Edge gives you one workspace for GitHub. A separate tab keeps LinkedIn ready beside it.

In this step, get ready to:

Confirm Microsoft Edge is ready for the workflow.
Open the GitHub account you confirmed you own.
Open your LinkedIn profile in a separate tab.

Verify Microsoft Edge

Windows Start reveals whether Microsoft Edge is already installed. Once the browser opens, its update page confirms whether it is current.

Press the Windows key to open Windows Start.
Type Microsoft Edge into the search field.

The search results show whether Microsoft Edge is available on your laptop.

✔️ Microsoft Edge is listed

Select Microsoft Edge from the search results.

Microsoft Edge opens in a browser window.

ⓧ Microsoft Edge is missing

Microsoft provides the Windows installer through its official download page.

Use your available browser to visit the official Microsoft Edge download page.
Select the Windows download offered on the page.

The installer downloads through your available browser.

Open the downloaded installer from your browser's downloads area.
Approve the Windows installation prompt if it appears.

The installation adds Microsoft Edge to Windows Start.

Press the Windows key to return to Windows Start.
Type Microsoft Edge into the search field.

Microsoft Edge now appears in the search results.

Select Microsoft Edge from the search results.

Microsoft Edge opens in a browser window.

The dedicated update page checks the browser installation. It also completes any available update.

Enter edge://settings/help in the Microsoft Edge address bar.
Press Enter.

You'll see Microsoft Edge check its current installation.

Follow any update prompt shown on the page.
Keep the page open until Microsoft Edge reports that it is current.

Your browser is now ready to carry the complete career workflow.

Edge still not reporting current?

The browser menu reaches the same update page:

Select Settings and more in Microsoft Edge.
Select Help and feedback.
Select About Microsoft Edge.

If the update check remains blocked, help me troubleshoot why Microsoft Edge is not reporting that it is current.

Open your GitHub profile

The account check protects your future work from landing on the wrong profile. Your existing credentials only restore access to the account you already own.

Select the plus button in the Microsoft Edge tab bar to create a separate tab.
Visit the GitHub website.

You'll see either GitHub's signed-in home page or its sign-in page.

GitHub now shows its signed-in interface for that account.

Select your profile picture in the top-right corner.
Select Your profile.
Confirm the profile identifies the GitHub account you own.

Your confirmed GitHub profile is now open in its own tab.

Profile does not match your account?

Use the account menu to sign out of the incorrect account.
Sign in again with the GitHub account you confirmed you own.

If the profile still looks unfamiliar, help me verify that I opened the correct GitHub account.

Open your LinkedIn profile

Your LinkedIn profile is the second public surface in the career launch kit. Opening it now confirms that the correct professional account is ready.

Select the plus button in the Microsoft Edge tab bar to create another tab.
Visit the LinkedIn website.

You'll see either LinkedIn's signed-in home page or its sign-in page.

Sign in to the LinkedIn account you confirmed you own if LinkedIn asks.
Select Me in the top navigation.
Select View Profile.
Confirm the profile identifies the LinkedIn account you own.

Before you make the final check, do you expect Edge to report that it is current while both confirmed profile tabs remain open?

Switch back to the Microsoft Edge update tab from earlier.
Confirm Microsoft Edge reports that it is current.
Switch back to the GitHub profile tab.
Confirm your signed-in GitHub profile remains open.
Switch back to the LinkedIn profile tab.
Confirm your View Profile page remains open.

You can now see all three readiness signals. Your current browser has the correct GitHub profile plus the correct LinkedIn profile ready in separate tabs.

LinkedIn profile not opening?

Confirm that you signed in with the LinkedIn account you already own. Return to the top navigation after the sign-in flow completes.

If View Profile still does not open your profile, help me troubleshoot my LinkedIn profile access.

Your browser workspace is ready. Next, you'll turn your GitHub profile into the first visible piece of your career launch kit.

Publish Your Career Baseline

Your browser and accounts are ready. Your career direction still lives outside your public profile.

A recruiter opening your GitHub profile needs a clear introduction to understand your direction. Publishing this baseline gives you an early result that you can evaluate from a recruiter's perspective.

In this step, get ready to:

Create a public repository for your profile README.
Write a truthful introduction using your exact certificate wording.
Verify that the README appears at the top of your public profile.

Create your profile repository

A profile README uses a repository whose name matches your username. The repository must be public with a populated README.md file at its top level.

Keep the baseline public-safe

Anyone can read a public repository. Include only professional information you are comfortable publishing.

Keep private contact details, identity documents, passwords, API keys, and certificate scans out of the repository. Copy only the degree wording from your certificate.

Identify your username in the address of the GitHub profile tab from earlier.
Record the username here: YOUR_GITHUB_USERNAME.
Select New repository.
Enter YOUR_GITHUB_USERNAME in the Repository name field.
Select Public.
Turn Add README on.
Click Create repository.

Good progress. Your username-matched public repository now contains the file GitHub needs for a profile README.

Repository not created?

Compare the repository name with the username in your profile address. Make sure you selected your confirmed account before creating the repository.

If GitHub reports a problem with the name, check whether that repository already exists under your account. Help me check my profile repository setup.

Write your baseline introduction

Your README becomes a public professional statement. Every claim should match a certificate, academic record, or current learning activity that you can explain honestly.

What belongs in the introduction?

Your degree uses the exact wording printed on your certificate.
Your immediate target names NOC, network, infrastructure, or data-center support.
Your long-term target names information security.
Your current learning focus names the practical skills you are actively developing.

Click Edit README.

You should see the README editor containing the starter content.

Select the starter content in the README editor.
Replace it with a short introduction that follows the four points above.
Click Preview.

You should see a readable introduction with your degree wording, immediate target, long-term target, and current learning focus.

Does the preview look incomplete?

Return to the editor if one of the four points is missing. Compare the degree wording directly with your certificate before correcting it.

Keep each claim short enough to explain in a conversation. Help me review my career introduction for unsupported claims.

Commit and inspect your README

The preview shows how the introduction renders. A commit records the version that visitors can read from your repository.

Compare the degree wording with your certificate.
Confirm that the immediate target names one infrastructure-support role family.
Confirm that the long-term target names information security.
Confirm that the learning focus describes work you are doing now.
Click Commit changes... to open the commit dialog.

GitHub opens a dialog where you can describe this saved version.

Enter Publish career baseline in the commit message box.
Click Commit changes.

That is your first public career artifact published. The repository now shows the committed README.

Before you inspect the published page, what do you think a recruiter can verify from this introduction alone?

Open your account menu in the top-right corner of GitHub.
Select Your profile.

You should see the new README at the top of your public profile. It should show your exact certificate wording, immediate role family, long-term information security target, and current learning focus.

Read the published introduction from a recruiter's perspective.

Your career direction is now clear. Practical networking, Linux, and troubleshooting evidence is still absent from the profile.

README missing from your profile?

Check that the repository name matches your GitHub username exactly. Confirm that the repository is public.

Confirm that the populated file is named README.md at the top level of the repository. Help me diagnose my missing profile README.

Your career baseline is live for recruiters to read. Next, you will turn current role requirements into a 12-week evidence plan that fills the practical gap.

Build Your Evidence Plan

Your public GitHub introduction now tells recruiters where you are heading. The next move turns that direction into evidence you can build.

The profile cannot yet demonstrate the practical skills that infrastructure-support roles demand. An evidence-based skills gap connects each employer requirement to a portfolio artifact.

The plan will expose missing proof for networking, Linux, troubleshooting, and documentation. It will also order that work across 12 weeks.

In this step, get ready to:

Separate the immediate infrastructure-support role from the long-term information security destination.
Map at least four requirements to current evidence, gap status, and proof artifacts.
Order the evidence work into a focused 12-week sequence.

Separate the two role targets

A role ladder keeps your immediate application target separate from your longer-term destination. The immediate role builds hands-on infrastructure evidence that supports a later move into information security.

The AWS India benchmark shows what one current data-center role expects. The U.S. role summaries show how support experience can contribute to a longer career path.

Open the supplied Data Centre Linux & HW Engineer, Data Center Operations benchmark in a new Microsoft Edge tab.
Review the benchmark's basic qualifications to identify the education requirement.
Review the benchmark's basic qualifications to identify the networking experience requirement plus the Linux experience requirement.
Review the listed duties to identify the troubleshooting evidence expected from applicants.
Open the Computer Support Specialists summary in another tab.
Find how support specialists can progress into information security or systems administration roles.
Open the Information Security Analysts summary in another tab.
Compare the two summaries to separate the entry pathway from the longer-term destination.

You should find that the benchmark expects degree alignment plus networking and Linux experience. Its duties also demand ticket resolution plus systems troubleshooting.

The support summary presents infrastructure work as an entry pathway. The analyst summary describes protecting networks and systems as the longer-term destination.

Why use a two-role ladder?

The immediate role gives you a realistic application target based on evidence you can build now. The longer-term role keeps each project connected to your information security direction.

This structure prevents entry-level preparation from becoming a mixed list of unrelated subjects. Every gap must support the next role or the destination beyond it.

Create the skills gap table

A Markdown table places every requirement beside the evidence you can currently show. Empty or weak evidence becomes a specific artifact to build.

Switch back to the profile repository tab from earlier.
Click Add file above the repository file list.
Select Create new file.
Enter career-gap.md in the filename field.
Add Career Evidence Plan as the document title.
Draft a Role Ladder section that names the immediate India-based support role plus the long-term U.S. information security destination.
Select Preview to inspect the opening section.

You should see one document title followed by two clearly separated role targets. This confirms that the plan has a defined starting point plus a defined destination.

Return to the file editor beside the preview.
Create a Skills Gap section with a four-column table headed Requirement, Current evidence, Gap status, and Artifact that proves the skill.
Add at least four rows covering networking, Windows troubleshooting, Linux, ticket documentation, cloud identity, or cloud security.
Select Preview to check the table layout.

You should see four distinct columns with at least four requirement rows. Each row should connect a missing skill to something you can eventually show.

What counts as evidence?

Current evidence is coursework, a completed lab, a document, or another artifact you can show if asked.
Gap status states whether convincing evidence exists today.
The proof artifact is the lab, diagram, ticket write-up, or project that closes the gap.

Table not displaying clearly?

Return to the editor to confirm that every row contains four populated cells.
Remove any empty row that creates an unexpected break in the preview.

If the columns still run together, help me repair this Markdown table.

Order the 12-week evidence plan

A fixed sequence protects your attention from unrelated topics. Each block builds evidence needed by the block that follows it.

Return to the file editor beside the preview.
Add a 12-Week Evidence Plan section.
Create Weeks 1 to 3: Networking and Windows troubleshooting as the first block.
Select Preview to confirm the first block appears beneath the skills gap table.

You should see the plan begin with the troubleshooting foundation expected by infrastructure-support roles.

Return to the file editor beside the preview.
Add Weeks 4 to 6: Linux and ticket documentation as the second block.
Add Weeks 7 to 9: Cloud and identity fundamentals as the third block.
Select Preview to confirm that the three blocks remain in chronological order.

You should see the sequence move from infrastructure troubleshooting into Linux evidence. The next block introduces cloud identity after those foundations.

Return to the file editor beside the preview.
Add Weeks 10 to 12: Cloud-security evidence and targeted applications as the final block.
Add one concrete proof artifact beneath each of the four blocks.

Before you preview the complete plan, do you expect it to read as one progression or as unrelated subjects?

Select Preview to inspect the complete 12-week sequence.

You should see four ordered blocks that progress from networking fundamentals to targeted applications. The sequence now turns every gap into scheduled evidence work.

Click Commit changes....
Enter Add 12-week career evidence plan as the commit message.
Click Commit changes to publish the file.

That is the planning gap closed. Your repository now shows exactly what evidence you have plus what you will build next.

Before you inspect the committed file, do you expect the plan to show a role-led sequence or a mixed list of subjects?

Return to the repository file list.
Open career-gap.md.
Confirm the role ladder separates the immediate India-based support role from the long-term U.S. information security destination.
Count at least four rows in the skills gap table.
Read the four plan blocks from top to bottom.

You should see a two-role ladder plus at least four evidence gaps. The 12-week plan should progress through networking and Windows troubleshooting, Linux and ticket documentation, cloud and identity fundamentals, then cloud-security evidence and targeted applications.

Can't find the committed plan?

Confirm that you committed the file inside the public repository named YOUR_GITHUB_USERNAME. Check that the filename is exactly career-gap.md.

If the file still does not appear, help me find my committed career plan.

Your career direction now has a role ladder plus a build schedule. Next, you will turn the evidence you can already support into an honest resume draft.

Draft an Evidence-First Resume

Your GitHub evidence plan now turns employer requirements into an ordered path. Your resume turns that path into a truthful application story.

A broad resume filled with unproven tools can weaken your applications. This draft separates completed evidence from planned learning so every claim can survive a recruiter's follow-up questions.

In this step, get ready to:

Create a structured resume-draft.md file in your public profile repository.
Separate completed evidence from planned learning.
Publish the reviewed resume draft as a GitHub commit.

Create the resume structure

A Markdown resume is easy to review in a browser. Clear sections also make unsupported claims easier to spot before you publish them.

Switch back to the GitHub profile repository named YOUR_GITHUB_USERNAME from earlier.
Click Add file above the repository file list.
Select Create new file.
Enter resume-draft.md in the filename field.
Add these section headings in order: Contact Details, Target Summary, Education, Evidence-Backed Skills, Selected Projects, and Additional Information.
Select Preview above the file editor.

Good progress. Your preview now shows six clear sections for the resume content you are about to verify.

Can't See the Resume Sections?

Confirm the filename is resume-draft.md. Check that each section heading starts on its own line.

Make sure you are creating the file inside YOUR_GITHUB_USERNAME. Help me check the structure of my Markdown resume draft.

Separate evidence from planned learning

A public resume can feel exposing. Your contact section can stay limited to information you already share professionally.

What Makes a Claim Evidence-Backed?

An evidence-backed claim points to something you can show. Useful sources include your certificate, verified coursework, or a completed GitHub artifact.

Planned labs belong in a future build queue. This keeps your current skills accurate while showing what you are building next.

Return to the file editor.
Enter one recruiter-safe contact method under Contact Details.
Write a Target Summary that names your immediate India-based infrastructure-support role family plus your longer-term U.S. information security direction.
Select Preview to review the opening sections.

You should see a concise introduction that matches the career direction in your profile README. The summary should make no employment or immigration promises.

Return to the file editor.
Copy the degree wording from your certificate into Education character for character.
Use Bachelor of Computer Applications (BCA), Cyber Security Specialization only when it matches your certificate exactly.
Include Cloud Security as coursework only when an official transcript or academic record supports it.
Select Preview to check the rendered education section.

Your education section should now mirror your official record. Any coursework label should have its own supporting academic evidence.

Return to the file editor.
List only supportable skills under Evidence-Backed Skills.
Write each Selected Projects bullet using an action, a tool, and an observable result.
Select Preview to inspect the skills and project bullets.

You should see claims that connect to your certificate, coursework, profile README, or career-gap.md. Each project result should describe something a recruiter can open or verify.

Return to the file editor.
Move unfinished networking, Linux, and cloud labs into a Future Build Queue under Additional Information.
Select Preview to confirm the planned labs appear outside your completed evidence.

The preview now keeps future labs in their own queue. Your completed skills remain separate and defensible.

Preview and commit the resume

The final review tests whether every skill or achievement has a source you could show if asked. This audit protects the credibility of the whole career launch kit.

Return to the file editor.
Remove any skill or achievement that lacks supporting evidence.
Keep every unfinished lab inside the future build queue.

Before the final preview, picture which certificate, coursework record, or GitHub artifact you could show for each claim.

Select Preview to run the final evidence check.

You should see all six resume sections in the rendered draft. Every current skill or achievement should map to evidence you can produce.

Click Commit changes....
Enter Draft evidence-first resume as the commit message.
Click Commit changes to publish the file.

That's the hard part done: your truthful resume draft is now committed to your public profile repository.

Before opening the committed file, consider whether its rendered view will preserve all six reviewed sections.

Select resume-draft.md from the repository file list.

You'll see the committed resume rendered with contact details, a target summary, education, evidence-backed skills, selected projects, and additional information. Completed claims point to evidence while unfinished labs remain in the future build queue.

Can't Find the Committed Resume?

Confirm the repository file list contains resume-draft.md beside career-gap.md. Check that the commit completed in the repository named YOUR_GITHUB_USERNAME.

Return to the file editor if the draft still shows as uncommitted. Help me troubleshoot why my resume draft was not committed.

Your resume now supports the same career direction as your GitHub evidence plan. Next, you will align your LinkedIn profile with this verified story.

Align Your LinkedIn Profile

Your resume draft now separates completed evidence from future work. Recruiters should meet that same truthful story on LinkedIn.

A mismatched degree or unsupported skill can weaken the evidence you already built. In this step, you will align LinkedIn with the GitHub documents from earlier.

In this step, get ready to:

Save a headline for your immediate role target.
Write an About section grounded in current evidence.
Complete an evidence check across your remaining profile sections.

Update your headline

Your headline is the quickest summary on your profile. It should connect your BCA cybersecurity background to one immediate role family.

Switch back to the LinkedIn profile tab from earlier.
Click the Edit icon in the introduction section.
Enter one headline in the Headline field. Its first part names your BCA cybersecurity background. Its second part uses the immediate support role from README.md. Its final part names one current learning direction from career-gap.md.
Compare every claim with resume-draft.md.
Click Save.

Your saved headline now appears beneath your name. Recruiters can immediately see your background plus your current direction.

Headline Did Not Save?

Return to the introduction section.
Confirm that the Headline field contains your text.
Select Save before leaving the editor.

If the saved text still does not appear, help me troubleshoot my LinkedIn headline update.

Write your About section

The About section gives your headline enough context to feel credible. Two short paragraphs can connect your immediate target to your longer-term security direction.

Check whether your LinkedIn profile already has an About section.

✔️ I already have an About section

Click the Edit icon beside the About section.

The About editor opens with your existing text ready for revision.

ⓧ I need to add an About section

Click Add profile section in the introduction section.

The section menu opens beneath your introduction.

Select Core.
Select About.

The empty About editor is ready for your professional summary.

Write the first paragraph in the editor. State the same immediate support role shown in README.md. State information security as your long-term direction.
Write the second paragraph after a blank line. Name evidence you have already completed. Describe your planned networking, Linux plus cloud-security labs as work in progress.
Click Save.

Your About section now shows two distinct stages in your career plan. Completed evidence stays separate from the practical work you are building next.

About Section Missing Details?

Check that the first paragraph names one immediate support role. Check that the second paragraph labels future labs as work in progress.

If the wording still feels too broad, help me review my LinkedIn About section for truthful career positioning.

Align education and skills

Your certificate is the authority for your degree wording. Cloud Security belongs in coursework only when an official transcript or academic record supports it.

Scroll to the Education section on your LinkedIn profile.
Check whether your qualification already has an entry.

✔️ My education entry already exists

Click the Edit icon beside your existing education entry.

The existing entry opens for comparison with your certificate wording.

ⓧ I need to add my education entry

Click the Add icon in the Education section.

A new education entry opens for your verified qualification details.

Enter the exact degree wording used in resume-draft.md in the field for your qualification.
Click Save.

You have closed a common credibility gap because your Education entry now matches your certificate.

Your Skills section acts as a compact evidence index. Every listed skill should trace to coursework or completed work.

Use the evidence-backed skills section in resume-draft.md as your selection filter.
Click Add profile section in the introduction section.

The section menu opens with the available profile categories.

Select Core.

The Core category now shows Add skills.

Select Add skills.

The skill selection window opens with a list of available skills.

Select one skill supported by your coursework or completed evidence.
Click Save.

The supported skill now appears in your Skills section.

Repeat the same path for each additional supported skill.
Review every entry currently visible in the Skills section.
Classify each skill against your coursework or completed evidence.

✔️ Every skill has supporting evidence

Your skills list already passes the evidence check. Keep the current entries unchanged.

ⓧ I found an unsupported skill

Click the Edit icon in the Skills section.
Click the Edit icon beside the unsupported skill.

The selected skill opens with its available controls.

Click Delete skill.

LinkedIn asks you to confirm the removal.

Click Delete.

The unsupported skill disappears from your profile.

Before you review the finished profile, do you expect every visible claim to trace back to your certificate or existing evidence?

Click Me at the top of LinkedIn.
Select View Profile.
Read the saved headline beneath your name.
Read both paragraphs in the About section.
Compare the Education entry with your certificate.
Compare the Skills section with your coursework plus completed evidence.

You should see a headline that identifies your BCA cybersecurity background. It should also show your immediate support target plus one current learning direction.

Your About section should contain two concise paragraphs. Your Education wording should match your certificate while every listed skill remains evidence-backed.

Found a Mismatch?

Return to the affected section through its Edit icon. Correct the wording before selecting Save.

If you are unsure whether a claim is supported, help me compare my LinkedIn profile with my existing career documents.

You have turned your career documents into one consistent recruiter-facing profile.

Secret mission

Turn the README into a Portfolio Dashboard

Turn your public profile README into the entry point for your career launch kit. You will add document links plus a checklist for the evidence you plan to build next.

Clean Up Your Resources

Choose how much of your career kit stays visible. This project uses free account tiers with no ongoing project cost.

Protect Your Public Information

Your GitHub profile repository is public. Anyone can read its committed files.

Remove private contact details, identity documents, certificate scans, passwords, or API keys before leaving the repository visible.

Resources you used:

A public GitHub profile repository named YOUR_GITHUB_USERNAME.
A public profile introduction committed as README.md.
A public evidence plan committed as career-gap.md.
A public resume draft committed as resume-draft.md.
A saved LinkedIn headline.
A saved LinkedIn About section.
A saved LinkedIn Education entry.
A saved LinkedIn Skills section.

Keep everything running

No action is needed while you are using this kit for applications. Choose this option when you want recruiters to keep seeing the dashboard.

Leave the YOUR_GITHUB_USERNAME repository public.
Keep README.md available as your profile dashboard.
Keep career-gap.md available as your evidence plan.
Keep resume-draft.md available as your truthful resume draft.
Leave your aligned LinkedIn profile content visible.

Pause - I'll come back to this later

Private visibility preserves the repository for your return. It also removes the profile README from public view.

Switch back to the YOUR_GITHUB_USERNAME repository on GitHub.
Select Settings.
Scroll to Danger Zone.
Select Change repository visibility.
Select private visibility.
Select I have read and understand these effects.
Select Make this repository private.

The repository is now private. Your profile README stops appearing publicly.

Your LinkedIn profile remains visible.

Delete - I don't want to use this again

Deleting the repository looks final because it is permanent. This option fits when you no longer need the public career kit.

Repository deletion removes README.md, career-gap.md, resume-draft.md, and the profile dashboard.

Return to the YOUR_GITHUB_USERNAME repository on GitHub.
Select Settings.
Scroll to Danger Zone.
Select Delete this repository.
Select I want to delete this repository.
Select I have read and understand these effects.
Enter YOUR_GITHUB_USERNAME as the repository name.
Select Delete this repository.

The repository is now deleted. Its profile README no longer appears on your GitHub profile.

Your LinkedIn profile is separate from the deleted repository. Reverting its sections restores the content that existed before this project.

Return to the LinkedIn tab from earlier.
Select Me.
Select View Profile.
Select the Edit icon beside the introduction section.
Restore the previous wording in the Headline field.
Select Save.

Your previous headline is visible again.

Select the Edit icon beside the About section.
Restore the About section to its pre-project wording.
Select Save.

Your previous About text is visible again.

Select the Edit icon beside the Education section.
Restore the Education entry to its pre-project state.
Select Save.
Select the Edit icon beside the Skills section.
Restore the Skills section to its pre-project state.
Select Save.

Your Education entry now matches its pre-project state. Your Skills section now matches its pre-project state.

That completes the reset. The public career launch kit no longer appears on GitHub.

Your LinkedIn profile now reflects its pre-project content.

Nice Work!

You did it! You built a public GitHub career dashboard that matches your LinkedIn profile.

You've learned how to:

Present a realistic career direction that connects India-based infrastructure support to longer-term information security work in the United States.
Build a 12-week evidence plan from current role requirements. Use it to guide your next networking, Linux, cloud identity, and cloud-security projects.
Align your truthful professional branding across resume-draft.md plus LinkedIn. Support every listed skill with coursework or completed evidence.
Secret Mission: Turn the profile README into a recruiter-friendly dashboard. Link it to both career-gap.md and resume-draft.md.

Ready to quiz yourself?