New comment by spoofyroot in "Ask HN: Who is hiring? (November 2026)"
- Status
- Open
- Remote policy
- Onsite
- Employment type
- Not stated
- Salary
- Not stated
- Source
- hn-whoishiring
- First observed
- 2026-11-02 23:39 UTC
- Last seen
- 2026-11-02 23:39 UTC
- Source claims posted
- 2026-11-02 22:33 UTC
- Consecutive misses
- 0 of 10
What the posting says
Meta | Security Engineer (Senior / Staff) | ONSITE Bellevue, Menlo Park, New York, Washington DC — Staff role also REMOTE (US) | Full-time
Meta's Central Security team is hiring Security Engineers at two levels (same team, same work):
- Senior (IC5): https://www.metacareers.com/profile/job_details/140745796424... - Staff (IC6): https://www.metacareers.com/profile/job_details/548694391486...
We find weaknesses before attackers do, then build the solutions that eliminate them. You'll be the expert engineering and product teams turn to for AI security and native-code security guidance, providing security guidance on a constant stream of new products, leading internal security/privacy initiatives, assessing and responding to internet threats, and conducting security assessments specializing in mobile platform and application code. The work protects 3B+ people. Looking for: B.S./M.S. in CS or equivalent experience; 6+ years (IC5) / 8+ years (IC6) in security engineering (vuln research, pentesting, or assessments of production systems); 4+ years reviewing C/C++ with secure coding practices; programming in Python/C++ or similar; security architecture and least-privilege experience on internet-facing products. Nice to have: iOS/Android security model, VM escapes, exploitation / reverse engineering / CTF, static analysis and fuzzing, Rust / Obj-C / Java/Kotlin, community contributions (research, talks, bug bounty), and experience using AI tools to improve security workflows.
Quality
- x Salary range stated weight 35%
- + Remote policy stated weight 20%
- x Location stated weight 15%
- + Organisation stated weight 15%
- + Publication date stated weight 15%
Not enough history yet to judge honesty signals.
Timeline
-
*
#1695840 2026-11-02 23:39 UTCPublished