1

Flutter Engineer Jobs in Washington (NOW HIRING)

About the Role Most companies hire engineers to close tickets. We hire them to solve problems ... Work across our stack Ruby on Rails, React, and Flutter, with native bits where it counts (yes ...

About the Role Most companies hire engineers to close tickets. We hire them to solve problems ... Work across our stack - Ruby on Rails, React, and Flutter, with native bits where it counts (yes ...

Experience with cross-platform development using Flutter and/or React Native is strongly desired. * Provide primary engineering support for legacy native codebases, including iOS and Android ...

Mobile Forensics Software Engineer

Herndon, VA ยท Remote

$141K - $236K/yr

Reverse engineer mobile software applications to identify and understand significant forensic ... Knowledge of mobile application development platforms such as Android, iOS, Flutter, or React ...

New

C++, User interface development (Flutter, QT, etc), 802.11, Matlab, DSP * Familiarity with in and out of band Wifi standards and protocols a plus * Security clearance level: Active TS/SCI with ...

next page

Showing results 1-20

Flutter Engineer information

See Washington salary details

$37.4K

$101K

$160.8K

How much do flutter engineer jobs pay per year?

As of Jul 24, 2026, the average yearly pay for flutter engineer in Washington is $101,009.00, according to ZipRecruiter salary data. Most workers in this role earn between $75,300.00 and $123,500.00 per year, depending on experience, location, and employer.

What does a Flutter engineer do?

A Flutter engineer develops cross-platform mobile applications using the Flutter framework and the Dart programming language. They design user interfaces, write code, troubleshoot issues, and optimize app performance for both iOS and Android devices. Proficiency with software development tools and understanding of mobile app architecture are essential for this role.

What is a Flutter Engineer job?

A Flutter Engineer is a software developer who specializes in building mobile, web, and desktop applications using the Flutter framework. They write code in Dart and utilize Flutter's widget-based architecture to create responsive and high-performance user interfaces. Their responsibilities include developing, testing, and maintaining cross-platform applications, integrating APIs, and ensuring app performance and scalability. Flutter Engineers often collaborate with designers and backend developers to deliver seamless user experiences.

Is Flutter high paying?

Flutter engineers typically earn competitive salaries due to their specialized skills in cross-platform mobile development using the Flutter framework and Dart language. Compensation varies based on experience, location, and company size, but overall, Flutter development is considered a well-paying field within software engineering. Skilled Flutter developers with experience in UI design and app deployment often command higher salaries.

Is Flutter still used in 2026?

Flutter remains a popular framework for Flutter engineers in 2026, as it continues to be widely adopted for cross-platform mobile app development due to its performance and ease of use. Its active community, regular updates, and support for building natively compiled applications make it a relevant skill for developers in the industry.

What are the key skills and qualifications needed to thrive in the Flutter Engineer position, and why are they important?

To thrive as a Flutter Engineer, you need strong programming skills in Dart, experience with Flutter SDK, and a good understanding of mobile application architecture for both iOS and Android platforms. Familiarity with tools such as Android Studio, Xcode, Git, and continuous integration systems, as well as any relevant mobile development certifications, is advantageous. Excellent problem-solving abilities, collaboration, and clear communication skills help you work effectively in agile development teams. These competencies are vital for delivering high-quality, cross-platform mobile apps efficiently and maintaining seamless team workflows.

What engineers make $500,000?

Senior engineers in high-demand fields such as software engineering, data engineering, and specialized roles like machine learning engineers can earn $500,000 or more annually, especially with extensive experience, advanced skills, and working in competitive industries or companies. Compensation often includes base salary, bonuses, and stock options, particularly in tech companies or startups with high growth potential.

What are the typical daily responsibilities of a Flutter Engineer?

As a Flutter Engineer, your daily tasks often include designing, developing, and testing cross-platform mobile applications using the Flutter framework. You might collaborate closely with product managers, designers, and backend developers to refine app features and implement user interfaces that provide a seamless experience across devices. Regular activities can also involve debugging, addressing performance issues, writing unit tests, and participating in code reviews to maintain high code quality. Additionally, you'll likely attend daily standup meetings and participate in agile sprint cycles to ensure alignment with team goals and project deadlines.

Infographic showing various Flutter Engineer job openings in Washington as of July 2026, with employment types broken down into 90% Full Time, 8% Part Time, and 2% Contract. Highlights an 85% Physical, 6% Hybrid, and 9% Remote job distribution, with an average salary of $101,009 per year, or $48.6 per hour.
Product Engineer

Product Engineer

Uscreen

Washington, DC โ€ข Remote

Full-time

Posted 22 days ago


Job description

Salary:

About the Role

Most companies hire engineers to close tickets. We hire them to solve problems.

Uscreen is looking for a Product Engineer who starts with the creator's experience and works backward to the tech that delivers it. Someone hands you a half-formed problem. You turn it into something creators can actually use, and you own the whole thing: the design call, the code, the ugly edge cases, and the metric that proves it worked.

This is not a ticket-taking role, and it is not a place to wait for someone to tell you what to build. You take a fuzzy customer pain and ship the value, end to end. The outcome is what matters to you.

This role is fully remote, worldwide. You report to the
CTO.

What You'll Do

  • Take ambiguous, half-formed customer problems and turn them into shipped product creators can actually use
  • Own the full path of a solution: the design decision, the code, the edge cases, and the metric that proves it worked
  • Talk directly to creators rather than waiting for a PM to translate their needs
  • Work across our stack Ruby on Rails, React, and Flutter, with native bits where it counts (yes, even BrightScript)
  • Measure success in outcomes that move the business, not tickets closed
  • Throw out yesterday's work the moment a better answer shows up, and delete more code than you add
  • Hold the bar between "working" and "solved" and keep fixing until good becomes right

You'll Likely Succeed If

  • You've shipped something real, and you can send us the link.
  • You'd rather talk to a creator than wait for a PM to translate.
  • You measure success in outcomes, not tickets closed.
  • You'll throw out yesterday's work the second a better answer shows up.
  • You delete more code than you add, at least sometimes.
  • You can tell good from almost-good and it bugs you until you fix it.
  • You have judgment about which problem actually matters, then ship the thing that moves it.

Why This Matters

Code that runs is table stakes. Working software isn't the same as a solved business problem, and the engineer we want feels that difference in their gut.

Anyone can rent a machine that spits out working code now, so that's not the edge anymore. The edge is judgment: knowing which problem actually matters to a creator, then shipping the thing that moves it. We hire for how you think, not what you've memorized.

How to Apply

Take an ambiguous prompt and ship a sharp answer: write to our CTO atcto@uscreen.tv and show one problem you owned end to end the problem and why it mattered, what you shipped to kill it (and what you chose not to build), how you knew it worked, and something you've built that we can click right now.

The best applications don't read like applications.