2

Remote Embedded Software Jobs in Pflugerville, TX

Software Engineer, Product

Austin, TX · Remote

$140K - $160K/yr

If you're passionate about solving massive-scale engineering challenges and eager to be part of a fast-paced remote startup culture, we encourage you to apply to join our team today! As a Software ...

Software Engineer (Ruby on Rails) A founding-stage, venture-backed Enterprise AI company building ... Location: 100% Remote Salary: Up to 150K DOE! In this role you will: * Write high-quality ...

Software Engineer (Ruby on Rails) A founding-stage, venture-backed Enterprise AI company building ... Location: 100% Remote Salary: Up to 150K DOE! In this role you will: * Write high-quality ...

Software Engineer (Ruby on Rails) A founding-stage, venture-backed Enterprise AI company building ... Location: 100% Remote Salary: Up to 150K DOE! In this role you will: * Write high-quality ...

Showing results 21-40

Remote Embedded Software information

See Pflugerville, TX salary details

$65.8K

$144.3K

$163.7K

How much do remote embedded software jobs pay per year?

As of Aug 15, 2026, the average yearly pay for remote embedded software in Pflugerville, TX is $144,279.00, according to ZipRecruiter salary data. Most workers in this role earn between $123,700.00 and $162,700.00 per year, depending on experience, location, and employer.

What is a remote embedded software engineer?

A remote embedded software engineer is a professional who designs, develops, tests, and maintains software that runs on embedded systems, such as microcontrollers or specialized hardware, while working from a location outside the traditional office environment. These engineers typically collaborate with hardware teams, write code for real-time or resource-constrained systems, and use remote tools to debug and deploy software. They may work in industries like automotive, medical devices, consumer electronics, or industrial automation. Remote embedded software engineers rely on communication and project management tools to coordinate with their teams and ensure product quality.

What are some common challenges faced by remote embedded software engineers, and how can they be addressed?

Remote embedded software engineers often face challenges such as limited access to physical hardware for testing, coordinating with hardware teams across locations, and ensuring clear communication about design specifications. To overcome these, teams typically use simulation tools, remote access labs, and detailed documentation. Regular virtual meetings and collaborative platforms also help maintain alignment and facilitate troubleshooting in distributed environments.

What are the key skills and qualifications needed to thrive as a remote embedded software engineer, and why are they important?

To thrive as a Remote Embedded Software Engineer, you need expertise in embedded systems programming (typically in C/C++), hardware interfacing, and a relevant degree in computer engineering or electrical engineering. Familiarity with development tools such as debuggers, version control systems (e.g., Git), and real-time operating systems (RTOS) is commonly required. Strong problem-solving abilities, self-motivation, and effective remote communication skills help you excel in a distributed team environment. These skills ensure reliable software integration with hardware, efficient collaboration, and successful delivery of complex embedded solutions.

What is the difference between Remote Embedded Software vs Remote Firmware Engineer?

AspectRemote Embedded SoftwareRemote Firmware Engineer
Required CredentialsBachelor's in Computer Engineering, Electrical Engineering, or related; experience with embedded systemsBachelor's in Electrical Engineering, Computer Engineering, or related; experience with firmware development
Work EnvironmentDevelops software for embedded devices, often in hardware labs or remote setupsCreates low-level firmware for hardware components, typically in hardware labs or remote
Industry UsageAutomotive, IoT, consumer electronics, industrial systemsConsumer electronics, IoT, aerospace, automotive
Common Search/ComparisonYesYes

Remote Embedded Software and Remote Firmware Engineer roles both involve working on embedded systems, but Embedded Software focuses on higher-level software development, while Firmware Engineers work on low-level hardware control code. Both require similar credentials and are used across industries like automotive and IoT, often in remote or hybrid environments.

What are remote embedded software jobs?

Remote embedded software jobs include embedded software engineer positions. As a work from home embedded software engineer, you develop embedded software systems for a variety of computerized devices. Your responsibilities start with assessing your client’s needs. You then design and code the embedded software, troubleshoot your software systems, perform research and test actions on the software, and implement software updates whenever necessary. Other duties include maintaining the software programs, documenting solutions to issues, providing the necessary post-production support, and reviewing the implemented system to debug the embedded environment and interpret error reports.

What are popular job titles related to Remote Embedded Software jobs in Pflugerville, TX?

For Remote Embedded Software jobs in Pflugerville, TX, the most frequently searched job titles are:

What cities near Pflugerville, TX are hiring for Remote Embedded Software jobs?

Cities near Pflugerville, TX with the most Remote Embedded Software job openings:

Infographic showing various Remote Embedded Software job openings in Pflugerville, TX as of August 2026, with employment types broken down into 100% Full Time. Highlights an 100% Remote job distribution, with an average salary of $144,279 per year, or $69.4 per hour.

Software Engineer L2 - Finance & Accounting Platform

Curative HR LLC

Austin, TX • On-site, Remote

$217K/yr

Full-time

Medical, Dental, Vision, Retirement, PTO

Posted 23 days ago


Job description

About Curative
Curative is building the future of health insurance with a first-of-its-kind employer-based plan designed to remove financial barriers and make care truly accessible: one monthly premium with $0 copays and $0 deductibles*. Backed by our recent $150M in Series B funding and valuation at $1.275B, Curative is scaling rapidly and investing in AI-powered service, deeper member engagement, and a smart network designed for today's workforce.
Our north star guides everything we do: healthcare only works when people can actually use it. That belief drives every decision we make: from how we design our plan, support our members, to how we collaborate as a team.
If you want to do meaningful work with a team that moves fast, experiments boldly, and cares deeply, Curative is the place to do it. We're growing fast and looking for teammates who want to help transform health insurance for the better.
Summary
We are hiring a forward deployed software engineer to be the technical owner of our health plan Finance and Accounting (F&A) platform - the brains of Curative's financial operations. It's a deeply data-intensive application: it pulls large volumes of financial data from many sources, transforms and reconciles it, and turns it into the accurate analysis the business depends on. You will sit at the intersection of engineering and F&A operations - embedded with the people who use the software, not insulated from them. You will join the F&A team's working sessions, hear directly where the numbers don't line up, and ship the fix the same week. You will also be the person watching the data - tracking
where our system and the source of truth disagree, and chasing down why. A big part of the job is building AI agents that take work off people's plates - handling incoming support and billing questions, and automating the manual, repetitive processes the F&A teams run. You will be the single technical point of responsibility for this service. You will partner with F&A and product stakeholders to turn their workflows into shipped software, set the architectural direction, own production, and represent the platform in cross-team discussions.
How we build
At Curative, AI writes most of the code. Engineers direct it. We use agentic AI coding tools as the primary development surface. Most engineers here routinely runs multiple agents in parallel - one implementing a feature, one resolving review comments, one chasing down a flaky test. The engineers job is to set context, make the decisions the AI can't make, and keep the bar high on what ships.
This is not a role for someone who wants to hand-roll every line. It is also not a role for someone who will accept whatever the AI produces. We are looking for the engineer in between: strong enough fundamentals to catch a wrong answer in a few seconds, disciplined enough to review every diff, and ambitious enough to drive several times the output of a traditional IC. Strong systems and architecture thinking is important, as is product taste. This is a fully remote position
What you'll own
  • The codebase. A full-stack Python + TypeScript application with significant domain complexity. You own code review, architectural decisions, and the quality bar. Most commits will be AI-authored, human-directed, human-reviewed. All of them are yours.
  • AI leverage. The internal tooling, prompts, skills, and evals that let one engineer operate a service of this scope. You will extend it.
  • Agents that do the work. You will design and ship AI agents that handle support and billing issues and automate the manual processes the F&A team runs by hand today - turning recurring, tedious work into software that runs itself. This is some of the highest-leverage work on the platform, and it's yours to own
    end to end.
  • The data. This platform lives and dies on its data - moving it from many sources, transforming it correctly, and keeping it trustworthy. You own the pipelines that feed it and the checks that catch a bad number before anyone downstream sees it.
  • Financial correctness. The numbers this platform produces have to be right. You own the logic and the safeguards that make the output something the business can rely on and stand behind.
  • Production. Cloud infrastructure, deploy pipeline, observability, on-call, incident response, and cost - including the data jobs the F&A team depends on running on schedule.
  • Sensitive data. This platform touches both PHI and financial information. You own handling it responsibly, with data-privacy discipline baked in rather than bolted on.
  • Operational metrics. You watch how the platform performs for its users - not just uptime, but whether the numbers reconcile, how much manual work the software is or isn't eliminating, and where the data says something is off. You surface what the data shows, propose changes, and close the loop.
  • Stakeholder relationships. You are the engineer in the room with accountants and F&A leads. You translate their pain into scope, push back when a request won't solve the real problem, and build trust by shipping reliably.
  • The roadmap. Co-owning the product plan with F&A and product stakeholders. Sequencing work, flagging what is infeasible, proposing alternatives - and sometimes arguing for the thing nobody asked for yet because you are close enough to the problem to see it.
  • Strategy for your surface. You don't just execute a roadmap handed to you - you shape it. You see patterns across stakeholder feedback, the data, and business goals, and propose what to build next.
  • Integrations. A growing set of connections to internal services and third-party financial systems that this platform reads from and writes to.
  • The domain. You will not arrive an expert in health-plan finance, but within 90 days you will understand the workflows well enough that every prompt you write is loaded with the right context.

What we're looking for
Foundational skills (non-negotiable)
You need these because you are the last line of defense on what the AI produces. The bar is not "can write it from scratch in an interview" - the bar is "can read a 400-line AI-generated diff and spot the subtle bug in 90 seconds." In this domain, that bug is often a number that's quietly wrong.
  • 5+ years shipping production software. Enough reps that you recognize bad code before you can articulate why.
  • Real fluency in Python and TypeScript. Not "I can read it" - fluent.
  • Strong SQL and relational database fundamentals. You can read a query plan, spot an N+1, and know when a migration is unsafe at scale, and reason carefully about the joins and aggregations that decide what a number ends up being.
  • Experience building data-intensive applications. You have built systems that move, transform, and reconcile meaningful volumes of data - ETL/sync pipelines and the interfaces on top of them - and you care about getting the data right, not just moving it.
  • A correctness mindset. You have built systems where the output has to add up, and you instinctively reach for the checks, invariants, and audit trails that prove a number is right rather than just plausible. You are comfortable with the idea that "close enough" is not close enough.
  • Systems thinking. Can sketch a service's architecture on a whiteboard, identify the failure modes, and reason about blast radius.
  • Production cloud experience (AWS, GCP, or equivalent). You have been on-call for something real.
  • Comfort working directly with non-technical stakeholders. You can run a 30-minute workflow review with an accountant, extract the real requirements, and leave them feeling heard - not bulldozed.
  • An interest in working with financial data. You don't need a finance background, but you should be genuinely interested in the problem space - financial data, the systems that produce it, and the satisfaction of making the numbers come out right.
  • Sharp written communication. You will spend more time writing prompts, specs, and PR descriptions than writing code.

Note: prior healthcare or finance experience is not required. We care far more about your track record building and operating data-intensive systems where correctness matters - any industry counts. What we do look for is an interest in working with financial data and the discipline that comes with it.
AI-first working style (also non-negotiable)
  • You already use Claude Code, Cursor, Codex, or equivalent as your primary development tool - not as a side autocomplete.
  • You have opinions about how to structure prompts, when to split work into subagents, and how to keep AI output from drifting.
  • You review every AI-generated diff. You do not merge on vibes.
  • You treat the AI as a junior engineer with infinite throughput: high leverage, zero judgment, needs supervision.
  • You enjoy building tooling that makes AI more effective on your codebase - skills, evals, fixtures, integrations.
  • You see AI leverage as what makes it possible for one engineer to own a full product surface and stay close to users - not as a reason to stay heads-down in a terminal.

Strongly preferred
  • A portfolio of AI-assisted work - skills you wrote, agents you built, automations you shipped.
  • Experience being the single owner of a non-trivial service in production.
  • Experience with data-intensive or financial systems - data platforms, analytics, billing, payments, or reporting.

Why this role
Healthcare is one of the highest-leverage places software can make a difference, and the money side of a health plan is where a lot of that leverage lives. We are a company where a single engineer can own the platform that runs it. The scope is large, the data is real, the correctness bar is high, and the operating model - AI-first, human-directed, shipped daily - is the one you have been waiting for. Your day might span sitting in on an F&A working session, debugging why two systems disagree on a number, building an agent to take a manual process off someone's plate, demoing a new workflow to an F&A lead, or setting the technical strategy for your platform. If you have been looking for a role where you own the full loop - problem discovery through production - where working with data and getting the numbers exactly right actually matters, and where AI-first isn't a buzzword but the actual way work gets done, this is it.
Perks & Benefits
  • Curative Health Plan (100% employer-covered medical premiums for you and 50% coverage for dependents on the base plan.)
    • $0 copays and $0 deductibles (with completion of our Baseline Visit )
    • Preventive and primary care built in
    • Mental health support (Rula, Televero, Two Chairs, Recovery Unplugged)
    • One-on-one care navigation
    • Chronic condition programs (diabetes, weight, hypertension)
    • Maternity and family planning support
    • 24/7/365 Curative Telehealth
    • Pharmacy benefits
  • Comprehensive dental and vision coverage
  • Employer-provided life and disability coverage with additional supplemental options
  • Flexible spending accounts
  • Generous PTO policy plus 11 paid annual company holidays
  • 401K for full-time employees
  • Generous Up to 8-12 weeks paid parental leave, based on role eligibility.