Get a reply from this employer — a resume and cover letter tailored to exactly what they’re hiring for.
Nysonian in Islamabad is seeking a Senior AI Engineer to own the design and production operation of our agentic AI systems end to end. You will manage models, orchestration, tool calls, guardrails, and the cloud infrastructure they run on, while collaborating across our commerce platform and internal CRM.
This builder role emphasizes architectural ownership over prompts, with responsibilities spanning multi-agent orchestration, tool integration (Shopify GraphQL, ShipHero, Gorgias, Klaviyo), and
Automations · Full-time · In-Person (Islamabad, PK) · Hours 6pm - 2am PKT
About Nysonian
Nysonian builds the next generation of global lifestyle brands, shaping how people travel, move, and live. We go beyond creating great products to build experiences that elevate everyday life and empower people around the world.
Our Fast-Growing Portfolio Includes:
With $350M+ in revenue, 400+ teammates across 8 countries, and 1M+ customers worldwide, we are shaping the brands that will define the next decade.
Core Values: Winners’ Mindset | Speed with Purpose | Thoughtful Innovation | Genuineness | No Ego, Full Ownership
The Opportunity
You'll own the design and production operation of our agentic AI systems end to end; the models, the orchestration, the tools they call, the guardrails around them, and the cloud infrastructure they run on. You'll also work inside our commerce platform and internal CRM, because an agent is only as good as the systems it can reach.
This is a builder role with real architectural ownership, not a prompt-tweaking role.
What You'll Own
Skills & Qualifications
4+ years building and operating production software, with real ownership of what happens after deploy. Strong AWS (EC2, Lambda, S3, RDS, IAM, VPC, queues). GPU workloads and self-hosted inference are a plus.
Containers, CI/CD, infrastructure-as-code, logging and metrics (Prometheus/Grafana or equivalent).
You have shipped agentic systems that run in front of real users, not just in a notebook. Deep practical experience with tool calling and function calling, MCP, structured outputs and schema validation, and recovering gracefully when a model returns something malformed.
Multi-agent orchestration patterns, state and memory management, context-window budgeting, and async/event-driven design.
Evaluation discipline — you can describe how you measured whether an agent got better.
Cost and latency engineering: caching, batching, model routing, token economics.
Serious prompt engineering across large, versioned, multi-section system prompts. Guardrails, grounding, hallucination mitigation, and output filtering as engineering problems with tests, not vibes.
LLM security: prompt injection, jailbreaks, data exfiltration through tools, secrets handling. OWASP LLM Top 10 familiarity.
Fine-tuning and adaptation (LoRA/QLoRA, distillation, preference tuning) — or a clear-eyed sense of when not to bother.
You can take a fuzzy business problem and produce an architecture: what's a model call, what's deterministic code, what's a tool, where a human belongs, and what happens when each part fails.
Sound instinct for the deterministic/model boundary. A rule that can be a regex should not be a paragraph of prompt, and a judgement call should not be a rule.
This is the part we care about most, because it's where AI systems in commerce actually hurt you. You treat a success status as a claim, not a fact. The expensive failures in this domain are silent: a tool that returns 200 and writes nothing, a token that was revoked last week, a workflow whose error handler swallows the error and reports "ok". You verify the side effect, not the exit code.
You can size an experiment. You know why a 3-point movement in a daily metric is usually noise, what a matched-window baseline is, and roughly how many conversations per arm you need before a prompt change can be called an improvement. You've migrated a production system across model versions and can say how you proved behaviour didn't regress.
Debugging discipline in a stack where the same input doesn't always produce the same output: tracing, replaying real traffic, and reproducing a failure before fixing it.
Hands-on MERN (MongoDB, Express, React, Node.js) in a production commerce or enterprise context; comparable to our Nysonik CRM. Comfortable with REST and GraphQL integrations, webhooks, queues, and third-party APIs that fail in interesting ways.
You track model releases, benchmarks, and the research that matters, and you can tell
the difference between a genuine capability shift and a launch post. We'll expect you to bring that to how we build.
Nice To Have
Why You’ll Love Working at Nysonian
Culture
Growth & Development
We are proud to be an equal opportunity employer. All qualified applicants will receive consideration without regard to race, color, sex, religion, gender, marital status, national origin, genetics, disability, age, veteran status or other characteristics.