Bangalore Senior Backend Engineer JD (₹40-60 LPA)

You are writing a job description for a Senior Backend Engineer role at an Indian company. Optimise for Bangalore tech talent — they are sceptical of buzzwords and read the salary band first.

## Inputs
- Company name: {{company_name}}
- What the company does (1 line): {{company_one_liner}}
- Team size: {{team_size}}
- Funding stage / revenue stage: {{stage}}
- Tech stack (primary): {{tech_stack}}
- Salary band (LPA, fixed): ₹{{salary_min_lpa}}-{{salary_max_lpa}} LPA
- ESOP offered (yes/no): {{esop}}
- Work mode: {{work_mode}}
- Office address (if hybrid/onsite): {{office_address}}
- Notice period buyout offered: {{buyout}}
- Hiring manager: {{hiring_manager}}
- 3 must-have skills: {{must_haves}}
- 2 nice-to-have skills: {{nice_to_haves}}

## Output structure
```
[Title] — Senior Backend Engineer ({{work_mode}}, Bangalore)
[Band] ₹{{salary_min_lpa}}-{{salary_max_lpa}} LPA fixed{{esop_line}}
[Notice] We hire candidates serving notice, and offer buyout: {{buyout}}.

About {{company_name}}
— 2 sentences, plain English, no "disrupting" / "revolutionising". Include team size and stage.

What you'll do
— 4-5 bullets, each starting with a verb, each tied to {{tech_stack}}. Real work, not hype.

Must have
— bullet list of {{must_haves}} with 1 line of context each.

Nice to have
— bullet list of {{nice_to_haves}}.

How we work
— 3 bullets: code review style, on-call expectations, growth signal.

How to apply
— 1 line: who to email or what link. Hiring manager: {{hiring_manager}}.
```

Rules: no "rockstar", no "ninja", no "10x". Do not mention free snacks, foosball, or unlimited PTO. Stick to facts in the inputs.