What I Learned from 10 Front‑End Interviews in Shanghai: Real Stories & Practical Tips
A former communications engineering graduate shares a detailed chronicle of ten front‑end interview experiences across startups, small firms, mid‑size companies, and a pre‑IPO e‑commerce firm in Shanghai, highlighting interview questions, personal reflections, and actionable lessons for aspiring developers.
Interview Process Overview
Over a month the candidate submitted roughly 60 resumes, received 13 interview invitations, and attended about 10 interviews across four company sizes: early‑stage startup (0‑20 employees), small company (20‑40), mid‑size education firm (50‑99), and a pre‑IPO e‑commerce firm (100‑499). The typical interview flow consisted of:
Written test or technical screen.
HR interview.
Deep‑technical round with a senior engineer or technical manager.
Typical Technical Questions
Vue.js basics: component lifecycle, Vuex state management, client‑side data export (e.g., Excel) without backend support.
Core JavaScript concepts: scope, closures, prototype chain, object‑creation patterns (factory, constructor, class).
HTTP & REST: RESTful conventions, status codes, retrieving the User‑Agent string, differences between GET and POST, form submission via POST.
Promises: execution order, async/await mapping, whether jQuery.ajax returns a Promise.
CSS layout: position values (static, relative, absolute, fixed), differences between transform and transition.
Vue source code: where the reactivity system is implemented, how watchers are registered.
General web fundamentals: client‑side performance considerations when generating files.
Sample Written‑Test Questions
Describe how to submit a form using POST.
Explain the principle of JavaScript Promise and whether jQuery.ajax returns a Promise.
How to obtain the User‑Agent string in JavaScript.
Explain the difference between position: absolute and position: relative.
Distinguish between CSS transform and transition.
Key Preparation Recommendations
Strengthen fundamentals: Review core JavaScript (scope, closures, prototype, object creation), HTML/CSS layout, and HTTP/REST concepts. Build small projects that require manual file generation (e.g., client‑side CSV/Excel export) to solidify understanding.
Practice coding daily: Use online judges or coding platforms; revisit high‑level front‑end book chapters (e.g., “高程” chapters 1‑6) before each interview.
Prepare for the interview flow: Keep a written‑test question set, rehearse HR answers (career goals, teamwork), and be ready for deep‑technical probing of framework internals and design patterns.
Document questions: After each interview, record the questions and your answers in a personal knowledge base, categorizing by topic for later review.
Guide the conversation: When possible, steer the interview toward areas you are comfortable with while showing willingness to learn unfamiliar topics.
Leverage community resources: Join front‑end discussion groups, use public Q&A platforms, and consult open‑source repositories for reference implementations.
Common Pitfalls Observed
Relying on framework usage without understanding underlying JavaScript leads to failure in deep‑technical rounds.
Neglecting the HR round; hiring decisions can be heavily influenced by cultural fit and communication.
Misrepresenting experience level (e.g., claiming two years when only one year of solid work exists) creates mismatched expectations.
Complex salary structures and unclear compensation terms can cause post‑offer disappointment; verify net salary before acceptance.
Outcome Summary
The candidate received two offers and accepted a position at an online education platform, citing internal learning resources as a key benefit.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
ITPUB
Official ITPUB account sharing technical insights, community news, and exciting events.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
