Peran Anda akan membantu tim Firefox DOM Core meningkatkan kesehatan area Session History. Anda akan menulis pengujian untuk meningkatkan cakupan serta memperbaiki pengujian dan/atau masalah demi meningkatkan ketepatan Gecko. Tanggung jawab Menulis Web-Platform tests untuk meningkatkan cakupan, serta Gecko mochitests jika diperlukan. Memperbaiki masalah dan membuat pengujian berhasil agar ketepatan Gecko meningkat. Menindaklanjuti code review bersama pemilik modul Gecko yang relevan dan melakukan iterasi hingga perubahan berhasil di-landing. Definisi selesai Cakupan pengujian Session History dan ketepatan kode di Gecko meningkat, yang diukur berdasarkan jumlah kasus pengujian yang berhasil, sehingga para senior engineer tim dapat refocus pada keamanan, performa, dan proyek strategis. Kualifikasi yang diperlukan Pengalaman yang luas dalam basis kode browser engine atau otomasi untuk browser engine, idealnya Firefox/Gecko. Kemampuan yang solid dalam JavaScript dan penerapannya untuk menulis pengujian otomatis. proficiency? "Penguasaan dan pengalaman dalam mengembangkan perangkat lunak menggunakan C++." "Kemampuan debugging yang kuat dalam basis kode yang matang dan besar." "Nyaman bekerja secara terbuka, termasuk menangani bug publik, code review, dan upstream landing." Kualifikasi yangpreferred Kontribusi sebelumnya kepada Gecko atau browser engine utama lainnya. familiarity. "Familiaritas dengan standar web dan Web Platform Tests." Need fix mistakes from my own draft. Ensure all. "Proficiency" translated_clean. "upstream landing" no translation perhaps retain technical. "jumlah kasus" source says measured by passed test cases but no number; "jumlah" is implied, adding? "measured by passed test cases" could say "dengan ukuran berupa kasus pengujian yang berhasil" without adding count. Better preserve: "diukur melalui kasus pengujian yang berhasil". We shouldn't say jumlah maybe okay but added. Let's formulate. Potential issue "Javascript" source capitalization is Javascript, title JavaScript. User asks preserve facts not exact string. Standard name JavaScript. Need perhaps translate title too? Final likely include title and company? They gave title and company. Request translate description. Could include title perhaps. We should not invent. No location. It says ringkasan situs agregator. A good output can begin "Senior Contract..." and "Mozilla". But source description has The role etc. The title/company may be metadata. They ask "Terjemahkan deskripsi lowongan berikut", likely output should include full translated description, maybe title not necessary. However preserving title might be useful. No markdown means plain lines. Could state title in translated form. But "Contract" ambiguity: position likely contract, perhaps "Senior Contract C++ / JavaScript Software Engineer (Browser Engine)" title. Translate as "Senior Contract C++ / JavaScript Software Engineer (Browser Engine)" leaving Contract? Maybe Bahasa Indonesia natural: "Senior Contract Software Engineer C++/JavaScript (Browser Engine)". It doesn't make fact from company. Could include. Need ensure no "lowongan" perhaps. Let's make clean final: Senior Contract Software Engineer C++/JavaScript (Browser Engine) Mozilla Peran ... Would retaining "Senior Contract" maybe not fully translated. "Senior Contract" in tech hiring could mean contract role. "Senior Engineer Perangkat Lunak Kontrak C++/JavaScript (Browser Engine)" natural. But if exact title matters, maybe leave title original? The instruction translates description, not necessarily title. Since title included separately, likely expected translation includes role title. In Indonesian job aggregators, "Senior Contract C++ / JavaScript Software Engineer (Browser Engine)" perhaps "Senior Contract C++ / JavaScript Software Engineer (Browser Engine)". No need force. "Contract" as an adjective perhaps "Kontrak" could alter title. Better "Senior Kontrak..." but strange. Could say "Senior Contract C++ / JavaScript Software Engineer (Browser Engine)" untouched while body translated. Yet ask translate. Hmm. No numerical data. "browser-engine codebase" = basis kode browser engine. "automating for a browser-engine" = mengotomasi sesuatu untuk browser engine? Original says "or in automating for a browser-engine" means automation for browser engine. Translate accurately: "pengalaman substansial dalam basis kode browser engine atau mengotomasi proses untuk browser engine". Fine. "comfort working in the open" = nyaman bekerja secara terbuka, dengan public bugs etc. "upstream landing" perhaps "penempatan perubahan di hulu" but natural? Better retain technical terms in parentheses? "kemampuan bekerja dengan comfortable..." No promotions. "Definition of done" perhaps "Definition of Done" standard. But translate heading "Definisi penyelesaian". "allowing the team’s senior engineers to focus on security, performance and strategic projects." "sehingga engineer senior tim dapat memusatkan perhatian pada keamanan, performa, dan proyek strategis." Great. "Fix the problems and pass the tests" = memperbaiki masalah dan memastikan seluruh pengujian berhasil? "pass the tests" means make tests pass, not all perhaps. "memperbaiki masalah dan membuat pengujian berhasil". Good. "iterate to landing" = melakukan iterasi hingga perubahan berhasil di-landing. Fine. "Web-Platform tests" source capitalization and "Web Platform Tests" distinct. Use exact names. Should use "C++" unchanged. No numbers. Need only text, no markdown. Plain heading is okay, no bullets? Source list can use lines; no markdown means avoid bullets maybe paragraph sentences. Let's produce paragraphs, no formatting markupSenior Contract Software Engineer C++/JavaScript (Browser Engine) Mozilla Peran Anda akan membantu tim Firefox DOM Core meningkatkan kesehatan area Session History. Anda akan menulis pengujian untuk meningkatkan cakupan, serta memperbaiki pengujian dan/atau masalah demi meningkatkan ketepatan Gecko. Tanggung jawab Menulis Web-Platform tests untuk meningkatkan cakupan, serta Gecko mochitests jika diperlukan. Memperbaiki masalah dan membuat pengujian berhasil demi meningkatkan ketepatan Gecko. Menindaklanjuti code review bersama pemilik modul Gecko yang relevan dan melakukan iterasi hingga perubahan berhasil di-landing. Definisi penyelesaian Cakupan pengujian Session History dan ketepatan kode di Gecko meningkat, yang diukur melalui kasus pengujian yang berhasil, sehingga engineer senior tim dapat memusatkan perhatian pada keamanan, performa, dan proyek strategis. Kualifikasi yang diperlukan Pengalaman substansial dalam basis kode browser engine atau mengotomasi proses untuk browser engine, idealnya Firefox/Gecko. Kemampuan yang solid dalam JavaScript dan penerapannya untuk menulis pengujian otomatis. Penguasaan dan pengalaman dalam mengembangkan perangkat lunak menggunakan C++. Kemampuan debugging yang kuat dalam basis kode yang matang dan besar. Nyaman bekerja secara terbuka, termasuk menangani bug publik, code review, dan upstream landing. Kualifikasi yang preferred Kontribusi sebelumnya kepada Gecko atau browser engine utama lainnya. Familiaritas dengan standar web dan Web Platform Tests.

Senior Contract C++ / JavaScript Software Engineer (Browser Engine)

Deskripsi Pekerjaan

Ringkasan

Lowongan Terkait Lainnya

Senior Contract C++ / JavaScript Software Engineer Firefox (Browser Engine)

Ads Quality Rater - Catalan (Spain)

Uber Driver with Electric Vehicle Needed for App Testing (France)

Freelance Software Tester for Payments testing (Remote in Germany & the Netherlands)