1

Rf Embedded Software Engineer Jobs in Micronesia

We are hiring a Software Engineer dedicated to our Shared Services operation. This is a ticket ... Embedded directly with Shared Services daily * Ticket queue is your primary input (Slack, ClickUp ...

$122K - $161K/yr

We are looking for a Senior Software Engineer - Server Manageability! NVIDIA's invention of the GPU ... Experience with C/C++ development, bash/python for scripting, and debugging skills in embedded ...

$129K - $176K/yr

... embedded in every GPU that enables our profiling and monitoring tools to capture data and provide ... Join our technically diverse team of GPU architects, software engineers and deep learning experts ...

... real-time / embedded systems * Experience working at the hardware-software boundary (system ... S. or Ph.D. in Electrical Engineering, Computer Engineering, or related field * 10+ years of ...

$108K - $150K/yr

... incorporating software, firmware, and hardware security elements. The ideal candidate brings ... Minimum 8 years of experience in DoD embedded systems and hardware design, including SBC, FPGA ...

$94K - $130K/yr

... software, firmware, and hardware security elements. The ideal candidate brings strong expertise in ... Minimum 5 years of experience in DoD embedded systems and hardware design, including SBC, FPGA ...

$144K - $190K/yr

... software, firmware, and hardware security elements. The ideal candidate brings deep expertise in ... Minimum 15 years of experience in DoD embedded systems and hardware design (SBC, FPGA, switch, and ...

Rf Embedded Software Engineer information

What are some common challenges faced by RF Embedded Software Engineers when integrating software with hardware components?

RF Embedded Software Engineers often encounter challenges related to ensuring reliable communication between software and RF hardware modules, particularly due to signal interference, timing constraints, and hardware-software compatibility issues. Debugging and testing in real-world environments can be complex, as subtle hardware anomalies may require close collaboration with hardware engineers for troubleshooting. Additionally, optimizing code for limited memory and processing power while maintaining low latency is a frequent challenge. Familiarity with embedded debugging tools and effective cross-disciplinary teamwork are essential for overcoming these hurdles.

What are RF Embedded Software Engineers?

RF Embedded Software Engineers are professionals who design, develop, and troubleshoot software that runs on embedded systems with a focus on radio frequency (RF) communications. They integrate hardware and software components to enable wireless communication in devices such as radios, IoT devices, and wireless sensors. Their work often involves programming microcontrollers, optimizing signal processing, and ensuring reliable data transmission. These engineers collaborate closely with hardware and RF design teams to deliver efficient and robust wireless solutions.

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

AspectRf Embedded Software EngineerRf Firmware Engineer
CredentialsBachelor's in Electrical Engineering, Computer Science, or related; experience with embedded systemsBachelor's or higher in Electrical Engineering, Computer Engineering; firmware development experience
Work EnvironmentDesigning and developing embedded software for RF hardware in labs or office settingsWriting low-level firmware for RF devices, often in manufacturing or R&D labs
Industry UsageWireless communication, telecommunications, aerospaceWireless devices, RF modules, IoT products

Both roles focus on RF technology and embedded systems, but Rf Embedded Software Engineers typically develop higher-level embedded software, while Rf Firmware Engineers work on low-level firmware directly controlling RF hardware. The roles often overlap, but the main difference lies in the level of software abstraction and specific responsibilities.

What are the key skills and qualifications needed to thrive as an RF Embedded Software Engineer, and why are they important?

To thrive as an RF Embedded Software Engineer, you need a solid background in embedded systems, RF design principles, digital signal processing, and a relevant degree such as electrical engineering or computer engineering. Familiarity with programming languages like C/C++, RF simulation tools (such as ADS or HFSS), and embedded development platforms is typically required, and certifications in wireless communications can be advantageous. Strong problem-solving skills, attention to detail, and effective teamwork and communication abilities help professionals excel in complex project environments. These competencies are critical for designing reliable, high-performance RF systems that meet industry standards and operational requirements.
What job categories do people searching Rf Embedded Software Engineer jobs in Micronesia look for? The top searched job categories for Rf Embedded Software Engineer jobs in Micronesia are:
Infographic showing various Rf Embedded Software Engineer job openings in Micronesia as of July 2026, with employment types broken down into 95% Full Time, 3% Part Time, and 2% Contract. Highlights an 84% Physical, 5% Hybrid, and 11% Remote job distribution.

Software Engineer - Shared Services

Extenteam Careers

On-site

Other

Posted 5 days ago


Job description

About Extenteam

Extenteam is an AI-driven operations platform for short-term rental property managers. We handle guest communication and daily workflows for over 80,000 properties through a proprietary platform (Tailwind) that combines AI automation with human-in-the-loop oversight. We are headquartered in Miami with our Shared Services team based in Manila.

We are hiring a Software Engineer dedicated to our Shared Services operation. This is a ticket-driven role focused on rapidly solving real problems for the people who run our service operation every day.

The Role

Your customers are internal: our agents in Manila, our Ops Leads and Team Leads, our Customer Success team, and our enterprise clients when they escalate technical issues. Every day, these groups file tickets describing things that are broken, slow, missing, or could be automated. Your job is to work through that queue, ship fixes, and build the tooling that compounds over time.

This is not a roadmap-driven engineering role. You are not waiting for a PM to scope work. You are reading tickets, asking the right clarifying questions, prioritizing what matters, and shipping working code fast.

You report into Engineering and partner directly with the Head of Operations and the Head of Shared Services Operations.

What You Will Do Every Day
  • Triage incoming tickets from agents, Team Leads, Customer Success, and clients
  • Diagnose the underlying problem (often it is not what the ticket says)
  • Ship fixes, automations, and small tools that solve the immediate need
  • Identify patterns across tickets and build durable solutions that prevent the same ticket from coming back
  • Pair with operations users to validate that your fix actually worked
  • Maintain and improve the internal tools you build over time
What You Will Build

Examples of work you would own:

  • An anomaly detector that flags AI replies violating OTA platform rules (Airbnb, VRBO ToS) before they reach the guest
  • A daily QA sampling tool that scores AI and agent responses and routes failures back into the knowledge base
  • A scheduling system that matches agent shifts to guest volume curves by hour and channel
  • A real-time operational dashboard pulling from Tailwind, Aircall, and HubSpot
  • Integrations between internal tools that today are connected by manual data exports
  • One-off scripts that solve a specific client or agent ticket and live as long as they need to
  • AI workflows that automate repetitive operational tasks (escalation routing, KB gap detection, client reporting)

Some of what you ship will be polished products that live for years. Some will be quick scripts that solve one ticket and never run again. Both matter.

What This Role Is Not
  • Not a customer-facing platform engineering role. You are not shipping product code to clients
  • Not a back-office IT role. You are building real software with real users
  • Not a project manager wrapped in an engineer title. You write code daily
  • Not a role where you wait for tickets to be perfectly scoped before you start. You scope them yourself
Required Experience
  • 4+ years of software engineering experience, with at least 2 years shipping production code
  • Direct experience building internal tools, automations, or operational systems
  • Comfort working from a ticket queue (support engineering, forward-deployed engineering, or internal tooling background is ideal)
  • Product mindset: comfortable talking directly to non-technical users, scoping problems, and prioritizing tradeoffs
  • Track record of shipping fast in environments without dedicated PMs or designers
  • Experience working asynchronously with distributed teams
Required Technical Skills
  • Strong fluency in Python and/or TypeScript
  • Experience with at least one workflow automation platform (n8n, Zapier, Make, Temporal, or similar)
  • Comfortable with agentic coding tools (Claude Code, Cursor, Replit Agent)
  • Database fluency (PostgreSQL preferred), able to write your own queries and design schemas
  • API integration experience (REST, webhooks, third-party SaaS APIs)
  • Prompt engineering experience with production AI systems (OpenAI, Anthropic, or similar)
Strongly Preferred
  • Experience as a forward-deployed engineer or solutions engineer at a B2B SaaS company
  • Background in contact center, customer support, or service operations tooling
  • Short-term rental, hospitality, or property management domain knowledge
  • Experience integrating with Guesty, Hostaway, OwnerRez, Aircall, or HubSpot APIs
  • Track record of deploying AI agents in production (not just prototypes)
How You Will Work
  • Embedded directly with Shared Services daily
  • Ticket queue is your primary input (Slack, ClickUp, email, escalations from CS)
  • Weekly syncs with Head of Operations and Head of Shared Services Operations to align on priorities
  • Async collaboration with the broader Engineering team
  • You own scoping, building, testing, and deployment of your work
  • We expect 4 hours of overlap with Miami time (Eastern Time) daily
Location

Remote, based in Europe or South America.