Robots and Pencils · posted · checked
Staff Engineer / AI Builder – NYC
AWSDockerNode.jsPythonOn-site · New YorkStaff+
Who can apply
On-site · New York
Location: New York, NY
We’re looking for a Staff AI Builder to lead the design and delivery of AI/ML systems. This role is ideal for an experienced engineer who thrives on architectural decisions, can confidently own systems end-to-end, and contributes to technical leadership across the team.
In this role, you will work as a key technical leader on a cross-functional team, defining AI architecture, leading model development and optimization, and solving challenging integration problems. You’ll be joining real, in-flight work where reliability, security, and scalability are critical. You’ll establish engineering standards, raise the bar on how we build AI systems, and contribute to the technical decisions that shape how our AI work scales over time.
Why This Role Matters
At Robots & Pencils, we design AI systems for a human world. Our name says it all. Robots and pencils means engineering paired with creativity, because every agent we ship has to work for real people in real workflows. That balance is baked into how we operate.
Every role here contributes directly to that mission. Here, you shape how AI systems integrate into enterprise operations, how teams move at real velocity, and how products create measurable impact for clients and the people they serve. We ship production-ready AI in 30 to 45 days. That pace demands people who take ownership, lead with craft, and care deeply about what they put their name on.
What You'll Do
Agentic & GenAI Engineering
Design and build agentic workflows — reasoning loops, tool/function calling, and orchestration across single- and multi-agent architectures — with clear judgment on which pattern fits the problem and which doesn't
Build and maintain RAG pipelines: chunking strategy, embeddings, vector search (OpenSearch), re-ranking, and staleness/refresh handling for dynamic knowledge sources
Integrate with AWS Bedrock and Agent Core, including MCP-based tool design — writing tool descriptions precise enough that an orchestrator routes correctly every time
Write and iterate on production system prompts — structured role framing, output constraints, and few-shot design — not just prompt tinkering
Build eval and observability into every agent you ship: golden datasets, RAGAS-style metrics, LLM-as-judge (as both a runtime guardrail and an offline eval), and tracing via LangFuse/LangSmith or equivalent