We’re looking for technologists of all kinds to join our team. If none of the other roles we have advertised fit your interests but you’d still like to work with us, this is your entry point.
dxw has been around since 2008, working with the public and third sectors to create services and products that improve lives – things like helping to track aid spending and looking at how to improve digital collaboration between local authorities.
As well as making life better for the people who use public services and the teams that run them, we care a lot about being a great place to work and grow. Last year we became employee-owned, which means that a trust owns 90% of our shares on behalf of all current and future dxw staff, and staff get to influence the direction of the company and share in its profits. We’ve incorporated our mission and values into the trust deeds too, so dxw must also be run in the interests of the people who use the services we build.
We work remotely with people based all around the UK. We keep in touch all the time for work and for social things, and some of us get together in person in our Leeds HQ and coworking spaces in London when we can.
If you care about making public services better then dxw is the place for you!
About the role
At dxw, we develop web applications and services in multidisciplinary project teams with a range of clients in various stages of digital transformation.
You’ll work with other technologists, but also designers, user researchers, delivery managers, and many other specialisms from dxw, our partners, and our clients. Sometimes you’ll work on teams with as few as two technologists, building prototypes and exploring solutions. Other times you’ll work on large projects with four or five developers and up to ten others from a wide range of other disciplines delivering production-ready software to members of the public.
As well as delivering software, you’ll participate in user research sessions, design workshops, and a number of activities carried out by your teams to help understand the problems and design and implement the right solutions.
We work in an agile way (but we don’t follow it too strictly) and hope to inspire our clients with our practices. You and your teams will work alongside our clients to write and prioritise work. You’ll take part in sprint retrospective meetings and you’ll present your work at show and tell sessions including wider stakeholders.
Usually, we work on projects for only a small part of their lifecycle and, in those cases, you’ll take part in building a shared understanding of any work done on a service before us and when we reach the end, you’ll work with your team to hand what we’ve done over to our client or other suppliers.
We try to use the right technology for the problem at hand. Here are some of the things our teams have worked with recently:
- Ruby and Ruby on Rails
- TypeScript and Express
- Python and Wagtail
- PHP and WordPress
- PostgreSQL or MySQL
- Git and GitHub
- AWS, Docker, and Terraform
We don’t expect you to have experience with everything in that list. You can pick up particular skills and tools as you need them, and we’re eager to help you learn.
As a member of the technology discipline at dxw, you’ll be involved in team and whole company away days, regular team forums and discussions, incident reviews, and other team activities.
We publish our progression framework openly. Take a look if you’re interested in what the various roles in the technology discipline look like. We’ll encourage and support your growth as much as you need, but we also won’t push you towards advancement you don’t want.
The wide salary range isn’t normally how we do things at dxw, but until we talk to you we won’t know what role you’d fit into and how senior that role would be. In most cases, our salaries are fully transparent and visible in our progression framework, and we’re working on making all of our salaries visible across the board. If you’re concerned about salary, please reach out to us at email@example.com and we can give you an indication of what your salary would be based on the role you’re interested in.
You’ve worked on at least one software project that has had contact with real users in the real world and understand some of the challenges involved in the development of live services. You enjoy variety in your work, like the idea of working on a series of different projects in different domains, and are comfortable working through fuzzy problems.
You have a solid understanding of how to write production software, a working knowledge of Git, and know or are willing to learn some of the technologies we use as you come across them on the job. You write tests as a normal part of your work and document and share the things you learn with others.
You understand the importance of secure coding practices. All technologists receive security training when they join the team.
Our public sector work means that appointments will be made subject to a background check and you must be living in and eligible to work in the UK.
We’re committed to making our teams as diverse as we can and to creating an environment where everyone feels included and can be themselves. We welcome non-traditional paths into the development profession and aim to hire the right person for the role, not the right combination of technical keywords. We especially encourage candidates historically excluded from technology to apply, including but not limited to people of colour, women and people whose gender doesn’t always align neatly with “man” or “woman”, parents and carers, people with visible and invisible disabilities and atypical neurotypes, and people who didn’t go to university.
How will the hiring process work?
We use a system called Applied for hiring to try and remove as much bias from selecting someone as we can.
Normally, you wouldn’t need a CV, but for this general application, we need a bit more information from you to be able to understand how you might fit into the team, so we do ask for one. We’ll also ask you to write a bit about what you’re looking for in a new role.
We’ll then review your application to see if we think there might be a role at dxw for you. If we do, we’ll invite you to a conversation with one of our technology leadership team to talk about you and what you want and see if there might be a good fit.
From there, we might direct you to one of our open roles or invite you to a structured interview with 3 members of the team, who score your answers independently before any discussion with each other. We send everyone invited to interview an overview of the topics we’ll cover in advance so you can come prepared. We don’t want to catch you out; we want to find out what you know and what and how you think.
Depending on the number of applicants, we sometimes then ask promising candidates to do a 2-3 hour work simulation with a member of the team. This is a little like a code test, but is more focused on how you approach a problem than what answers you give. Our work simulations also include some one-on-one time with a different member of the team. They won’t have any part in deciding if we hire you or not, and anything you talk about would stay between you both, so please feel free to ask about whatever you’d like to know!
We send all unsuccessful candidates feedback on applications, based on the scores given in the review stages.
This process has less focus on your background and what you’ve done before than it does on what you know and can do now. But please let us know if you think we’ve missed the mark or can make it better by emailing Ellie, our HR Administrator, at firstname.lastname@example.org. Your comments will be kept anonymous.
- Annual £1000 personal learning and development allowance
- Interest-free season ticket loans, electric vehicle and cycle to work schemes
- Up to 18 weeks of paid parental leave depending on your situation
- 25 days holiday plus bank holidays
- Pension with up to 5% matching contribution from dxw
- Flexible working to support your wellbeing and personal commitments
- Macbook and home office setup budget