Forward Deployed Engineer

Client Discovery & Requirements
•Own the technical arc of a client engagement, from scoping the problem through to the system running in production on their floor.
•Embed at client sites and run working sessions with founders, operators, and floor staff to map their actual workflows — not what they think they need, but what they actually do.
•Translate ambiguous, often contradictory business problems into clear, scoped technical requirements, and make the architectural calls that hold up at the client’s scale, not just in a demo.
•Identify the fastest path to a working pilot: what to build first, what to defer, and where the real leverage is.
•Represent Lecxe professionally in every client interaction — you are often the only Lecxe person they see.
On-Site Engineering & Deployment
Build the system yourself, across whatever the stack calls for — Next.js on the frontend, FastAPI on the backend, Postgres for data, LangGraph for agent workflows.
•Handle integrations with the systems clients actually use: Tally, basic ERPs, WhatsApp Business API, payment gateways, email.
•Deploy into the client’s environment: configure infrastructure, migrate data, test with real users, and stay until it works.
•Set up evaluations that meaningfully measure whether the system is doing its job — not vanity metrics — and iterate based on what the data shows.
•Debug production issues in real time, with the client watching. Stay calm, diagnose fast, fix it.
Communication & Coordination
•Serve as the live feedback loop between the client and Lecxe’s core engineering team — surface blockers early, communicate scope changes clearly, and never let a surprise reach the Product Manager without a proposed resolution.
•Train client staff on the software you deploy: non-technical users, operators, and in some cases the client’s own IT team.
•Write crisp handover notes and implementation documentation after every engagement so the next person walking into that client knows exactly what was built and why.
Continuous Improvement
•Work across engagements over time, picking up new domains, industries, and client contexts as priorities shift.
•Bring what you learn in the field back to Lecxe’s product decisions: what clients actually struggle with, what workarounds they’ve invented, and where the product needs to evolve.
•Participate in code reviews with the core engineering team and apply feedback; this role grows toward the Product Manager track.
Even Better If
•You’ve built and deployed AI agents into production where they did real work for real users, with hands-on experience in agentic frameworks (LangGraph, LangChain, or equivalent), prompt engineering, or RAG pipelines.
•You have a history of side projects, open-source contributions, or shipped products — especially the unglamorous kind that broke in production and taught you something.
•Prior exposure to client-facing work — consulting, implementation, solutions engineering, or even a founder’s office internship.