Embedded Systems Architect
Embedded Systems Architect
Posted today
SENIORITY
Lead
About the role
- Hardware / Electrical: You understand electronics at a level that allows you to participate meaningfully in circuit, processor, sensor, power, communications, and hardware-interface decisions.
- Embedded Systems: You understand how hardware, firmware, software, sensors, communications, and user interfaces come together to create a complete embedded product.
- Embedded Software / Firmware: You are comfortable getting into the code, whether that means writing firmware, developing drivers, debugging low-level issues, or reviewing and improving existing embedded software.
- Systems Architecture: You can take complex product requirements and translate them into a thoughtful, scalable system architecture.
- Hands-On Execution: You don't stop at the architecture diagram. You build, prototype, test, troubleshoot, and iterate.
- Product Thinking: You understand that great engineering is about more than technology-it is about creating reliable products that solve real customer problems.
- Entrepreneurial Mindset: You are naturally curious, resourceful, and comfortable operating without a playbook. You see problems as opportunities and are willing to roll up your sleeves to get things done.
- Ownership: You want to own outcomes, not just tasks. You take initiative, make decisions, and follow problems through to resolution.
- Impact: You want to work on technology that matters and be able to look back and say, "I helped build that."
- Define the architecture for next-generation embedded products and platforms.
- Work across electrical hardware, embedded firmware, embedded software, sensors, communications, and system-level integration.
- Translate product requirements into practical system architectures and technical solutions.
- Make architecture and technology decisions while balancing performance, reliability, manufacturability, cost, and time to market.
- Design and/or contribute to embedded hardware and electrical systems.
- Develop, modify, debug, and review embedded firmware and software.
- Work directly with microcontrollers, processors, sensors, communications interfaces, and peripheral devices.
- Build prototypes and proof-of-concept systems to validate new technologies and architectural approaches.
- Troubleshoot problems across hardware and software boundaries.
- Participate directly in schematic reviews, board bring-up, firmware development, debugging, testing, and system integration.
- Establish reusable platforms, interfaces, and development standards across products.
- Collaborate closely with other engineers rather than operating in functional silos.
- Take ideas from whiteboard prototype engineering validation production.
- Identify technical risks early and develop practical solutions.
- Help establish the long-term technology roadmap for embedded systems.
- Mentor and collaborate with engineers while remaining a hands-on technical contributor.
- Work closely with product development, manufacturing, quality, service, and leadership to bring solutions to market. A Small Team Means You Do It AllThis is an environment where titles don't define the boundaries of your job. Because our engineering team is intentionally lean, everyone is expected to contribute beyond their traditional discipline. The Embedded Systems Architect may spend the morning discussing system architecture, the afternoon debugging firmware or bringing up hardware, and the next day building a prototype or solving a production issue. That's part of what makes this opportunity compelling. You won't be one small piece of a massive engineering organization. Your decisions will matter. Your work will be visible. And you will see the direct connection between your ideas and the products we deliver to customers. We're looking for someone who thrives in that environment-not someone who needs a large team and narrowly defined responsibilities around them. The right person will approach this role with an entrepreneurial, builder's mindset. You are someone who:
- Sees opportunities where others see limitations.
- Is comfortable with ambiguity and figuring things out as you go.
- Doesn't wait for perfect requirements before getting started.
- Can make thoughtful decisions with incomplete information.
- Is willing to experiment, prototype, fail fast, and iterate.
- Takes ownership when something needs to get done.
- Enjoys building new capabilities rather than simply maintaining the status quo.
- Is motivated by the opportunity to create something meaningful.
- Wants their technical expertise to have a visible and lasting impact. To Apply: For confidential consideration, please submit resume to srgjobs Bend, OR 3124 296 SW Columbia Street Suite B Bend, OR 97702
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.
