Skip to main content

Fullstack Developer - Drone

Posted 26 days ago

ltmHouston (TX)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Required seniority: Senior Software Engineer or Staff‐level Software Engineer around 8-10 years of experience. Must have hands‐on coding experience in production cloud systems Core Required SkillsA. Software Engineering Strong proficiency in Python and/or C#Experience designing and implementing REST APIsAbility to own code from design deployment production support Comfortable working in a multi‐repo, CI/CD‐driven environmentB.Cloud‐Native Azure Engineering Hands‐on experience with multiple of the following is required: Azure App Service and/or Azure Container AppsAzure Functions / Durable Functions Azure Blob Storage, ADLS, and SQL‐based storage Azure Key Vault, Managed Identity, API authentication Logging and monitoring (Application Insights, Log Analytics) Infrastructure‐as‐Code (Bicep, ARM, or Terraform) Azure DevOps pipelines (build, release, PR reviews) This aligns directly with AMIE's deployed and planned architecture. C. Distributed Workflow & Orchestration Designing long‐running, stateful workflows Handling retries, failures, idempotency, and external dependencies Orchestrating interactions between services and external APIsAMIE mission scheduling, execution tracking, and data pipelines depend on this. D. API & System Integration Integrating with external vendor APIs (e.g., robotics, Skydio, Boston Dynamics) Experience with event‐driven or message‐based integrations Understanding of security, throttling, and API lifecycle concernsAI / Data Adjacency (Required Awareness) The engineer does not need to build ML models, but must be comfortable integrating them: Working with CV/ML inference inputs and outputs Managing data pipelines for images, metadata, and results Invoking inference services and handling results programmatically Understanding separation between model training vs. inference execution This is core to AMIE's value chain. Microsoft Teams / M365 Integration (Code‐First)
Required: Experience building Teams bots, agents, or integrations
Working with APIs, webhooks, or declarative agent frameworks Event‐driven interactions between Teams and backend services Ways of Working Comfortable with Agile / sprint‐based delivery Participates in design reviews, sprint planning, and PR reviews Able to co‐engineer with Microsoft and internal Chevron engineers

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this