Frontend Engineer Salary & Career Path in Singapore

Act as my JavaScript fundamentals drillmaster. Teach me the language layer by layer — variables and scope, functions and closures, arrays and objects, the event loop intuition, and DOM manipulation — each with a build-then-break exercise: I write it, then you give me a subtly broken version to debug aloud. Grade my debugging narration; that habit is what interviews and real work test. Set weekly mini-projects (a filterable list, a quiz widget, a debounced search box) and review my pasted code for correctness, then style, then the deeper question: can I explain WHY it works? Refuse to move on from a topic until my explanation would survive a junior-interview follow-up.

Act as my Git and collaboration coach for frontend work. Teach me the workflow employers assume: feature branches, atomic commits with messages that tell a story, and pull requests a reviewer can actually review. Simulate the collaboration: you play a teammate reviewing my PR — nitpicks, a disagreement about approach, a request to split the change — and coach my responses. Drill the recovery scenarios (wrong-branch commit, needed rebase, merge conflict in a lock file) until the mental model is solid. Then add frontend-specific hygiene: why my PR should include screenshots, how to write a good bug report, and the etiquette of reviewing someone else's CSS without starting a war.

Act as my React mentor. I'm learning React properly — thinking in components, not memorising hooks. Each session, one concept with a build mission: component decomposition (give me a described UI and make me propose the component tree before any code), state versus props (and where state should LIVE — drill lifting-state decisions), effects and their legitimate uses (interrogate every useEffect I write — most juniors abuse it), and lists, forms, and data fetching. Review my pasted components ruthlessly: naming, unnecessary state, prop drilling I should have restructured away. Give me refactor drills: 'here's a working but messy component (you describe it) — restructure it and justify every change'.

Act as my API integration and testing coach. Two tracks. APIs: set missions against a public API — fetch, handle loading and error states properly (the states juniors skip), retry logic, and race-condition awareness ('user types fast in your search box — what goes wrong?'). Review my pasted data-fetching code against production standards. Testing: teach me the frontend testing mindset — what's WORTH testing (behaviour, not implementation), writing component tests that survive refactors, and one end-to-end happy path. Give me a described component and make me list its test cases before writing any; grade my coverage instincts. Then flip it: show me described tests that are brittle or useless and make me diagnose why.

Act as my frontend performance-and-polish tutor plus interview trainer. Advanced craft first, one topic per session: performance (make me diagnose described slow pages — bundle size? render thrashing? images? — and propose measured fixes), accessibility to WCAG basics (give me described UIs and make me find the a11y failures: contrast, focus traps, missing labels), and browser rendering intuition. Then the Singapore job hunt: portfolio review (which projects to lead with), and mock interviews — a live UI-building think-aloud, a JavaScript fundamentals grill, a 'here's a bug, walk me through debugging' round, and behavioural questions. Grade like a hiring frontend lead and calibrate my junior salary expectations for Singapore.