What does name attribute do in an input field ?

0-2 years experience

1. 1If you add <input type='text' name='email'> to a form and submit it, what will the server receive for that field?
2. 2How would you retrieve the value of an input with name='username' using the FormData API?
3. 3What does the browser send when two inputs in the same form share the same name attribute?

2-5 years experience

1. 1Our login form has the password input mistakenly using name='user' instead of name='password'. The backend rejects the request—explain why and how you'd fix it.
2. 2A client‑side validation script uses document.querySelector('[name=phone]') but sometimes fails on dynamically added inputs. What could be causing this and how would you debug it?
3. 3Describe how server‑side frameworks bind form data to objects using the name attribute, and what problems arise if the names don't match the expected property names.

5-8 years experience

1. 1We're building a multi‑step checkout flow that aggregates data from many forms across pages. Discuss the trade‑offs of relying on name attributes for data aggregation versus using a client‑side state store.
2. 2Our product must support internationalization where visible field labels are localized. How would you keep the name attribute stable for backend processing while showing localized labels to users?
3. 3On a high‑traffic site handling millions of form submissions daily, what performance or security considerations stem from how name attributes are serialized, and how would you mitigate them?

8+ years experience

1. 1Our legacy monolith maps input name attributes directly to database column names. We're moving to microservices with separate validation services—how would you refactor the naming strategy to reduce coupling while preserving backward compatibility?
2. 2Multiple teams have inconsistent naming conventions for form inputs, causing bugs in shared analytics pipelines. Propose an organization‑wide policy and tooling to enforce a consistent naming schema, and outline the rollout plan.
3. 3We need to support both traditional HTML form submissions and JSON API payloads for the same data, which may use different naming conventions (snake_case vs camelCase). How would you reconcile these differences while keeping the front‑end maintainable?