Interested in this AI/ML Engineer role at Las Vegas Sands Corp.?
Apply Now →Skills & Technologies
About This Role
Position Overview
The primary responsibility of the Senior Application Security Engineer (AI\-First Development) is to design, orchestrate, and validate the offensive security tooling and adversary\-emulation capabilities used to find, prove, and help remediate exploitable weaknesses across applications, infrastructure, the software supply chain, and AI/ML systems. This role operates within an AI\-First SDLC in which AI agents serve as primary producers of offensive tooling, exploit proof\-of\-concept code, attack automation, and adversary\-emulation artifacts, while the engineer provides operational direction, context engineering, human\-in\-the\-loop governance, and final accountability for the safety, authorization, and effectiveness of all offensive security work. All testing is performed strictly within authorized scope and defined rules of engagement.
The Senior Application Security Engineer is an experienced security or software engineer with a strong offensive security and secure\-coding background who has adopted modern AI\-assisted development tools as a core part of their daily workflow and is prepared to grow into deeper agent orchestration, context engineering, and verification responsibilities. This is a tool\-builder\-forward role: the emphasis is on engineering high\-quality offensive tooling and exploit proof\-of\-concepts as much as on executing engagements.
All duties are to be performed in accordance with departmental and Las Vegas Sands Corp.’s policies, practices, and procedures. All Las Vegas Sands Corp. Team Members are expected to conduct and carry themselves in a professional manner at all times. Team Members are required to observe the company’s standards, work requirements and rules of conduct.
Essential Duties \& Responsibilities
- Offensive Tooling Strategy, Agent Workflow Design, and Orchestration
+ Design, build, and maintain AI agent workflows that produce offensive security tooling, exploit proof\-of\-concept code, attack automation, and adversary\-emulation artifacts from engagement objectives and authorized scope.
+ Decompose engagement objectives and threat scenarios into discrete, verifiable offensive tasks and tooling components that AI agents can execute effectively within defined boundaries and rules of engagement.
+ Select and configure appropriate AI models, agent frameworks, and offensive tooling for each workflow based on blast radius, target sensitivity, operational safety, and cost considerations.
+ Construct and maintain operational context that provides agents with approved attack techniques, target environment details, rules of engagement, and safety constraints needed to produce correct, in\-scope, and consistent outputs.
+ Contribute to the offensive toolchain, including reusable testing skills, automation hooks, and project memory files that provide persistent context across agent sessions. Authoring of advanced toolchain components may be developed on the job.
+ Systematically capture attack patterns, technique effectiveness, and findings from each engagement and encode them back into shared context, offensive skills, and agent configurations so that subsequent work becomes more reliable.
+ Participate in collaborative refinement sessions to align on engagement objectives, scope, safety constraints, and context packages before agent execution begins.
+ Establish and maintain rules of engagement, scope boundaries, written authorization, and deconfliction procedures for each engagement, ensuring all offensive activity remains legal, authorized, and safe.
- Exploit Validation and Findings Assurance
+ Apply human oversight at governance checkpoints appropriate to the risk level of each workflow, including pre\-execution review, in\-flight observation, and post\-execution audit.
+ Review, test, and approve AI\-generated offensive tooling, exploit code, and attack automation, ensuring they meet Sands coding standards, operational safety requirements, and rules of engagement before use against any authorized target.
+ Verify that AI\-generated exploits and offensive tooling demonstrate genuine, reproducible impact rather than false positives, and reject findings that cannot be reliably validated or that achieve results outside authorized scope.
+ Partner with Cyber Security on Threat and Risk Assessments, vulnerability remediation, AI agent governance, and approved tooling decisions, surfacing offensive findings and exploitability signals that inform their reviews.
+ Support agent observability practices that track engagement activity, finding rates, exploit reproducibility, and coverage across targets and environments.
+ Produce clear, reproducible engagement deliverables, including technical findings reports, executive summaries, attack\-path narratives, and prioritized remediation recommendations tailored to both technical and executive stakeholders.
- Offensive Engineering and Application Exploitation
+ Architect and deliver shared offensive tooling, exploitation frameworks, and reusable testing harnesses spanning web, API, cloud, and binary targets that the security team consumes, using AI\-First methodologies as the primary development approach.
+ Define attack methodologies, engagement playbooks, tooling interfaces, and safety controls that serve as foundational context for agent\-driven offensive work.
+ Collaborate with cross\-functional teams including engineering, QA, Cyber Security, and IT Operations to translate threat scenarios into executable offensive testing workflows.
+ Coordinate with security and engineering teams across global locations to ensure consistency in testing standards, safety controls, and reporting practices.
+ Write, debug, and refactor exploit code, offensive tooling, and attack automation directly when agent outputs require manual intervention or when developing novel exploitation techniques.
+ Ensure delivered offensive tooling meets enterprise standards for reliability, maintainability, operational safety, observability, and responsible use.
+ Design and execute offensive testing of the organization's AI and LLM\-based systems and agents, including prompt injection, jailbreaks, tool and MCP abuse, guardrail evasion, and model and training\-data extraction, drawing on frameworks such as the OWASP LLM Top 10 and MITRE ATLAS.
- Continuous Improvement and Mentorship
+ Evaluate emerging AI models, agent frameworks, offensive tooling, and attack techniques to continuously improve testing effectiveness and coverage.
+ Mentor team members on AI\-assisted offensive security practices, context engineering techniques, and verification methodologies.
+ Document attack patterns, prompt and context libraries, and lessons learned to build institutional knowledge.
+ Participate in collaborative construction sessions, guiding agent execution in real time and coaching team members on effective offensive tooling and engagement orchestration techniques.
- Perform job duties in a safe manner.
- Attend work as scheduled on a consistent and regular basis.
- Perform other related duties as assigned.
Minimum Qualifications
- At least 21 years of age.
- Proof of authorization to work in the United States.
- Bachelor's degree in Computer Science, Software Engineering, Cybersecurity, or a related field, or equivalent professional experience.
- Must be able to obtain and maintain any certification or license, as required by law or policy.
- 5\+ years of professional software engineering or offensive security experience, including time in senior or lead positions owning the design and delivery of non\-trivial security tooling or leading penetration\-testing or red\-team engagements.
- Demonstrated daily use, over the past 6 months or more, of at least one modern AI\-assisted development tool such as Claude Code, Cursor, GitHub Copilot, or Windsurf, with the ability to speak concretely about effective usage patterns and failure modes.
- Strong foundational knowledge in at least one major programming or scripting ecosystem (such as Python, Go, C/C\+\+, Rust, or PowerShell) and hands\-on experience building offensive security tooling or exploits. Familiarity with additional languages and runtimes is a plus.
- Experience assessing or exploiting workloads on at least one major cloud platform (Azure, AWS, or GCP). Azure experience is a plus.
- Hands\-on experience conducting offensive security work such as penetration testing, red\-team engagements, or application, web, and API exploitation, including familiarity with common offensive tooling (such as Burp Suite, Metasploit, or nmap) and adversary frameworks such as MITRE ATT\&CK.
- Solid working knowledge of Windows and Linux internals, networking fundamentals, and enterprise identity systems such as Active Directory, including common identity and privilege\-escalation attack paths.
- Demonstrated experience conducting thorough code reviews, identifying defects in both human\- and AI\-generated outputs, and providing constructive technical feedback.
- Excellent written and verbal communication skills, with the ability to articulate technical decisions and trade\-offs, and to write clear, actionable findings reports for both technical and non\-technical stakeholders.
- Strong interpersonal skills with the ability to communicate effectively and interact appropriately with management, other Team Members and outside contacts of different backgrounds and levels of experience.
Preferred Qualifications
- Practical experience constructing structured context for LLMs, including prompt design, RAG pipelines, context window optimization, project memory files (such as CLAUDE.md or AGENTS.md), and integration with MCP servers. Familiarity with tactical context management techniques such as plan mode, context editing, and multi\-session splitting.
- Experience authoring reusable skills, configuring automation hooks, building custom MCP servers, or otherwise assembling agent toolchains that enable repeatable, production\-grade offensive security workflows.
- Hands\-on experience with vulnerability research, exploit development, fuzzing, or reverse engineering, including container and Kubernetes attack and escape techniques.
- Knowledge of secure development practices, the OWASP Top 10, adversary frameworks such as MITRE ATT\&CK, and threat modeling. Industry certifications such as OSCP, OSEP, OSWE, GXPN, or CRTO. Experience working within a regulated industry such as gaming, finance, healthcare, or hospitality. Understanding of data privacy and responsible AI principles.
- Experience with command\-and\-control or adversary\-emulation frameworks (such as Cobalt Strike, Sliver, Mythic, or Caldera), purple\-team collaboration with detection engineering, or red\-team operations against cloud and identity systems.
- Hands\-on experience red\-teaming AI/ML or LLM\-based systems and agentic workflows (prompt injection, jailbreaks, tool and MCP abuse, model and data extraction), including familiarity with the OWASP LLM Top 10 or MITRE ATLAS and tooling such as PyRIT, Garak, or Promptfoo.
Physical Requirements
Must be able to:
- Physically access assigned workspace areas with or without reasonable accommodation.
- Work remotely as necessary.
- Work indoors and be exposed to various environmental factors such as, but not limited to, CRT, noise, and dust.
- Utilize laptop and standard keyboard to perform essential functions of the job.
Role Details
About This Role
AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.
Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.
Across the 4,133 AI roles we're tracking, AI/ML Engineer positions make up 69% of the market. At Las Vegas Sands Corp., this role fits into their broader AI and engineering organization.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
What the Work Looks Like
A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
Skills Required
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.
Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
Compensation Benchmarks
AI/ML Engineer roles pay a median of $185,000 based on 13,200 positions with disclosed compensation. Senior-level AI roles across all categories have a median of $227,400.
Across all AI roles, the market median is $200,700. Top-quartile compensation starts at $254,000. The 90th percentile reaches $307,500. For comparison, the highest-paying categories include AI Safety ($274,200) and AI Engineering Manager ($268,700). By seniority level: Entry: $97,760; Mid: $165,778; Senior: $227,400; Director: $250,000; VP: $250,000.
Las Vegas Sands Corp. AI Hiring
Las Vegas Sands Corp. has 4 open AI roles right now. They're hiring across AI Software Engineer, AI Product Manager, AI/ML Engineer. Based in Remote, US.
Remote Work Context
Remote AI roles pay a median of $173,300 across 2,012 positions. About 14% of all AI roles offer remote work.
Career Path
Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.
From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.
The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.
What to Expect in Interviews
Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.
When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.
AI Hiring Overview
The AI job market has 4,133 open positions tracked in our dataset. By seniority: 106 entry-level, 1,901 mid-level, 1,663 senior, and 463 leadership roles (Director, VP, C-Level). Remote roles make up 14% of the market (583 positions). The remaining 3,532 roles require on-site or hybrid attendance.
The market median for AI roles is $200,700. Top-quartile compensation starts at $254,000. The 90th percentile reaches $307,500. Highest-paying categories: AI Safety ($274,200 median, 57 roles); AI Engineering Manager ($268,700 median, 42 roles); Research Engineer ($260,000 median, 442 roles).
Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.
The AI Job Market Today
The AI job market spans 4,133 open positions across 15 role categories. The largest categories by volume: AI/ML Engineer (2,865), Data Scientist (339), AI Software Engineer (313). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.
The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (106) are outnumbered by mid-level (1,901) and senior (1,663) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 463 positions, representing the bottleneck between technical execution and organizational strategy.
Remote work availability sits at 14% of all AI roles (583 positions), with 3,532 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.
AI compensation is structured in clear tiers. The market median sits at $200,700. Top-quartile roles start at $254,000, and the 90th percentile reaches $307,500. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.
Category matters for compensation. AI Safety roles lead at $274,200 median, while Prompt Engineer roles sit at $140,000. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.
The most in-demand skills across all AI postings: Python (2,128 postings), Aws (1,324 postings), Azure (1,003 postings), Rag (916 postings), Gcp (817 postings), Pytorch (655 postings), Prompt Engineering (639 postings), Claude (571 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.
Frequently Asked Questions
Get Weekly AI Career Intelligence
Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.