> Markdown version of [/jobs/ext/4156551-senior-software-engineer-l6](https://www.wearedevelopers.com/jobs/ext/4156551-senior-software-engineer-l6). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer (L6) - **Company:** Street Group - **Location:** Manchester, UK (Remote available) - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Cyber Security, Laravel, Model View Controller (MVC), AI Infrastructure, ReactJS, Vue.js, AngularJS, Amazon Simple Queue Service (SQS) - **Published:** October 8, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=42531f61d147c2c2 ## About the Role * You have deep commercial experience with PHP and Laravel (or a similar MVC framework), and you've led architecture and design across multiple teams or systems, not just within one. * You have experience working with Vue 3, React, Angular or a similar modern JS framework. * You have strong production experience with AWS. ECS, RDS, SQS, Lambda and EventBridge are advantageous, and you're comfortable shaping cost, reliability and security at estate level. * You work AI-natively by default, and you've gone beyond your own workflow to build AI tooling, agents or infrastructure that other engineers rely on. You also know how to put guardrails around it. * You turn ambiguity into direction: you're used to open-ended problems with no brief, and the solutions you ship to hard problems are the boring, maintainable kind. * You get up to speed fast. Drop you into an unfamiliar team or codebase and you're adding value in your first week. * You think in products and systems: you can see how a technical decision lands in the business, and how a change to a team or process will affect a system boundary. * You're a trusted influencer and communicator. You can align teams with competing priorities, tell leadership early when something affects customers, money or reputation, and make the engineers around you better. ## Description * Setting technical direction across a portion of the product: deciding which systems get built, how they fit together and what gets retired, while still contributing and steering the engineers around you. * Finding the problems nobody has named yet, like "something about how we do X won't survive the next year of growth", then framing them, making them tractable and taking them through to a solution across teams. * Leading technical decision making at product-area level: the shared services, platform pieces and seams between teams, and you'll own reviews for the big changes. * Getting ahead of scaling bottlenecks, operational toil and security exposure before teams feel them, using data rather than gut feel - your aim is for whole teams to ship faster quarter on quarter. * Driving the agents, shared plugins and AI infrastructure in CI and review that the whole function relies on. You'll own their governance (failure modes, drift, safe-use standards) and make build-vs-buy recommendations that inform our AI investment. * Leading on complex platform changes, major framework upgrades, security architecture, estate-level cost and reliability work - and getting multiple teams aligned on outcomes everyone can live with. * Acting as a co-owner of product outcomes: bringing proposals product adopts, often opportunities engineering spotted first, and explaining complex technical trade-offs in commercial terms leadership can act on. * Lifting engineers beyond your own team through mentoring, standards and tooling.