DirectJobHub
Jobs · Engineering · Texas

Senior Real-Time & Application Software Developer

Emerson · Round Rock, TX · 3 wk ago
HybridEngineeringFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also we must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting mentions benefits: "We provide a market-leading 401(k) and profit-sharing plan, a variety of medical insurance plans, with dental and vision coverage, family formation benefits in addition to paid parental leave (maternal and paternal), Employee Assistance Program, tuition reimbursement, employee resource groups, recognition, and much more. Our culture prioritizes work-life balance and offers flexible time off plans, inclusive of vacation, holiday, and sick leave." So Benefits section can be included. Pay: not mentioned. Schedule: not mentioned. So we omit Pay and Schedule. We need sections: About the role (maybe from first paragraph describing role). Responsibilities (list). Requirements (maybe "FOR THIS ROLE, YOU WILL NEED:" list). Qualifications (maybe "PREFERRED QUALIFICATIONS THAT SET YOU APART:" list). Skills (maybe combine knowledge? Could embed within Requirements? But we need to follow headings: Skills maybe separate if there is skill list. The posting includes "Strong knowledge of embedded software development using C/C++, C#, or RUST", "Knowledge of Linux and/or VxWorks RTOS concepts...", "Strong problem-solving skills...". Those could go under Skills. But we also have Requirements (education/experience). Qualifications (preferred). We'll decide. We must not invent filler. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We need to preserve all substantive information. So we need to include description paragraphs, responsibilities list, requirements list, qualifications list, benefits list. We must remove duplicated lines, boilerplate like "Equal Opportunity Employer", "Work Authorization", "Accessibility Assistance", "About Us", "Why Emerson", etc. Also remove duplicated lines like "Individuals with temporary visas..." appears twice; we should keep only once? The instruction: remove duplicated lines. So we should keep only one instance of that info, maybe under Requirements? Actually it's a work authorization requirement. Could be part of Requirements. We'll include it as a bullet under Requirements. We also need to remove "No calls or agencies please." (application instruction). Also remove "Learn more about our Culture & Values and about Diversity, Equity & Inclusion at Emerson ." etc. We must not include sections like "About Us", "Why Emerson", "Our Culture & Commitment to You" maybe could be part of About the role? But we have a section "About the role" for role description. The "Our Culture & Commitment to You" is more about benefits and culture; we already have Benefits section. Could incorporate some culture description into Benefits or About the role? The instruction: include a section ONLY when posting has real, specific content for it. The posting does have content about culture and benefits. We already have Benefits. Could also have a "Culture" section but not in allowed headings list; we only allowed those headings. So we should incorporate culture description into Benefits or About the role? Probably Benefits section can include the benefits and culture description. The posting also mentions "Our Culture & Commitment to You" paragraph about flexible benefit plans, etc. That's benefits. So we can put that in Benefits. Now we need to decide what goes under each heading. About the role: Should contain the introductory paragraphs describing the role, the team, PACSystems, location, etc. We'll take the first few paragraphs up to "IN THIS ROLE, YOUR RESPONSIBILITIES WILL:" as About the role. Responsibilities: The list after "IN THIS ROLE, YOUR RESPONSIBILITIES WILL:" includes many items each starting with a capitalized word and dash. We'll turn each into

  • . Requirements: The "FOR THIS ROLE, YOU WILL NEED:" paragraph includes education/experience, knowledge, problem-solving, legal authorization. We'll turn each bullet into
  • . Also include "Legal authorization to work in the United States without sponsorship now and in the future" and the visa restriction sentence. Qualifications: The "PREFERRED QUALIFICATIONS THAT SET YOU APART:" list. We'll turn each into
  • . Skills: Could we separate skills from requirements? The posting includes "Strong knowledge of embedded software development using C/C++, C#, or RUST", "Knowledge of Linux and/or VxWorks RTOS concepts...", "Strong problem-solving skills...". Those are already in Requirements. But we could still have a Skills section that captures those technical skills. However we must not duplicate content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we put them in both Requirements and Skills, we'd duplicate. Better to place them under Skills and keep Requirements focused on education/experience and legal auth. But the "FOR THIS ROLE, YOU WILL NEED:" includes those knowledge items. So we could split: Requirements: education/experience + legal auth. Skills: technical knowledge and problem-solving. That avoids duplication. Let's parse the "FOR THIS ROLE, YOU WILL NEED:" block: "Bachelor's degree in Engineering, Computer Science, Computer Engineering, Electrical Engineering, or a related STEM discipline plus 5+ years of experience; or Master's degree plus 3+ years of experience. Strong knowledge of embedded software development using C/C++, C#, or RUST Knowledge of Linux and/or VxWorks RTOS concepts, including real-time execution, concurrency, memory management, and debugging Strong problem-solving skills and a genuine desire to understand complex, distributed control systems Legal authorization to work in the United States without sponsorship now and in the future Individuals with temporary visas such as E, F-1 (including those with OPT or CPT), H-1, H-2, L-1, B, J or TN, or who need sponsorship for work authorization now or in the future, are not eligible for hire." We'll separate: Requirements (education/experience + legal auth): - Bachelor's degree ... plus 5+ years of experience; or Master's degree plus 3+ years of experience. - Legal authorization to work in the United States without sponsorship now and in the future. - Individuals with temporary visas such as E, F-1 (including those with OPT or CPT), H-1, H-2, L-1, B, J or TN, or who need sponsorship for work authorization now or in the future, are not eligible for hire. Skills: - Strong knowledge of embedded software development using C/C++, C#, or RUST - Knowledge of Linux and/or VxWorks RTOS concepts, including real-time execution, concurrency, memory management, and debugging - Strong problem-solving skills and a genuine desire to understand complex, distributed control systems Now Qualifications (preferred): list each bullet. Benefits: combine the paragraph about benefits and culture. We also have some other paragraphs about "Our Culture & Commitment to You" that includes benefits description; we already captured. We also have "About Us" etc which we discard. Now we need to output HTML fragment with headings

    for each section. We'll produce:

    About the role

    ... paragraphs ...

    Responsibilities

    • ...
      • ...

    Requirements

    • ...
      • ...

    Skills

    • ...
      • ...

    Qualifications

    • ...
      • ...

    Benefits

    • ...
      • ...
    We need to ensure we don't include empty sections. Now we need to copy the prose for About the role: Let's extract from start up to before "IN THIS ROLE, YOUR RESPONSIBILITIES WILL:". Original text: "Job Description Are you a software engineer who is excited by the challenge of building both embedded firmware and user-facing applications that power industrial automation systems? Emerson has an exciting opportunity for you. We are looking for curious, motivated engineers who enjoy working across the full software stack, from real-time controller firmware running on Linux and VxWorks RTOS to workstation applications used by engineers to configure, program, visualize, and manage industrial automation systems. Based in Austin, Texas, you will join a diverse community and work as a contributing member of a cross-functional Agile team focused on the development of Emerson's PACSystems technologies. PACSystems is trusted by leading companies across discrete and hybrid manufacturing industries to safely and reliably control critical processes. In this role, you will contribute to both the embedded controller platform and the engineering software tools that interact with PACSystems controllers. Your work may include PLC programming capabilities, deterministic control execution, industrial communications, diagnostics, configuration, visualization, and management workflows used in demanding industrial environments. You will contribute to the design and development of next-generation PACSystems software capabilities across embedded and workstation layers. Our work includes C and C++ software development, real-time distributed computing, Linux and VxWorks RTOS environments, workstation application development, and systems where timing, reliability, usability, and predictable behavior are critical. Our team also embraces modern development practices, including automated testing, AI-assisted development, and spec-driven methods that improve quality and reduce ambiguity. You will be part of an organization led by leaders who are deeply committed to technical excellence, Agile principles, mentorship, and building an environment where engineers do their best work. If you are looking for a role where you can grow quickly, contribute meaningfully, and be part of something that has lasting real-world impact, we want to hear from you." We need to remove "Job Description" at start? It's not a heading; we can keep as part of paragraph? Probably we should keep the content but drop the label "Job Description". The instruction: do not repeat the job title as a heading; but "Job Description" is not a heading; we can keep it as part of paragraph or remove. Safer to remove it as it's likely boilerplate. We'll start paragraph after that. Thus About the role paragraph(s) will be the above text without "Job Description". We'll combine into one or multiple

    . Could split into two paragraphs for readability but not required. We'll keep as one

    . Now Responsibilities list: The text after "IN THIS ROLE, YOUR RESPONSIBILITIES WILL:" includes: "Collaborate - Contribute to a creative team atmosphere, participate in code reviews, and actively engage in Agile activities such as sprint planning and retrospectives. Take part in Hackathons, Tech Talks, and Communities of Practice with like-minded engineers. Learn from Domain Experts - Work alongside experienced engineers, product managers, and subject matter experts in industrial automation to build your understanding of the domain and learn how real-world requirements translate into software. Contribute to Specifications - Support the authoring and review of structured software specifications, gaining hands-on experience with spec-driven development practices and AI-assisted development workflows. Innovate - Write software using modern tools, frameworks, and AI-enabled development practices. Learn to apply spec-driven methodologies to improve quality, reduce ambiguity, and accelerate your own delivery. Automate - Write automated unit tests and contribute to system-level testing to support a healthy automation pipeline and a release-ready product. Iterate - Actively participate in team retrospectives and bring ideas for how the team can improve its processes and ways of working. Tech Savvy — Stay curious about emerging technologies, AI development tooling, and spec-driven methodologies, and look for opportunities to apply new skills to real problems. Always Curious — Ask questions, challenge assumptions, and take time to understand the problem before diving into solutions. Treat every task as a learning opportunity. Team Obsessed — Engage openly with your teammates, actively seek feedback

Similar jobs