What LinkedIn is for
LinkedIn is a professional profile and a job search site at linkedin.com. Recruiters in Kerala IT parks use it to read your background and, sometimes, to message you. It is not a government portal, and a complete profile does not create a job. InfoparkDaily is not affiliated with LinkedIn.
Use it for four jobs: a public record of your work, a search of open roles, a way to reach a named person after you have applied, and a place to show work you can talk about in an interview.
Create the account
- Open linkedin.com on a laptop if you can. The phone app is fine later. The first setup is easier on a wide screen.
- Join with an email you will still have in two years. A college email that dies after graduation locks you out. Add a phone number in settings so you can recover the account.
- Use your real name, the one on your resume and certificates. A nickname, a company name, or “Java Developer Available” as the name makes the profile look fake.
- Set the location to the city where you can attend an interview: Kochi, Thiruvananthapuram, Kozhikode, or the city you will move to. Do not put “India” if you want local recruiters to find you.
- Turn on two-step verification in Settings → Sign in and security. Job hunters are targeted by fake HR accounts.
Photo, banner, and headline
The photo is a clear head-and-shoulders picture, facing the camera, with a plain background. You do not need a studio. You do need a picture where your face is visible. A logo, a group photo, or a blank circle gets skipped.
The banner can be a simple campus or desk photo, or LinkedIn’s plain background. Do not paste your phone number across the banner. That invites spam, not interviews.
The headline sits under your name. It is not a slogan. Put the role you want, the skill that proves it, and the city.
- Fresher example: “Fresher Java developer · Kochi · academic projects in Spring Boot”
- Experienced example: “QA engineer · 3 years · Selenium and API testing · Kochi / open to Trivandrum”
- Career switch example: “Support engineer moving into manual testing · Kochi · ISTQB in progress”
Change the words to your real skill. Do not copy a headline whose tools you cannot explain in an interview.
About section
Write four short parts in the first person.
- What you do now, in one sentence.
- Two or three skills you can demonstrate, with a tool name.
- One result: a project, an internship, a ticket volume, a feature you shipped. Numbers help only when they are true.
- What you want next, and the cities you will work in.
Example you can adapt: “I am a 2025 B.Tech graduate in Kochi. I have built a Spring Boot and MySQL project for a library system and a React page that lists the books. I am looking for a junior Java or full-stack role in Infopark or Technopark and can join after the notice period I do not yet have — I am available now.” Delete any sentence that is not true for you.
Skip “passionate team player” and “synergy”. Recruiters search for skill words: Java, Python, manual testing, Figma, accounts payable, .NET.
Experience, education, and projects
Add each job with the company name, title, city, and months. Write three bullets. Each bullet is a task plus a result. “Worked on APIs” is weak. “Wrote REST endpoints for invoice search and cut the old report from two hours to a button” is something an interviewer can ask about.
Freshers: use Projects and Education, not an empty Experience block. For each project name the stack, what the user can do in the app, and your part if it was a team. Link the GitHub or a live demo if it is public and still works. A broken link is worse than no link.
Internships count. So does a college placement-cell project if you can explain it. A one-week certificate course is a license or a skill, not a job.
Education: degree, college, year, and score only if you want it public. Kerala IT screens often ask for the degree name, not the percentage.
Skills, Featured, and the custom URL
Add the skills you can answer questions on. Pin the five that match the roles you are applying for this month. Remove skills you added because a classmate had them.
Featured is for one resume PDF, one project, or one post. Do not pin five certificates. Recruiters open the first item.
Settings → Edit public profile → custom URL. Use your name: linkedin.com/in/your-name. Put that URL in the resume header. A URL full of numbers looks unfinished.
Open to Work: you can show it to recruiters only, or to everyone. “Recruiters only” is the quieter choice if your current employer is on LinkedIn. The green frame does not rank you above other people. It only labels you.
How to search jobs
- Open LinkedIn Jobs.
- Search a role, not a sentence. “Java developer”, “manual tester”, “business analyst”. Add the city: Kochi, Ernakulam, Thiruvananthapuram, Kozhikode.
- Use the filters that matter: date posted (past week), experience level, and on-site or hybrid. “Easy Apply” is a convenience filter, not a quality filter.
- Open the company name. If the company has no website, no employees, and a job posted an hour ago that asks you to pay, stop.
- Read the full description. Many “Kochi” posts are for another city with a line that says remote or relocation.
- Set an alert for two searches you will actually open. Ten alerts become noise and you miss the real one.
Easy Apply sends the resume stored on LinkedIn. Update that file before you use it. If the post also links to the company careers page, prefer the company page when the description says “apply on our site”. Apply once. Applying on both creates two records and looks careless.
After you apply, save the job and write the date in a note or a sheet. LinkedIn will not remind you of every closing date.
How to connect with HR
A connection request is a request to be in someone’s network. It is not an application. The application is the form or the email the job post names. Connect after you have applied, or when you have a real reason: you studied the same subject, you worked with their product, or you are asking one specific question.
Find people with Search. Filter by the company, then by titles such as Recruiter, Talent Acquisition, HR, or the hiring manager title in the job post. Do not message ten people with the same text. Pick one recruiter and, if you need a second person, the hiring manager.
Write a note that fits in the box LinkedIn shows. The limit changes, so if the box is short, keep one sentence. Say who you are, which role, and that you already applied.
- Connection note: “Hello, I applied today for the Java developer role at [company] in Kochi. I have two years of Spring Boot. If the role is still open I can share a short project note.”
- After you apply, if you are already connected: “Hello, I submitted the application for [role] on [date] through [the careers link / Easy Apply]. Happy to share anything else you need.”
- Referral, only if you know the person: “I applied for [role]. If you are comfortable referring me, the job link is [url]. If not, no problem.”
Do not write “Dear Sir, I am a hardworking fresher, please check my profile and do the needful.” It gives the reader no role and no fact. Do not send a follow-up the next morning. Five to seven days is enough, and only one follow-up.
If they do not reply, the application still stands. Silence is common. It is not a reason to message their personal number if they did not publish it.
How to write a LinkedIn post
A post is useful when a stranger can learn what you did. It is not useful when it asks for a job in the first line and offers nothing to read.
A simple structure:
- One sentence on the problem.
- What you built or tested, with the tool names.
- What changed, if you can measure it. If you cannot, say what the user can do now.
- One thing you would do differently.
- Optional last line: you are open to a junior role in Kochi. Put the role once, not as a paragraph of hashtags.
Example: “Our college library still used a paper register. I built a small Spring Boot app where a student can search a book and a staff user can mark it issued. The data sits in MySQL. I would add login next, because the current version trusts the browser. I am looking for a junior Java role in Kochi.”
Post when you finish something: a project, a bug you fixed, a course you can explain, a walk-in you attended and what the company actually asked. Do not post every certificate the day you download it.
Hashtags: three specific ones are enough, such as #Java, #Kochi, #SoftwareTesting. Twenty hashtags look like spam. Tag a company only if the post is about work you did for them and you are allowed to talk about it. Do not tag ten HR accounts to force a reply.
Comments: reply to people who ask a real question. A comment that only says “Congratulations” on fifty posts does not build a profile.
Images: a screenshot of the app, a short architecture sketch, or a photo of a notebook diagram. Cover personal data in screenshots. Do not post offer letters, ID cards, or someone else’s resume.
A week that is enough
- Monday: update the headline and the top three skills to match the roles you will apply for.
- Tuesday and Thursday: apply to a small number of fitting roles and save the links.
- Wednesday: one connection note to a recruiter on a role you already applied for.
- Friday: one post or one Featured item. Skip the week if you have nothing new. An empty week is better than a fake post.
Safety
- No one from LinkedIn will ask you to pay a fee to “unlock” a Kerala IT job.
- Do not share OTP, Aadhaar, or bank details in chat.
- A message that moves you to Telegram immediately, and then asks for money, is a scam pattern. Stop.
- Check the company on its own website and, when the role claims an Infopark or Technopark address, on the park board linked from the career tools page.
Next: build the PDF in the resume builder, then read the Naukri guide if you also want a resume database profile.