Staff Engineer / AI Builder
Free to start · No card · 5 credits the moment you sign up
Job description
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
- Design for LLM failure, not just LLM success: retries with backoff and jitter, circuit breakers, fallback models, and a clear user-facing story when something upstream degrades
Full-Stack & Platform Engineering
- Build backend services in Python and Node.js, including serverless architectures (AWS Lambda, API Gateway) that support agentic workflows
- Design DynamoDB single-table schemas — composite keys, transactional writes — for conversation state, agent memory, and session history
- Support event-driven orchestration (Step Functions, SQS, EventBridge) for asynchronous agent operations, with an eye toward reliability and clean error handling
- Contribute to frontend integration points so agentic features land cleanly for end users, and write clean, well-tested code across the stack
- Support deployment, monitoring, and production troubleshooting in cloud-native environments (AWS, Docker), with guidance from senior engineers where needed
Collaboration & Technical Leadership
- Bring informed technical judgment to architecture discussions — naming the real trade-offs of a pattern (e.g., gateway centralization vs. latency, single- vs multi-agent design) rather than defaulting to what's familiar
- Partner with product, design, and delivery leads across global teams to scope and ship features end-to-end
- Mentor other engineers on the pod and help raise the bar on agentic engineering practices, including AI-assisted development tools like Claude Code
- Own assigned features and releases end-to-end — including the unglamorous parts: debugging, hardening, and keeping production systems trustworthy
What You'll Bring
- 6+ years of professional software engineering experience, including meaningful time shipping GenAI/LLM-powered systems in production — not just prototypes
- Real, hands-on depth in agentic AI: reasoning loops, tool/function calling, multi-agent orchestration, and a considered point of view on when single-agent design beats multi-agent, and why
- Practical RAG expertise: chunking strategies, embeddings, vector databases (OpenSearch or similar), cosine similarity search, and re-ranking — you can explain the mechanism, not just the terminology
- Experience building evaluation and observability for LLM systems: golden datasets, LLM-as-judge, RAGAS or comparable metrics, and tracing tools like LangFuse/LangSmith
- Strong prompt engineering skills — you can write a production system prompt with real structure and constraints on request, not just describe the concept
- Hands-on experience with the AWS GenAI stack: Bedrock, Agent Core, Lambda, DynamoDB (single-table design), S3, SQS, EventBridge, Step Functions
- Strong Python and Node.js skills, with experience building full-stack applications and RESTful APIs
- Solid understanding of production reliability patterns for LLM-backed systems: retries/backoff, circuit breakers, fallback models — as a bundle, not a single tactic
- Experience with containerization (Docker) and cloud-native deployment
- Comfort owning ambiguous, integration-heavy problems, and the ability to go a level deeper when someone pushes on your answer instead of staying abstract
Helpful Extras and Unique Skills
- Direct experience with Amazon Bedrock Agent Core — agent registration, MCP tool wiring, memory/session management, gateway provisioning
- Experience in a regulated or high-stakes domain (education, healthcare, financial services) where evaluation rigor and reliability carry real consequences
- Familiarity with workflow orchestration tools such as Step Functions, Sequencer, or similar state-machine-based systems
- A point of view on LLM observability tooling, gained from actually running it in production rather than reading about it
Our salary range is $176,612 - $243,680 CAD
Originally posted on Himalayas
Prepare your application
Use the description above to assess your fit for Robots & Pencils. This checklist is guidance from Resumize, rather than additional requirements from the employer. Imported listings can be shortened or change after collection, so confirm the complete description and current availability before sending an application.
Match requirements to evidence
Identify the responsibilities and skills the employer explicitly names. For each important requirement, choose one example from your work, education, training, or projects. Explain what you did, how you did it, and what changed as a result. Include a measurable outcome when you can support it. If you lack a requirement, describe related experience accurately instead of adding an unfamiliar skill to your resume.
Put the most relevant examples near the top of your resume. Keep job titles, dates, qualifications, and contact details consistent across your application materials. Use the employer’s terminology when it describes your experience accurately; a copied list of keywords does not explain your contribution. A short, specific bullet is easier to review than a paragraph that mixes several unrelated duties.
Check the working arrangement
Confirm the location, schedule, employment type, and any eligibility requirements on the employer’s site. A remote label does not establish worldwide eligibility or flexible hours. If compensation, benefits, equipment, travel, or contract duration are missing from this listing, write down your questions for the recruiter. Do not assume details from another opening at the same company apply to this role.
Review before submitting
Follow the employer’s requested file format and application instructions. Open your exported resume and check that its text is selectable, its sections read in order, and its links work. Proofread names, dates, and contact information. Share confidential work samples only when you have permission, and use an anonymized example when necessary.
Submit through a trusted employer or recruiting destination. If the original listing has disappeared, search the employer’s careers page for the title rather than assuming the vacancy remains open. Save the application date, job reference, and the version of your resume you sent. Those details help you prepare for a later conversation and avoid submitting conflicting information through several job boards.
Review your resume for writing and readability feedback, or browse other openings if this opportunity is unavailable.