Program Analysis Engineer

About Us

Endor Labs is building the Application Security platform for the software development revolution. Modern software is complex and dependency‑rich, making it increasingly difficult to pinpoint the risks that truly matter. Endor Labs solves this challenge by building a call graph of your entire software estate—enabling teams to clearly identify, prioritize, and fix critical risks faster.

Trusted by companies that are one or one hundred years old, Endor Labs secures code whether it was written by humans or AI, and whether it's 40‑year old C++ code or cutting edge Bazel Monorepos. Endor Labs was founded by serial entrepreneurs Varun Badhwar and Dimitri Stiliadis, and is backed by leading VC firms such as Dell Technology Capital, Lightspeed, and Sierra Ventures.

We are looking for a Program Analysis Engineer with an interest in program analysis, static analysis, or machine learning for code, to join our engineering organization. This is an individual contributor role focused on our static analysis and ML-for-code initiatives.

As an MTS, you will contribute to our existing suite of static analysis tools, help evolve our SCA (Software Composition Analysis) and SAST (Static Application Security Testing) platforms, and help shape machine‑learning experiments that power the next generation of our detection and prioritization capabilities. You will partner closely with engineering, product, and research peers to translate customer needs into production systems that run at scale.

This role is a good fit for engineers who enjoy working on programming languages and code analysis, who are curious about applying ML techniques to real‑world code and App Sec problems, and who thrive in a fast‑paced startup environment.

Location:

Palo Alto, California (hybrid work model – 3 days per week onsite).

• Contribute to our existing suite of static analysis tools, helping improve precision, recall, coverage, and performance across supported languages.
• Help evolve our SCA and SAST platforms, shaping how we detect vulnerabilities, analyze dependencies, and prioritize risk across the software supply chain.
• Participate in machine‑learning experiments for SCA and SAST, from problem framing and dataset work through evaluation and the path from prototype to production.
• Contribute to our program‑analysis infrastructure, which includes call graph construction, data‑flow and taint analysis, and language‑specific analyzers.
• Work with product and engineering to help shape parts of the technical roadmap for analysis and ML‑for‑code work.
• Collaborate with engineers across the team through design discussions, code reviews, and hands‑on pairing.
• Opportunities to represent Endor Labs externally—e.g., talks at technical conferences, meetups, or industry events—if that’s something you enjoy.
• Engage with customers when needed—triaging findings, explaining analysis behavior, and turning field feedback into product improvements.
• Help identify and address performance bottlenecks, reliability issues, and technical debt across the analysis stack.

• Experience with program analysis or static analysis (e.g., call graphs, data‑flow or taint analysis, abstract interpretation, symbolic execution) or ML for code (e.g., vulnerability detection, code representation learning, program repair, code embeddings, reachability prediction, LLM‑based code understanding). Deep expertise in one area is great; a working familiarity and eagerness to learn is also welcome.
• A software engineering background—industry experience, research, open source, or a mix.
• Comfort working in at least one of Java, Python, or Go, and the ability to ship production‑quality code (or the trajectory to get there quickly).
• A product mindset—you care about building things that work well for users, not just technically interesting code.
• Good communication and collaboration skills. You can work through technical trade‑offs with teammates and explain your thinking clearly.

• Interest in giving talks at technical conferences, workshops, or industry events, or in engaging directly with customers. Neither is required.
• Familiarity…