Remote-First Software Engineer III — Web & AWS

Remote-First Software Engineer III — Web & AWS

Full-Time 45000 - 55000 £ / year (est.) Remote
The Economist

At a Glance

  • Tasks: Join our Web team to enhance economist.com and improve user engagement.
  • Company: The Economist, a leading global media organisation with a collaborative culture.
  • Benefits: Remote-first work, competitive salary, and opportunities for professional growth.
  • Other info: Be part of a dynamic team that values innovation and creativity.
  • Why this job: Make a real impact on a fast-paced web experience while working with talented professionals.
  • Qualifications: Mid-level software engineering skills and a passion for quality and performance.

The predicted salary is between 45000 - 55000 £ per year.

The Economist is seeking a mid-level software engineer to join our Web team.

You will help grow economist. com into a fast, intuitive web experience while enabling discovery and engagement with our journalism.

You’ll join a collaborative, cross-functional group and contribute from week one, taking ownership, delivering high-quality software, and supporting performance, accessibility, and observability across our applications.

Remote-First Software Engineer III — Web & AWS employer: The Economist

The Economist is an exceptional employer, offering a dynamic work culture that fosters creativity and collaboration among its talented team. With a strong focus on professional development, employees have ample opportunities to grow their skills while working on high-profile global events that make a significant impact. Located in a vibrant city, the company provides a stimulating environment where innovation thrives, making it an ideal place for those seeking meaningful and rewarding employment.

The Economist

Contact Details:

The Economist Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Remote-First Software Engineer III — Web & AWS

✨Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at The Economist or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

✨Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to The Economist.

✨Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like The Economist.

✨Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like The Economist that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Remote-First Software Engineer III — Web & AWS

Web Development
AWS
Software Engineering
Performance Optimisation
Accessibility Standards
Observability
Collaboration

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at The Economist.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at The Economist and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at The Economist

✨Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

✨Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If The Economist uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

✨Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

✨Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.