Callum King

Seeing far fewer Frontend roles right now Spoke to an engineer yesterday who thinks this is partly due to how easy it is to prompt AI to generate HTML, CSS, and JavaScript using frameworks like React, Vue, or Angular Whats everyones thoughts? Surely this can't be the only reason for the decline in demand

27

43 Comments

If you’re still spending hours finding locators and writing brittle UI test scripts, you’re living in the good old days of test automation. Modern UI automation doesn’t start with XPath anymore. It starts with intent. In this article, I’ll show you how to build smart, self-healing UI test automation using Selenium MCP and AWS Bedrock. Check it here -> https://lnkd.in/g8yfdYcW

2

During Rails developer interviews, performance optimisation knowledge consistently separates candidates who receive offers from those who don't. Our clients tell us that developers who understand production performance characteristics command 15-25% higher salaries. Performance skills employers prioritise: 🔹 Identifying N+1 queries and implementing eager loading solutions 🔹 Understanding database indexing strategies for frequently queried columns 🔹 Implementing effective caching strategies (fragment, Russian doll, HTTP) 🔹 Using profiling tools like Bullet, Scout, or New Relic 🔹 Optimising background job processing to maintain responsive applications Technical leads at our client companies consistently mention that candidates who can discuss real-world performance challenges they've solved stand out significantly during technical assessments. Why performance knowledge matters for your career: Senior Rails positions almost always require demonstrated performance optimisation experience. The ability to discuss how you've improved response times, reduced memory usage, or scaled applications proves you've worked on production systems at scale. Developers who've used APM tools and can articulate their findings during interviews demonstrate production experience that junior developers lack. This distinction directly impacts compensation negotiations. Career development insight: If you're currently in a junior or mid-level Rails role, volunteering to investigate performance issues provides valuable experience that accelerates career progression. Our placement data shows developers with documented performance improvement projects receive significantly more interview requests. What performance challenges have you tackled in your Rails career? We're connecting developers who understand production optimisation with companies valuing this expertise. #RailsPerformance #CareerDevelopment #RubyOnRails #TechSkills #TechRecruitment

5

*Live coding tests for Developers during interviews. A good idea?* I increasingly see more organisations asking Developers to complete live coding tests during interviews. I’m mindful that these tests help assess technical skills and allow interviewers to see candidates solve problems in real-time, but are good Developers being passed by that don’t cope well with this type of interview? Some talented Developers often feel anxious during these tests, which can affect their performance. The focus on quick thinking may compromise thoroughness, and complex problems may not fit well within the time constraints. Additionally, factors like communication style can inadvertently influence interviewer perceptions. Furthermore, live coding tests often overlook crucial skills such as system design and teamwork. Thus, it’s important to consider whether these tests reflect a Developer’s capabilities or simply measure performance under stress. What’s your experience of live coding tests during an interview? #LiveCoding #TechRecruitment #DeveloperInterviews #HiringDebate #SoftwareEngineering #InclusionInTech

3

"You're not a junior anymore - but you're not quite 'senior' either. So what now?" That awkward space in the middle. Too experienced for junior roles. Not quite ticking all the boxes for senior. I speak to a lot of .NET devs who feel stuck in the "mid-level gap". Here's the reality - this is where you build influence: - Own small projects or features from end to end - Mentor others, even informally - Speak up in sprint reviews and planning - Learn to explain technical decisions clearly Hiring managers aren't just looking for strong coders at senior level - they want problem solvers who can shape direction. If you're in that gap and not sure what to focus on next, feel free to get in touch. #DotNet #SoftwareEngineering #CareerGrowth #TechCareers

8

It’s worth having a closer look at who’s actually involved in your hiring process. I’ve seen interviews where the candidate never speaks to another tester. Or where all the questions come from a developer’s perspective - focused on speed, coverage, tooling - but missing the bigger picture around risk, quality strategy, or communication. And for the candidate? That’s telling. If the team doesn’t involve test engineers in hiring, what message does that send about how they’re valued internally? The best processes I’ve seen bring testers into the room early - not just to assess, but to represent what the team actually cares about when it comes to quality. Because culture isn’t just how you work. It’s also who gets a voice. Hiring someone into a test role without showing them what that role really looks like on your team? That’s a missed opportunity - for them and for you.

5

Blazor United and the rise of full-stack .NET is something that’s been coming up more and more in conversations I’ve been having with .NET developers recently. A common theme I’m hearing is frustration around constantly needing to jump between backend C# and whichever JavaScript framework is currently in demand. Blazor United seems to be changing that conversation, with developers telling me they’re excited about being able to build across the full stack using .NET. The ability to combine server-side and WebAssembly rendering in one model is a big part of the appeal, along with improvements in performance, payload optimisation, and built-in security features. From a recruitment perspective, it feels like this could drive stronger demand for engineers who can deliver end-to-end solutions within the .NET ecosystem. Definitely one to watch as adoption grows. Do you agree? #DotNet #Blazor #FullStackDevelopment #TechHiring

34

32 Comments

One month back at OpusRS – here’s what I’m seeing in the JavaScript contract market. It’s been great to get stuck back in, and I’ve already noticed some clear trends across the UK JavaScript contract space. 🏢 Hybrid working is shifting. Fully remote roles are becoming less common, with more contracts now asking for 2–3 days a week in the office. Collaboration and team presence are making a comeback. 💬 Contractors who know how to add value and communicate clearly with clients are being consistently extended. It’s not just about technical ability—commercial awareness and soft skills are making a real difference. 📉 Rates have taken a hit compared to a few years ago, but demand is still strong for those who can hit the ground running. ⚙️ Next.js is gaining serious traction. While React remains dominant with 39.5% of developers using it, Next.js is quickly rising with 17.9% adoption—thanks to its performance benefits and built-in features like server-side rendering and static site generation If you're a contractor looking for your next move, or a business needing top JavaScript talent, I’d love to connect. #JavaScript #NextJS #ReactJS #Contracting #TechRecruitment #OpusRS

25

2 Comments

🚀 Big .NET shifts ahead in 2026 and they’re already impacting the talent market. I’ve just read a great overview of the top .NET trends, and it aligns strongly with what I’m seeing in Software Engineering recruitment: 🔹 Modern .NET skills are now essential, not optional especially with the latest LTS releases and performance-focused C#. ���� AI-native development is becoming standard. Experience with tools like Copilot, ML.NET, and Semantic Kernel is increasingly expected. 🔹 Cloud-native architecture dominates hiring needs, particularly Azure, microservices, and containerization. 🔹 Security-first engineering is rising fast, with DevSecOps and Zero-Trust now core competencies. 🔹 Blazor and MAUI are gaining real traction, driving demand for full-stack .NET developers. 💡 In short: .NET roles are evolving quickly, and companies are looking for engineers who can blend cloud, AI, and modern development practices. Have a read of the full article here: https://lnkd.in/ef5nMpD3 If you’re exploring opportunities or building a .NET team, I'm happy to connect.

31

1 Comment

Been working with a few developers recently who are using Blazor on the front end, still fairly unspoken about, but definitely one of those frameworks that’s starting to pop up more and more. It’s made me notice a wider trend in newer tech that developers are starting to move towards: .NET MAUI: loads of .NET devs dipping into cross‑platform UI. WebAssembly: not mainstream yet, but definitely growing, especially with .NET and Rust folks. Bun & Deno: early adopters moving away from Node for speed and cleaner tooling. Svelte & SolidJS: the “lighter than React” frameworks gaining real traction. There’s a clear shift towards devs becoming more rounded — picking up new tools and frameworks as the stack evolves. Feels like we’re in one of those phases where the stack is updating again, Developers are quietly upskilling into the next wave. Im Curious what others are seeing, what’s the next “unspoken but growing” tech you’re spotting.

13

🔥 If you explain BDD like this in an interview… you’ll get shortlisted instantly. Most candidates talk about Cucumber, step definitions, tags, and runners. But a real SDET explains BDD the way it’s meant to be used: ⭐ **“BDD is not a testing framework. BDD is a collaboration framework that produces testable requirements.”** That one line changes the entire interview. Here’s how I explain BDD clearly: 1️⃣ BDD starts before automation It begins with the 3 Amigos (BA + Dev + QA) discussing user stories. Goal → achieve shared understanding. 2️⃣ Gherkin converts business language → executable scenarios Instead of writing test cases in QA language, we write: Given (context) When (action) Then (expected outcome)** This becomes living documentation. 3️⃣ Automation connects Gherkin to code Using tools like Cucumber / SpecFlow / Behave, we bind scenarios to step definitions using code (Java/Python/JS). 4️⃣ CI/CD runs these scenarios as acceptance tests This ensures: ✔ Business rules aren’t broken ✔ Regression stays clean ✔ Requirements stay up-to-date 5️⃣ The true value of BDD Not the tools. Not Gherkin. Not automation. 👉 The real value is eliminating ambiguity in requirements. 70% of defects come from unclear requirements — BDD solves that. #AutomationTesting #SoftwareTesting #SDET #TestingFramework #TestAutomation #AutomationFramework #QualityEngineering #QACommunity

23

There’s a lot of fuss about digital ID‘s in the UK and one of the major concerns appears to be centralised data. But honestly? The problems already here. Have you ever heard of HMRC Connect? It’s part of a multi-layered partially AI powered tool that pulls information from all sorts of government departments and public sources like social media. HMRC officially uses this for fraud detection and investigating potential tax evasion. In reality Connect has access to almost anything: - Claims you’ve made with DWP - Cars registered with DVLA - If you ever bought or sold a house (Land Registry) - When you enter and leave the country (Home Office and Border Force) - Your bank and savings accounts - Your pensions - Your social media history - Your credit history - and many more things from insurance, to companies house, and even eBay and Airbnb are monitored And you really think that Digital ID is a privacy issue? Whoops.

1

3 Comments

Also, brick walls and structures generally DO NOT feature integrations with financial payment or HR systems. Software is powerful and should be created with responsibility and care. #WhatsHappeningHere

2

We recently automated our test coverage process using Claude Code agents. The key was building two specialised agents - one for writing tests, one for reviewing them - rather than using single-prompt generation. I wrote up the technical implementation, including: - How agent descriptions trigger task routing - Why tool configuration matters - The 4-step iterative process we use - Lessons learned from implementation Full breakdown here: https://lnkd.in/dgCM8XEu

11

Learn what Playwright is, why teams use it, how it compares with other E2E tools, and how to scale tests with parallel execution.

2