Software Engineer

We are Printed.com, one of the largest and fastest growing on-line print shops in the UK. We are filled to the brim with a passionate team who are mad about printing, designing, building and growing the business. In the office you’ll find that we are forward-thinking, with a mission to be creative, innovative and to help our customers.

We are constantly investing in new products and using technology to improve how we increase our market share and take advantage of new opportunities. Catch us in our production space and you will find a fast-paced, dedicated team who endeavour to reach perfection for our customers.

We’re a growing company with offices in London and Newcastle, looking for employees that are equal parts dynamic and enthusiastic. People brimming over with new, original ideas that they just can’t wait to share with their team and bring to life.

We are looking for a Software Engineer to join our Engineering team as we scale our platform across UK and US markets. Reporting our Technical Engineering Manager, you'll work across a mix of PHP (Symfony/Laravel) applications running on AWS (EC2 and EKS), contributing hands-on to feature development and platform improvements. This role suits someone building their confidence owning well-scoped problems, who's comfortable asking the right questions when something's unclear, and who's keen to develop their skills with support from senior engineers. You'll be trusted to make sound technical decisions within your area, execute reliably against a spec, and start contributing to the team's engineering practices as you grow into a more senior role.

This is a hybrid role with a minimum of 2 days required in our Cramlington office.

Ownership & Initiative

Take ownership of well-defined problems and features, escalating ambiguity or unclear requirements to a Senior Engineer or Manager rather than resolving it unsupported. Comfortable digging into a bug beyond the surface symptom, with support available when the root cause isn't obvious.

Multi-Project Delivery

Work across a small number of concurrent workstreams — typically feature development alongside platform or infrastructure tasks — managing your own time and flagging early when priorities conflict, rather than resolving trade-offs independently.

Engineering Best Practices

Follow and reinforce engineering best practices (code review standards, testing, CI/CD, documentation) consistently in your own work and give constructive code review feedback to peers and junior engineers.

Process & Ways-of-Working Adoption

Adopt new tools, processes, and ways of working as the engineering function matures, and help surface friction or confusion you hit along the way so it can be fed back to the team leads driving the change.

Mentoring & Technical Guidance

Support junior engineers through pairing and code review and be receptive to mentoring and technical guidance from senior engineers as you build toward more autonomous ownership.

·         Our stack is PHP (Symfony/Laravel) with Vue.js front ends - but we're open to engineers from other frameworks (e.g. Rails, Django, .NET) or other JS frameworks (React, Angular) who can demonstrate solid fundamentals and pick things up quickly

·         Comfortable working across JavaScript, SCSS, and Twig as part of day-to-day full-stack delivery, or building toward that across a similar front-to-back stack

·         Working knowledge of AWS (EC2, EKS/containers, RDS, or similar services), or strong general cloud fundamentals with willingness to build AWS-specific depth

·         Good exposure to DevOps, platform, or infrastructure work

·         Comfortable managing your own priorities across a small number of concurrent tasks

·         Clear, confident communicator, comfortable asking questions and flagging blockers rather than guessing

·         Open to pairing with and learning from other engineers; some experience supporting junior engineers or interns is a plus

·         Familiarity with observability tooling (e.g. Grafana, Prometheus/Mimir) is a plus

·         Developing a pragmatic sense of trade-offs between speed, technical debt, and long-term maintainability

·         A proactive problem-solver - comfortable taking a well-defined problem and running with it, and knowing when to ask for direction on the ambiguous parts

·         Approaches technical disagreement collaboratively - pushes back on ideas, not people, and is open to being persuaded by a stronger argument

·         Beginning to factor cost into technical decisions, with guidance from senior engineers on the bigger architectural calls

·         Some exposure to legacy or end-of-life systems is useful, though not expected to lead modernisation efforts independently

·         Security-conscious in day-to-day development (access control, dependency hygiene, data handling), with senior engineers available for the trickier calls