Résumé du poste par JobGrid
Lead Engineer at Patchstack: Remote, Royaume-Uni; Temps plein; IT; Engineering Manager. JobGrid adds normalized role facts, source context, and a path to the employer application page so candidates can compare the listing before applying.
- Location and workplace: Remote, Royaume-Uni
- Role classification: IT, Engineering Manager, Temps plein
- Source freshness: checked by JobGrid on 2026-05-31.
- Application path: candidates continue to the employer application page with non-personal referral tags.
As a Lead Engineer, you'll lead a small squad (typically 3 engineers) to deliver a clear mission end-to-end: setting direction, making pragmatic technical decisions, and ensuring the team ships reliably.
This is a hands-on squad leadership role: you will write code, review code, own architecture choices, and be accountable for outcomes. You'll partner closely with Product (PM) and Design, and coordinate where needed with Security Research and Ops/Infra.
In our model, squads are built around missions — Flow (Industrialisation) and Ecosystem (Distribution), as described in the pipeline above. Your exact squad mission will be confirmed during hiring, but the leadership expectations are consistent across both.
Tech stack
- Backend: Laravel / PHP (primary), with supporting services and tooling
- Frontend: Vue.js / Inertia.js, ShadCN
- Infrastructure: AWS, Docker, GitHub Actions CI/CD
- Data & intelligence: MySQL, automated vulnerability pipelines
- AI tooling: Claude, MCP integrations, AI-assisted development workflows
- Practices: ADRs, small PRs, trunk-based development, feature flags, observability-first
Responsibilities
Squad outcomes & delivery leadership
- Own your squad's mission and delivery cadence: define milestones, ensure steady shipping, and remove blockers.
- Translate high-level goals into a delivery plan: scope, sequencing, trade-offs, and risks.
- Drive a high-quality execution loop: clear tickets/specs, small PRs, fast reviews, strong release habits.
- Maintain a predictable operating rhythm: planning, weekly goals, retros, and continuous improvement.
Technical direction & architecture
- Make and communicate pragmatic architectural decisions, guided by our technical principles: safe, reversible actions over brittle one-way changes; explainable decisions over opaque scoring; and a single intelligence loopacross multiple delivery surfaces.
- Set standards for code quality, testing strategy, observability, and performance.
- Use ADRs when decisions have long-term impact; ensure the "why" is documented and shared.
- Own technical debt management: pay it down deliberately while maintaining delivery speed.
- Leverage AI tools and automation to accelerate development, testing, and operational workflows — and set the standard for the squad.
- Contribute to closing the feedback loop: ensuring production telemetry and partner signals flow back to inform research priorities and pipeline quality.
Hands-on engineering
- Build and maintain Laravel-based services and web applications (plus supporting tooling/services).
- Ship secure, testable, performance-aware code; keep production stable.
- Lead by example in code reviews, refactoring, and incident response when needed.
- Experiment with new tools, frameworks, and AI-assisted development practices — validate what works and share learnings.
Collaboration & cross-functional alignment
- Partner with Product and Design to shape solutions early (not just implement tickets).
- Coordinate with Security Research where domain knowledge is needed to ship correct intelligence flows and mitigation-related work.
- Work with Ops/Infra on reliability, scaling, deployments, and platform evolution.
People leadership (small-team, high impact)
- Create clarity for your squad: who owns what, what "done" means, and how quality is measured.
- Coach engineers through pairing, reviews, and feedback — raising the bar without creating bureaucracy.
- Support hiring and onboarding when your squad grows.