← Tất cả việc làm

Kỹ sư backend cấp cao, Agent Experience tại Grab

Đã xác nhận còn mở

Grab tuyển kỹ sư backend cấp cao cho công cụ nội bộ của nhân viên hỗ trợ hành khách, tài xế và đối tác bán hàng. Hệ thống Agent Experience cần hoạt động ổn định, cung cấp dữ liệu chính xác để xử lý yêu cầu người dùng.

Grab logoGrab
Địa điểm
TP. Hồ Chí Minh, Việt Nam
Loại hình
Full-time
Công nghệ
Python, Java, C++, C#, Node.js, Go

Tạo hồ sơ ứng tuyển miễn phí — Lưu kỹ năng và dự án trong một hồ sơ có thể dùng lại. Hồ sơ mặc định riêng tư; bạn quyết định khi nào chia sẻ. Ứng tuyển tin này trực tiếp với nhà tuyển dụng.

Tổng quan vị trí

Grab tuyển kỹ sư backend cấp cao cho công cụ nội bộ của nhân viên hỗ trợ hành khách, tài xế và đối tác bán hàng. Hệ thống Agent Experience cần hoạt động ổn định, cung cấp dữ liệu chính xác để xử lý yêu cầu người dùng.

Trách nhiệm

  • Phát triển dịch vụ Go và kiến trúc nhằm tăng tính sẵn sàng, khả năng mở rộng, giảm độ trễ và cải thiện hiệu quả vận hành.
  • Lập kế hoạch dung lượng, tối ưu hiệu năng, thử nghiệm tính năng và xử lý sự cố sản xuất khi trực hệ thống.
  • Rà soát thiết kế, mã nguồn, phối hợp với nhóm hạ tầng và hướng dẫn kỹ sư khác.

Yêu cầu

  • Có bằng cấp công nghệ liên quan, ít nhất năm năm làm phần mềm phân tán và nền tảng thuật toán, cấu trúc dữ liệu vững.
  • Có kinh nghiệm vận hành dịch vụ web quy mô lớn, hiểu hiệu năng, mở rộng hệ thống và sẵn sàng lập trình bằng Go.
  • Giao tiếp tiếng Anh trong công việc; hiểu thành phần bên trong hệ thống và mạng là lợi thế.

Công nghệ trong công việc

  • Python: Python Java C++ C# Node.js .
  • Java: Python Java C++ C# Node.js .
  • C++: Python Java C++ C# Node.js .
  • C#: Python Java C++ C# Node.js .
  • Node.js: Python Java C++ C# Node.js .
  • Go: Python Java C++ C# Node.js .
  • C: Python Java C++ C# Node.js .
  • Golang: understanding of systems internals and networking are a plus Strong understanding of system performance and scaling Proficient in English communication You can be a good coder in any language (C++, C, Java, Scala, Rust, Haskell, OCaml, Erlang, Python, Ruby, PHP, Node.JS, C# .
  • Rust: understanding of systems internals and networking are a plus Strong understanding of system performance and scaling Proficient in English communication You can be a good coder in any language (C++, C, Java, Scala, Rust, Haskell, OCaml, Erlang, Python, Ruby, PHP, Node.JS, C# .
  • Ruby: understanding of systems internals and networking are a plus Strong understanding of system performance and scaling Proficient in English communication You can be a good coder in any language (C++, C, Java, Scala, Rust, Haskell, OCaml, Erlang, Python, Ruby, PHP, Node.JS, C# .
  • PHP: understanding of systems internals and networking are a plus Strong understanding of system performance and scaling Proficient in English communication You can be a good coder in any language (C++, C, Java, Scala, Rust, Haskell, OCaml, Erlang, Python, Ruby, PHP, Node.JS, C# .
  • Scala: understanding of systems internals and networking are a plus Strong understanding of system performance and scaling Proficient in English communication You can be a good coder in any language (C++, C, Java, Scala, Rust, Haskell, OCaml, Erlang, Python, Ruby, PHP, Node.JS, C# .
  • CAN: understanding of systems internals and networking are a plus Strong understanding of system performance and scaling Proficient in English communication You can be a good coder in any language (C++, C, Java, Scala, Rust, Haskell, OCaml, Erlang, Python, Ruby, PHP, Node.JS, C# .

Hướng dẫn đánh giá mức độ phù hợp (tiếng Anh)

Phân tích dựa trên yêu cầu và trách nhiệm trong tin tuyển dụng của nhà tuyển dụng.

Understanding the scope. This Senior Software Engineer, Backend position at Grab is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “Grab seeks a senior backend engineer for internal tools used by support agents serving passengers, drivers and merchants. The Agent Experience systems must remain reliable and accurate while helping agents resolve user…” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the software engineering area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Develop Go services and architecture for availability, scale, low latency and operational efficiency.”; “Plan capacity, tune performance, prototype product features and diagnose production incidents during on-call work.”; “Review designs and code, work with infrastructure teams and mentor other engineers.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “A relevant computing degree, at least five years in distributed software systems and strong algorithms and data structures.”; “Experience operating large-scale web services, understanding performance and scaling, and willingness to develop in Go.”; “Professional English communication; systems internals and networking knowledge are useful.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are Python, Java, C++, C#, Node.js, Go. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a named tool, explain the closest related system you have worked with and how you would ramp up; do not relabel that experience as direct production use. If the source describes technologies beyond this list, prioritize its exact wording.

Evidence to put in the application. Tailor the first half of your CV to the named work instead of using a generic summary. Lead with two or three outcomes that match the responsibilities, and include enough context to show complexity, scope and your role. Add technical detail where it substantiates an outcome: architecture, interfaces, data or traffic scale, test strategy, deployment approach, incident response or collaboration, as relevant to your real projects. Keep confidential employer information private; describe the problem and your contribution without disclosing protected data. If the role is in software engineering, make the connection explicit between your past work and this position’s actual requirements. A short, specific cover note can explain why this team and scope fit your experience, but it should not repeat the CV.

Interview preparation. Build a small set of stories from the employer’s stated duties: one about delivering a difficult piece of work, one about diagnosing a failure or unexpected result, and one about working through a design or prioritization decision. Use the examples to explain your reasoning, not just the final answer. Be ready to discuss the technical depth behind any claim on your CV and to draw boundaries around what you personally did. Questions worth preparing include how success is measured in the first months, which responsibility currently takes the most team capacity, how work is reviewed and released, and which technical constraints shape decisions. These are preparation prompts, not claims about Grab’s interview process; the posting does not establish the number or format of interview rounds.

Location and employment details. The supplied listing describes the work arrangement as not specified; the displayed location is HCMC, Vietnam. The employer’s source is the authority for where applicants may live, travel expectations, work authorization, compensation, schedule and employment type. Confirm each point before investing time in an application, especially if the role serves a specific territory or customer group. This page does not infer that “remote” means work from any country. Where the official post gives a region, travel requirement or language requirement, use that exact condition when deciding whether the role is practical for you. Where a detail is absent here, use the linked employer posting to verify it.

Questions to resolve with the employer. Use the source posting to separate confirmed facts from unknowns. Ask which outcomes define success for this role, what the team expects the hire to own directly, how collaboration works across functions or locations, and what support is available for onboarding. For Senior Software Engineer, Backend, also clarify the priority among the responsibilities listed above and how the named qualifications are evaluated in practice. If compensation, benefits, reporting line, team size, travel or work authorization is important to your decision, request the precise terms from the employer; this page does not fill in missing terms. Recheck the source listing immediately before applying because vacancies and requirements can change.

Phúc lợi

  • Khi được nêu trong tin, Grab cung cấp bảo hiểm nhân thọ và y tế, phúc lợi linh hoạt, nghỉ phép cho cha mẹ và sinh nhật, cùng chương trình hỗ trợ nhân viên; xác nhận điều kiện áp dụng tại địa phương với nhà tuyển dụng.

Về Grab

Grab vận hành các dịch vụ số tại Đông Nam Á. Vị trí này thuộc bộ phận kỹ thuật của công ty tại Việt Nam.

Trang web nhà tuyển dụng

Cách ứng tuyển

Kiểm tra tin gốc và gửi hồ sơ trực tiếp qua trang tuyển dụng của nhà tuyển dụng.

Xem tin gốc và ứng tuyển

Nguồn được kiểm tra: 2026-10-11

Khám phá việc làm theo danh mục

Việc làm liên quan