From QA to front-end: an offer in six weeks

Lin (not his real name) spent three years in testing at a mid-sized fintech company, most of it writing automation: API regression, end-to-end scripts, quality gates in CI. He knew exactly where he wanted to go: writing product code full time, as a front-end developer. His worries were the usual ones. Is switching realistic in this market? Without a front-end title on the CV, would anyone even look?

I rewrote my CV again and again and got nothing back. What I really needed was someone to tell me, honestly, what I was missing and what I wasn't.

Week one: taking stock

The first few conversations did not rush into the CV. They started by mapping what he already had. The JavaScript built up over four automation frameworks was solid, the CI experience was real, and a tester's eye for edge cases counted in his favour. JobExpress set all of this against the junior front-end roles currently open in London and named the gaps precisely: component frameworks he could use but had not gone deep on, no product-grade work he could show publicly, and a CV that read as testing duties from top to bottom.

The skills assessment set a paper pitched at junior front-end level. JavaScript and debugging scored high; component state management and styling and layout came out clearly low. Once the radar chart was laid out, Lin could see for the first time that he was not 'a bit short on everything'. He was short in two specific places.

Weeks two to five: closing the gaps

The learning roadmap started from those two gaps and was laid out week by week around Lin's time, two hours each evening and half a day at the weekend, with a completion standard written for every stage.

• Go deep on one framework instead of skimming three. React was the choice, and the bar was being able to build a small app with routing and state management on his own
• Two small but complete projects: a booking component and a data dashboard. Both chosen to look like real work output rather than tutorial copies, with the code in public repositories
• Rewrite the CV to lead with engineering: the four automation frameworks restated as delivered code, a number attached to every line, and the testing duties compressed into one paragraph

The rewritten CV went through an ATS score first. The first version came out at 61, losing marks mainly on keywords and phrasing: React, TypeScript and component libraries were all in the job description and none of them were on the CV. After adding the keywords for the target roles and switching from a two-column layout to a single column, the third version reached 84.

Week six: targeted applications

No mass applying. JobExpress filtered roles by Lin's job-search profile, keeping only those confirmed as genuinely open and friendly to juniors: 11 in total. Every CV was tailored to the exact wording of the job description, and every cover letter was written from his own projects; any line that did not sound like him was rewritten until it did. Every application went into the progress tracker, so who had not replied and when to follow up was clear at a glance.

Interviews and offers

Four passed the initial screen and three went to interview. In the technical rounds the two public projects became the main topic, and the interviewers pressed him on design trade-offs rather than 'why don't you have front-end experience'. At one company the testing background turned out to be the selling point: they were short of a front-end developer who understood quality gates. He ended up with two offers and chose the smaller team where he could work across the whole product. Eight weeks after the first conversation, he started as a front-end engineer.

Looking back: three things that made the difference

• Start by mapping what is not missing. Three years of testing was not baggage; the JavaScript and CI experience went straight to the top of the CV
• Fill two gaps, not everything. With limited time, the narrower the route, the more likely you are to finish it
• Apply less, but apply precisely. Four of 11 passed the screen, better than dozens of scattered applications had ever managed