2

Flight Test Engineer Remote Jobs in Utah (NOW HIRING)

... is remote eligible for candidates who currently reside in Utah. What You'll Do * API Test & Framework Engineering: Actively participate in the development lifecycle by proactively digging into ...

... is remote eligible for candidates who currently reside in Utah. What You'll Do * API Test & Framework Engineering: Actively participate in the development lifecycle by proactively digging into ...

Quality Engineer II

Sandy, UT ยท On-site +1

$68K - $88K/yr

Leads development of risk assessments and test methods * Supports component qualifications, design ... Remote or field-based positions will have different workplace arrangements which will be indicated ...

Sr. Software Engineer (AI & Backend)

Salt Lake City, UT ยท On-site +1

$118K - $156K/yr

This is a remote position; however, the candidate must reside within 30 miles of one of the ... Write automated unit tests, integration tests, end-to-end tests, concurrency tests, load ...

Sr. Software Engineer (AI & Backend)

Salt Lake City, UT ยท On-site +1

$118K - $156K/yr

This is a remote position; however, the candidate must reside within 30 miles of one of the ... Write automated unit tests, integration tests, end-to-end tests, concurrency tests, load ...

Senior Electrical Engineer

Salt Lake City, UT ยท On-site +1

$104K - $135K/yr

... remote working. Key Responsibilities * Provide leadership and mentoring to junior staff * Lead ... Must pass drug test, fit-for-duty medical exam, background check, and must have a satisfactory ...

CI gates, structural tests, linting rules, and architectural enforcement that mechanically prevent ... Bay Area (hybrid) or Salt Lake City area (remote). No visa sponsorship. What We Offer Bolo AI is ...

New

All positions are remote capable, so we can work with anyone anywhere, except Space, but that ... Tests own work and contributes to the development of test plans. * Evaluates and plans software ...

WordPress Developer

Lehi, UT ยท On-site +1

All positions are remote capable, so we can work with anyone anywhere, except Space, but that ... Tests own work and contributes to the development of test plans. * Evaluates and plans software ...

next page

Showing results 1-20

Flight Test Engineer Remote information

What are the key skills and qualifications needed to thrive as a Flight Test Engineer (Remote), and why are they important?

To thrive as a Flight Test Engineer (Remote), you need a strong background in aerospace engineering, flight dynamics, and systems integration, often supported by a relevant engineering degree or certification. Familiarity with data acquisition systems, flight test instrumentation, and software such as MATLAB or LabVIEW is typically required. Strong analytical thinking, communication, and teamwork skills are essential for collaborating with multidisciplinary teams and interpreting complex data remotely. These abilities ensure accurate test execution, safety, and effective problem-solving in a highly technical and regulated environment.

What are Flight Test Engineers (Remote)?

Flight Test Engineers (Remote) are professionals who oversee and coordinate the testing of aircraft systems and performance, often from a remote location. They are responsible for planning, monitoring, and analyzing flight tests to ensure safety, compliance, and efficiency. Working remotely, they use advanced communication and data analysis tools to collaborate with on-site teams, review test results, and provide technical recommendations. This role requires strong engineering knowledge, attention to detail, and the ability to solve complex problems from a distance.

What is the difference between Flight Test Engineer Remote vs Flight Test Engineer on-site?

AspectFlight Test Engineer RemoteFlight Test Engineer on-site
Work EnvironmentPrimarily remote, with occasional on-site testing or meetingsLocated at testing sites or aircraft facilities
Required CredentialsSimilar certifications, such as engineering degrees and flight test certificationsSame as remote, often with additional on-site safety training
Industry UsageCommon in aerospace companies with remote testing capabilitiesTraditional testing roles at physical locations
Work FlexibilityHigher flexibility, with remote collaboration toolsLess flexible, based on testing schedules and site access

Both roles require similar technical credentials and industry knowledge. The main difference lies in the work environment, with remote positions offering more flexibility and on-site roles involving physical testing at specific locations.

How does a remote Flight Test Engineer effectively collaborate with on-site teams during test campaigns?

Remote Flight Test Engineers typically work closely with on-site engineers, pilots, and technicians through a combination of video conferencing, real-time data streaming, and collaborative project management tools. They are often responsible for monitoring live test data, analyzing results, and providing immediate feedback or troubleshooting support from their remote location. Clear communication and proactive scheduling are essential, as remote engineers must coordinate across different time zones and adapt to the dynamic nature of flight test operations. Regular virtual meetings and detailed documentation help ensure that the remote engineer remains fully integrated with the on-site team, contributing to the success of the test program.
What are the most commonly searched types of Flight Test Engineer jobs in Utah? The most popular types of Flight Test Engineer jobs in Utah are:
What cities in Utah are hiring for Flight Test Engineer Remote jobs? Cities in Utah with the most Flight Test Engineer Remote job openings:

Software Engineer AI-Native Full Stack

Bolo AI

Salt Lake City, UT โ€ข On-site, Remote

Other

PTO

Posted 2 days ago


Job description

Software Engineer โ€” AI-Native Full Stack

Bay Area (Hybrid) | Salt Lake City Area (Remote) | Full-Time Senior Engineer

Bolo.ai

Bay Area (Hybrid) | Salt Lake City Area (Remote) | Full-Time

The Role Has Changed

Three person engineering teams are building what used to take thirty. Not by working harder, but by working differently. The engineers shipping at this pace don't write code. They write specs precise enough that agents implement them correctly. They build harnesses. CI gates, structural tests, linting rules, and architectural enforcement that mechanically prevent entire classes of agent mistakes. They design validation systems where agents write the tests and humans verify that features actually work from the user's perspective.

The code is a generated artifact. The spec, the harness, and the validation infrastructure are what engineers maintain.

This is how we work at Bolo.ai. We're hiring engineers who already work this way, or who have the depth to start.

The Company

Bolo.ai builds generative AI systems for the energy industry, making daily work faster, safer, and better for heavy industry workers. We have Fortune 500 contracts, production deployments, and growing enterprise demand. We're scaling.

Energy adds real constraints. Regulatory compliance, data residency, operational technology integration, deployment across cloud and on-premises infrastructure. These constraints make the architecture harder and the work more interesting.

The Work

You'll spend your time on four things:

Specifications. You write behavioral specs, architectural constraints, and feature requirements that agents implement against. When agent output misses the mark, you tighten the spec. Not by adding more words, but by being more precise about what "correct" means. This requires understanding the system deeply enough to define its behavior at every layer.

Harness. You build and maintain the infrastructure that keeps agents producing reliable code. Structural tests that enforce architectural boundaries. Linting rules where every failure message teaches the agent what went wrong. CI gates that reject drift. Structured knowledge bases agents can navigate. The principle: every class of agent mistake gets a mechanical fix so it never recurs.

Validation. Agents write the code. Agents write the tests. You verify that features work from the user's perspective, under real deployment conditions, against edge cases that matter in production. You define scenarios and acceptance criteria. You build the end-to-end checks, behavioral verification, and automation that make this trustworthy at scale. When something breaks, your job is diagnosing whether the failure is in the spec, the harness, or the agent's implementation, and fixing the right layer.

Architecture and operations. Our systems run across cloud providers and on-premises environments. You design modular abstractions, clean interfaces where deployment targets don't leak into application logic. You own production systems used by energy companies in regulated environments where failures have real consequences. Reliability, observability, and graceful degradation matter here.

What Makes Someone Good at This

7+ years of engineering experience, applied at a higher altitude. You need years of building and debugging production systems. Not because you'll write every line, but because you can't design a harness that catches real failures, write a spec that anticipates edge cases, or diagnose a broken feature across the full stack without that foundation. The depth serves the abstraction.

Systems thinking over code fluency. How components interact. Where failures cascade. What breaks when requirements change. What to anticipate before it happens. This is what agents are worst at and what matters most.

An agent-driven workflow. You already direct AI agents (Claude Code, Codex, Cursor, or similar) to handle implementation while you focus on architecture, specification, and validation. Or you have the engineering judgment to make that transition and the motivation to do it now.

Experience building the infrastructure around agents. CI enforcement, scenario-based testing, documentation systems agents can consume, structured knowledge bases โ€” you've built some of this, or you have specific ideas about how and why.

Comfort making decisions with incomplete information. Startup. Requirements shift. The right approach isn't always obvious. You move forward, and you know when to ask versus when to make a call.

Direct communication. You give and receive honest feedback. You can disagree with a decision, say so clearly, and still commit to the outcome. We care about getting it right more than being right.

Enthusiasm for a field that reinvents itself quarterly. Tools change. Workflows get replaced. Best practices from three months ago become obsolete. You're energized by that. You see this as the most interesting period in the history of software.

About Us

Small, senior-leaning engineering team. Real ownership, direct impact, no layers between you and the work. We expect a lot from each other and give each other the room to deliver.

Sustainable pace over heroic sprints.

Bay Area (hybrid) or Salt Lake City area (remote). No visa sponsorship.

What We Offer

Bolo AI is headquartered in Palo Alto, backed by True Ventures, Benchstrength, Accomplice, J Ventures, and Beat Ventures.

  • Competitive compensation with equity so you share in what we build together.
  • Hybrid flexibility โ€” in-person collaboration in Palo Alto with room to work how you're most productive.
  • Early-stage ownership โ€” join at a stage where your decisions shape the product, the architecture, and the engineering culture.
  • Generous PTO and flexible working hours.
Hiring Process

We evaluate how you work in an AI-native workflow. AI tool usage is expected, not just permitted. We're looking at engineering judgment. Can you write specs agents execute well against, build systems that catch real failures, and reason about problems across the full stack.

We'll be straightforward about our process, give you real information to evaluate us, and give you feedback regardless of outcome.

If this sounds like what you're already building toward, we'd like to talk.