> Markdown version of [/jobs/ext/4758667-software-engineer](https://www.wearedevelopers.com/jobs/ext/4758667-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer - **Company:** PDS Inc. - **Location:** Doral, FL, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Systems Engineering, Assembly Language, Audio Signal Processing, C++ (Programming Language), Codecs, Software Debugging, Software Architecture, Real-Time Operating Systems, Software Tools, Requirements Management, Requirements Traceability, SAS (Software), Software Engineering, MagicDraw, Software Verification, DO-178B - **Published:** November 17, 2026 - **Apply:** https://www.thejobnetwork.com/job/1c28b87a-520a-48c1-b6f8-c7c28e45009c/software-engineer ## About the Role n * Bachelor of Science in Software, Computer, or Electrical Engineering (Master's degree a plus). \n * 7+ years of experience in the development, architecture, and maintenance of high-level and structured assembly language software, including demonstrated ownership of software architecture on at least one DO-178B/C program. \n * Demonstrated experience leading technical design decisions and mentoring other engineers \n * Minimum 7 years of experience with C/C++ in embedded, real-time environments, including architecture-level design experience. \n * Strong ability to read schematics, troubleshoot hardware, and guide hardware/software partitioning decisions. \n * Solid working knowledge of the DO-178B/DO-178C software development process, including experience producing or reviewing lifecycle data (PSAC, SDD, SAS, SVP). \n * Working knowledge of requirements management and modeling tools (e.g., DOORS, CAMEO/MagicDraw, SCADE) a plus., * Strong familiarity with DSP algorithms (FIR, IIR, Tone Detection) and their application at an architectural level. \n * Experience applying DSP techniques to audio processing. \n * Familiarity with Audio CODECs and audio signal chains. \n * Familiarity with the Analog Devices Inc. family of DSP ICs for embedded applications. \n * Experience with DSP software development tools (e.g., CrossCore Embedded Studio). \n * Familiarity with avionics data buses and protocols (e.g., ARINC 429, MIL-STD-1553) preferred. \n * Experience with real-time operating systems and time/space partitioning concepts (e.g., ARINC 653) preferred. ## Description The Software Engineer III is a senior, architecture-level role responsible for defining and evolving the software architecture of embedded and DSP-based systems used in a commercial aircraft environment. This individual leads technical design decisions across one or more projects, drives architecture and trade-study reviews, ensures compliance with DO-178B/DO-178C processes, and provides technical mentorship to less-experienced engineers. The role combines hands-on development with architectural ownership, requirements traceability, and cross-discipline technical leadership., n The essential functions include, but are not limited to: \n * Define, document, and maintain the software architecture for avionic equipment, ensuring designs are robust, testable, and consistent with safety and regulatory requirements under DO-178B/DO-178C. \n * Lead the design, debug, and documentation of assembly language and high-level software at the project and system level. \n * Conduct architecture reviews, technical assessments, and trade studies; evaluate competing technical solutions and recommend the best path forward. \n * Provide technical leadership, guidance, and mentorship to Software Engineer I/II personnel and review their design and code. \n * Partner with project engineers, systems engineers, and hardware personnel to determine software/hardware partitioning across one or more ongoing projects. \n * Own and drive requirements specification, allocation, and bidirectional traceability for software components. \n * Lead the software verification process for architecture and software of own design and that of other engineers; define verification strategy for new components. \n * Generate and review architectural and design documentation (e.g., SDD, SAS) in accordance with current GEI procedures and standards. \n * Serve as technical point of contact for the isolation, root-cause analysis, and rectification of complex problems reported by customers following product release. \n * Support proposals, technical estimates, and certification activities by providing architectural and technical input.