Skip to main content
Back to Jobs

Backend Engineer, AI (Agent Systems)

Build and operate backend systems for AI-powered features in production

As a Backend Engineer, AI at Bjak, you will build and operate production systems that turn model capability into fast, stable, observable APIs used across mobile and desktop clients. You will design inference pipelines, orchestration layers, and service boundaries around models while owning production concerns like monitoring, logging, alerting, and incident response. Your work focuses on optimizing latency and throughput across inference, cac...

Why This Role?

Direct impact on real-world AI assistant reliability and user experience

Key Responsibilities

  • Build and operate backend systems serving AI-powered features in production
  • Design inference pipelines, orchestration layers, and service boundaries around models
  • Own production concerns: monitoring, logging, alerting, and incident response
  • Optimize latency and throughput across inference, caching, batching, and streaming
  • Debug distributed systems under load to ensure reliability
  • Iteratively improve system performance based on real usage patterns

Requirements

  • Strong backend engineering fundamentals in production environments
  • Experience running high-throughput, low-latency services
  • Familiarity with AI inference patterns (LLMs, embeddings, multimodal)
  • Comfortable debugging distributed systems under load
  • Bias toward shipping and learning from production behavior

Required Skills

pythonnode.jspytorchkubernetesdockerbackendaibackend engineeringAI inferencedistributed systemsAPI developmentperformance optimizationproduction operations

Indonesia Context

Working Hours Overlap:
Flexible — work your own hours
See remote (USD) vs local pay →
View Original Description from Ashby Job Boards

Original description from Ashby Job Boards

ABOUT A1 There are over 5 billion users using basic applications today such email, notes, tasks that are not AI-native. Our mission is to build a proactive smart assistant for everyday users to bring intelligence to conversations, errands, organising and workflows, with minimal prompting. Our product focuses on achieving high reliability for long-running workflows, persistent context, and real-world task completion. The system must handle multi-step reasoning, interact with external tools, and remain reliable despite non-deterministic model behavior. Our objective is to help users complete tasks daily enjoyable with over ~90%* reduced time.   ROLE As a Backend Engineer, AI, you own the inference and orchestration layer that powers every AI interaction in the product. Your work sits between models and users, where latency, correctness, reliability, and cost directly impact real-world experience. You will build and operate production systems that turn model capability into fast, stable, observable APIs used across mobile and desktop clients.   FOCUS - Build and operate backend systems that serve AI-powered features in production. - Design inference pipelines, orchestration layers, and service boundaries around models. - Own production concerns: monitoring, logging, alerting, and incident response. - Optimize latency and throughput across inference, caching, batching, and streaming.   IDEAL EXPERIENCES - Strong backend engineering fundamentals in production environments. - Experience running high-throughput, low-latency services. - Familiarity with AI inference patterns (LLMs, embeddings, multimodal). - Comfortable debugging distributed systems under load. - Bias toward shipping and learning from production behavior.   OUTCOMES - Backend systems run reliably at scale, handling production AI traffic with low latency and high throughput. - APIs are stable, clear, and support seamless integration with frontend and ML systems. - Production incidents are quickly detected, diagnosed, and resolved, minimizing user impact. - Iterative improvements based on real usage continuously increase system performance and reliability.   TECH STACK - Python - NodeJs - Pytorch - OpenAI / Anthropic / open-source LLMs - SQl & noSQL - Kubernetes - Docker   HOW WE WORK The best products today in the world were built by small, world class teams. We are a high talent density and hands-on team. We make decisions collectively, move at rapid speed, striking a balance between shipping high quality work and learning. Joining our team requires the ability to bring structure, exercise judgment, and execute independently. Our goal is to put in hands of our users a truly magical product   INTERVIEW PROCESS If there appears to be a fit, we'll reach to schedule 3, but no more than 4 interviews. Applications are evaluated by our technical team members. Interviews will be conducted via virtual meetings and/or onsite. We value transparency and efficiency, so expect a prompt decision. If you've demonstrated the exceptional skills and mindset we're looking for, we'll extend an offer to join us. This isn't just a job offer; it's an invitation to be part of a team that's bringing AI to have practical benefits to billions globally.

Salary Context

Similar Engineering roles on LokerDollar pay around $160k/yr (range $1.8k–999.999k/yr, n=601 active listings).

Hiring at Bjak

Bjak has 134 other active roles on LokerDollar and has been hiring here since May 7, 2026 — across Engineering, AI, Marketing.

View all Bjak openings →

Openness not stated by employer — check the listing

Company
Bjak
Source
Ashby Job Boards
Salary
Job Type
full time
Location
Remote
Category
Seniority
mid
PostedVerified
Jun 2, 2026

Share this job

Help a friend find their next remote role.

Frequently asked questions

Is Backend Engineer, AI (Agent Systems) at Bjak a remote job?
This role is based in Remote. See the listing for remote/onsite details.
What type of employment is Backend Engineer, AI (Agent Systems) at Bjak?
This is a full time position.
How do I apply?
Click the "Apply" button on this page to go to the official application at Bjak.

Explore related

Market data & reports

Salary & skill-demand research built from our own listings data.

From the blog