About the Role
The Senior Engineer / Tech Lead is the hands-on anchor of a delivery pod. You will take a defined problem, design the approach, write most of the tricky code yourself, review the rest, and lead 2–4 engineers through sprint cycles. You will deploy and operate what you build. You will also step into customer demos and working sessions when needed. This is a visibly high-ownership role — you and the Solution Architect will be the engineering face of the BU on delivery. Over 2–3 years, strong performers in this role grow into Solution Architect or Engagement Lead.
Key Responsibilities
- Own delivery of a client project or product module from design through production — architecture, implementation, deployment, and support.
- Hands-on coding across the full stack — React/Node, Python, SQL, REST APIs, Azure. At least 60% of your time is heads-down building.
- Lead a small pod of 2–4 engineers — sprint planning, daily standups, code reviews, pairing, and unblocking.
- Deploy and operate apps on the Pierian App Store — PM2, Nginx, centralised SSO, and the observability baseline.
- Debug production issues, customer-reported bugs, and data problems — calmly and with a written root-cause at the end.
- Pair with the Solution Architect on new builds — pick up patterns and feed improvements back.
- Join customer demos and working sessions alongside the Consultant/Architect — you should be able to run a technical demo solo for routine asks.
- Enforce and improve engineering hygiene in your pod — branch strategy, PR quality, test coverage, release discipline.
- Mentor 1–2 junior engineers through structured pairing and regular 1:1s.
Must-Have Requirements
- 6–8 years of full-stack engineering experience, with at least 2 years leading a small team or owning a non-trivial module end-to-end.
- Strong in at least one of Node.js / Python, plus React on the front end. SQL fluency is non-negotiable.
- Experience deploying and operating applications — Linux, PM2, Nginx, Docker, environment management, and basic monitoring.
- Hands-on usage of AI coding tools — Claude Code, GitHub Copilot, or Cursor — every day, with examples to show.
- Experience integrating with enterprise systems through APIs — SaaS platforms, ERPs, or internal services — including handling authentication, pagination, retries, and schema drift.
- Good written communication — PR descriptions, design notes, and customer-facing bug responses should be clear without a rewrite.
- Planning discipline — can size work, commit to a sprint, and deliver against it without constant reprioritisation.
- Calm under pressure — comfortable with production incidents and customer escalations.
Good to Have
- Experience with LLM integration — prompt engineering, RAG, function/tool calling, or building a Claude skill / MCP server.
- Experience with Kissflow, Zoho Qntrl, Power Automate, or another workflow/BPM platform.
- Experience with document AI, OCR, or computer vision use cases.
- Experience with Azure (Functions, App Service, AI Search, Fabric) or AWS (Lambda, ECS, RDS).
- Open-source contributions, a personal project, or a technical blog that shows how you think.
