An answer bank is a saved set of truthful replies to the screening questions employers ask again and again: years of experience with a skill, notice period, current and expected CTC, work authorization, relocation and commute. Build it once, in about thirty minutes, and every later application reuses the same consistent answers instead of you retyping them, or worse, answering differently on Monday than on Friday. This post lists the question types you will meet on LinkedIn Easy Apply, how to write each answer, and how to keep the bank current.
Why consistency matters more than speed
Speed is the obvious benefit, but consistency is the real one. Recruiters at the same company often see several of your applications, and some applicant tracking systems keep your previous answers. If you said 4 years of React on one form and 6 on another, that looks careless at best. A single source of truth prevents that. It also prevents the quiet drift where tired evening answers get vaguer than morning ones.
The question types to cover
Years of experience with a specific skill
Easy Apply frequently asks "How many years of work experience do you have with Java?" with a number box. List every skill in your resume and write a whole number for each. Be honest and conservative: count professional use, not a weekend course. If you used a tool for 18 months, write 1, not 2. Some forms reject decimals, so a whole number is both safer and easier to defend in an interview.
Add the skills that appear in job descriptions you target, even if you have little experience. For a skill you have never used professionally, the truthful answer is 0, and it is better to save that than to leave the question unanswered and have the run pause every time.
Notice period
Indian employers ask this almost universally, sometimes as a dropdown (Immediate, 15 days, 30 days, 60 days, 90 days) and sometimes as a number of days. Save both forms: the number of days and the closest dropdown label. If you are serving notice, decide how you will phrase it and keep it the same everywhere.
Current CTC and expected CTC
Decide on the unit before writing anything. Some forms want annual figures in rupees, some in lakhs per annum, some ask for monthly figures, and global roles may want a currency. Save your figures in each format you are likely to meet, for example annual rupees as a plain number and lakhs per annum as a decimal like 12.5. Write your expected figure as a realistic range in text fields and a single number in numeric fields.
Work authorization and visa sponsorship
"Are you legally authorized to work in this country?" and "Will you now or in the future require sponsorship?" are yes/no questions with legal weight. Answer them exactly as your situation stands for each country you target. This topic has enough traps that we cover it separately in handling work authorization forms.
Relocation and commute
"Are you willing to relocate?" and "Are you comfortable commuting to this job's location?" look harmless, but answering yes to roles you would never take wastes your application and the recruiter's call. Decide your real limits: which cities you would move to, and how far you would commute for a hybrid role. If your answer genuinely depends on the city, narrow your location filters rather than saying yes everywhere.
Education and certifications
Degree level, graduation year, and yes/no questions like "Do you have an AWS certification?" Save your highest degree, the year, and a clear list of certifications you hold right now, not ones in progress.
Free-text questions
Occasionally a form asks "Why are you interested in this role?" or "Describe a project using Kafka." These do not reuse well. Keep a short, honest two-sentence summary of your background that you are comfortable sending, and accept that some questions deserve a manual answer.
How the answer bank works in AutoApply CV
You save answers in the dashboard and sync them to the extension settings. During a run on LinkedIn Easy Apply, the extension fills matching questions from those saved answers. When it meets a question it cannot answer truthfully from the bank, it pauses that job instead of guessing, and the question shows up under pending questions on the dashboard. Answer it there, save, and the next time that question appears it is filled for you. Paused jobs do not use your daily allowance. More detail on the extension side is on the Chrome extension page.
Writing rules that save you trouble later
- Only write what you can defend in an interview. If a recruiter asks you to talk about your 5 years of Kubernetes, you need 5 years of stories.
- Use whole numbers for years. They pass more validation rules and are easier to keep consistent.
- Save multiple phrasings. "Years of experience with SQL" and "How many years have you worked with SQL databases?" may need separate entries with the same answer.
- Avoid absolute claims you cannot meet. "Can you start immediately?" should only be yes if it is true.
- Keep salary units explicit. Note in the bank whether a figure is annual, monthly, rupees or lakhs.
Keep it current
An answer bank goes stale. Your experience count rises every year, your notice period changes when you resign, and your expected CTC moves after an offer. Set a reminder to review it monthly, and immediately after any of those life events. Re-sync to the extension after each edit so old values do not keep going out.
Next step
Open the last five job descriptions you were interested in, copy every skill named in them, and write a whole-number year count for each into your answer bank today. That one list covers the most common pause reason before your next run.
