Vị trí Staff Backend Engineer, Architecture Engineering: Nonlinear Productivity tại GitLab

Tổng quan vị trí

Vị trí Staff Backend Engineer, Architecture Engineering: Nonlinear Productivity tại GitLab, được giữ lại từ bản ghi nguồn của nhà tuyển dụng. Hãy kiểm tra tin chính thức để xác nhận còn tuyển trước khi ứng tuyển.

Trách nhiệm

• Thiết kế, triển khai và vận hành phần mềm, hệ thống hoặc giải pháp kỹ thuật phù hợp với vai trò.
• Phối hợp với các nhóm kỹ thuật và sản phẩm trong quá trình lập kế hoạch, đánh giá và bàn giao.
• Xử lý sự cố, ghi chép quyết định và cải thiện độ tin cậy, chất lượng.

Yêu cầu

• Kinh nghiệm chuyên môn phù hợp về phần mềm, hệ thống, hạ tầng, dữ liệu hoặc kỹ thuật.
• Kỹ năng kỹ thuật, giải quyết vấn đề và giao tiếp tốt.
• Có khả năng làm việc hiệu quả trong môi trường phân tán, từ xa.

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

• Python: Proficiency in Go, Rust, or Python, with the ability to read and modify code in the .
• Go: Proficiency in Go, Rust, or Python, with the ability to read and modify code in the .
• Rust: Proficiency in Go, Rust, or Python, with the ability to read and modify code in the .
• LLM: • Experience building reliable agentic or large language model (LLM)-based systems, including multi-step orchestration, tool use, guardrails, and .
• CAN: Our Talent Acquisition team can help answer any questions about location after starting the recruiting .

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 Staff Backend Engineer, Architecture Engineering: Nonlinear Productivity position at GitLab is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “Staff Backend Engineer, Architecture Engineering: Nonlinear Productivity at GitLab, retained from the employer source record. Verify current availability on the official posting before applying.” 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 “Set the technical direction for the team's agentic systems, from how agents are orchestrated to where a step should stay human-owned, and defend those calls once they're tested against real code.”; “Discover and prioritize sources of friction across GitLab's SDLC, driving the fix — agentic, process-based, or both — from a rough hypothesis through to a shipped, measured result.”; “Work across any part of GitLab's codebase as the problem requires, since this team operates like a small, generalist group rather than one scoped to a single service.”. 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.

Phúc lợi

• Xem tin nhà tuyển dụng để biết phúc lợi và điều kiện hiện hành.

Về GitLab

The Platform Readiness team is part of GitLab Developer Experience, building internal developer tooling capability for platform readiness across GitLab's four deployment targets: Self-Managed, Dedicated, Dedicated for Government, and GitLab.com. We partner with platform teams, feature teams, and product management to ensure every feature is evaluated against platform readiness requirements before it ships.

Current challenges we're tackling:

Moving from manual coordination to embedded automation: Transitioning from manual, ad-hoc platform readiness assessments to automated, agentic evaluation while maintaining human oversight and trust

Building a structured, machine-readable requirements body: Evolving the platform requirements schema to capture the full scope of platform readiness concerns across all domains and platforms

Making platform readiness native to the tools feature teams already use: Enabling platform teams to contribute domain expertise and validation logic without requiring deep Platform Readiness infrastructure knowledge

Building the measurement systems to know we're working: Creating observability and evaluation frameworks that give us confidence in agentic-workflow decisions and surface failures early

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

Việc làm liên quan

• Kỹ sư Backend cấp cao, Architecture Engineering: Nonlinear Productivity tại GitLab — GitLab
• Vị trí Senior Software Engineer (Backend) tại TeamSnap — TeamSnap
• Kỹ sư backend cấp Staff, an toàn người dùng tại Reddit — Reddit
• Kỹ sư backend an ninh bên ngoài cấp cao tại Horizon3 — Horizon3
• Kỹ sư Backend cấp cao cho trải nghiệm nhân viên hỗ trợ tại Grab — Grab
• Kỹ sư phần mềm Backend cấp cao cho Agent Experience tại Grab — Grab