Software Engineer V – Principal Engineer $120,000 - $160,000 Missoula/Hybrid/Remote

We need to output HTML fragment with sections: About the role? The posting includes description about ELM, mission, etc. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We have: - About the role: description of company, mission, role description. Could be "About the role" section. - Responsibilities: list under "Roles & Responsibilities". That is a list. - Requirements/Education and Experience: includes education, experience, etc. Could be "Requirements" or "Qualifications". The posting includes "Education and Experience" and "Preferred Qualifications". We need to decide sections: maybe "Requirements" for mandatory, "Preferred Qualifications" for preferred. But we have headings list: Requirements, Qualifications, Skills. We can map. We have "Education and Experience" (mandatory) and "Preferred Qualifications". Also "Skills" maybe from list of skills. We have Pay: Starting wages $120,000-$160,000. Benefits: list of benefits. Schedule: not mentioned. So we should not include Schedule. We must not include boilerplate like EEO, etc. Remove duplicated lines. We need to preserve all substantive info. Let's extract content. Company description: "ELM Utility Services is an EEO Employer - M/F/Disability/Protected Veteran Status ELM Utility Services, is a team of over 1900 employees nationwide. We are seeking highly experienced Principal Engineer who combines deep technical expertise with strong ownership, systems thinking, and leadership through influence. We are especially interested in – but do not necessarily require - engineers who understand how to build mobile applications around real business domains, field workflows, and operational Experience designing mobile solutions that reflect the way field teams actually work is highly valuable. We value engineers who think beyond individual features, take ownership of outcomes, collaborate across teams, and help evolve scalable, reliable platforms that support the company's long-term growth and mission. At ELM, our mission is important — helping keep our communities safe by reducing accidents involving underground utility infrastructure. Our engineering teams design, build, and operate enterprise-class software that powers critical operational and corporate workflows across the organization. As a Software Engineer at ELM, you are not just writing code- you are helping shape the systems that dispatch work, process field data, support regulatory compliance, improve operational efficiency, and ultimately contribute to public safety. We value engineers who think beyond individual features, take ownership of outcomes, collaborate across teams, and help evolve scalable, reliable platforms that support the company's long-term growth and mission." We can condense but must preserve all substantive info; we can't summarize away detail. However we can keep the sentences as is, maybe combine but not lose info. We need to avoid duplication: there are repeated sentences about valuing engineers etc. We should keep unique content. Let's list unique points: - ELM Utility Services is an EEO Employer (but we must remove EEO boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the EEO statement. So we drop "ELM Utility Services is an EEO Employer - M/F/Disability/Protected Veteran Status". Also later "WE ARE AN EQUAL OPPORTUNITY EMPLOYER". Remove those. - "ELM Utility Services, is a team of over 1900 employees nationwide." - "We are seeking highly experienced Principal Engineer who combines deep technical expertise with strong ownership, systems thinking, and leadership through influence." - "We are especially interested in – but do not necessarily require - engineers who understand how to build mobile applications around real business domains, field workflows, and operational Experience designing mobile solutions that reflect the way field teams actually work is highly valuable." - "We value engineers who think beyond individual features, take ownership of outcomes, collaborate across teams, and help evolve scalable, reliable platforms that support the company's long-term growth and mission." - "At ELM, our mission is important — helping keep our communities safe by reducing accidents involving underground utility infrastructure." - "Our engineering teams design, build, and operate enterprise-class software that powers critical operational and corporate workflows across the organization." - "As a Software Engineer at ELM, you are not just writing code- you are helping shape the systems that dispatch work, process field data, support regulatory compliance, improve operational efficiency, and ultimately contribute to public safety." - (repeat of valuing engineers sentence again; we can keep one.) Now Responsibilities list: - Lead large-scale technical initiatives and epics from concept through deployment and operational support. - Provide technical leadership across multiple teams and domains, helping drive architectural consistency and long-term maintainability. - Mentor and coach engineers across the organization, elevating technical capability and engineering maturity. - Collaborate with Product Managers, Team Leads, Architects, and Executive Leadership to align technical solutions with business outcomes. - Design and implement scalable, resilient, and observable distributed systems and integrations. - Drive improvements in engineering standards, SDLC practices, CI/CD pipelines, testing strategies, and operational excellence. - Champion best practices around performance, security, compliance, resiliency, and maintainability. - Participate in technical design reviews, backlog elaboration, and cross-team solutioning efforts. - Translate complex technical concepts into clear communication appropriate for both technical and non-technical audiences. - Identify systemic issues, technical debt, and architectural risks, and help lead pragmatic modernization efforts. - Contribute hands-on code and technical implementation where appropriate. - Support incident response, root cause analysis, and continuous improvement activities for production systems. - Promote a culture of ownership, accountability, collaboration, and continuous learning. Education and Experience (mandatory): - Bachelor’s degree in Computer Science, Software Engineering, or related field, or equivalent practical experience. - 12+ years of professional software engineering experience preferred. - Demonstrated success designing and delivering enterprise-scale applications and platforms. - Expert-level proficiency in modern software development practices and object-oriented programming languages such as C# and .NET. - Strong experience with modern web application development using TypeScript, JavaScript, Angular and/or React. - Deep understanding of API design, distributed systems, asynchronous processing, and integration patterns. - Strong experience with relational databases and SQL Server preferred. - Experience with cloud-native technologies and platforms such as Azure, containerization, CI/CD pipelines, and observability tooling. - Strong understanding of software architecture, scalability, security, resiliency, and performance optimization. - Experience working in Agile/Scrum product delivery environments. - Excellent communication, collaboration, and organizational skills. - Strong analytical thinking and problem-solving abilities. - Ability to influence technical direction without direct authority. Preferred Qualifications: - Experience with Azure DevOps, Git-based workflows, and modern DevOps practices. - Experience leading mobile application engineering strategy, including architecture, deployment methodology, release governance, staged rollouts, production monitoring, and continuous improvement of mobile delivery practices. - Experience designing event-driven or service-oriented architectures. - Familiarity with observability platforms such as Datadog, Azure Monitor, or similar tooling. - Postgres SQL - Experience operating within regulated or compliance-driven environments. - Demonstrated ability to lead modernization initiatives and mentor engineering teams through change. Pay: Starting wages for this position will be $120,000-$160,000 depending on experience. Benefits: Our Total Rewards Package Includes Optional benefits like Medical, Dental, Vision, Life, Disability, FSA, H.S.A., and Teladoc. Company Paid Life Insurance Paid-Time Off (PTO) for vacation and sick time 6 Paid Holidays 401(k) plan Bonuses for milestone anniversaries Competitive pay based on experience Long history of stable employment and promoting from within Opportunity to lead and modernize production systems with meaningful operational impact We need to format benefits as list. We should not include "Competitive pay based on experience" as benefit? It's more pay; but we already have Pay section. Could include but it's duplicate. Might keep as part of benefits but it's okay. We must not include sections with filler like "not specified". We have all specifics. Now decide headings: About the role (company overview + role description). Responsibilities (list). Requirements (mandatory education/experience). Qualifications (preferred). Skills maybe we could combine but we have skills listed in requirements; we could have a Skills section but we already have many skill items in requirements. To avoid thin sections, we could omit Skills and put skill details under Requirements. Or we could have Requirements and Qualifications only. The instruction: Prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. That's six sections. We must not include Schedule. Now produce HTML: use

for each section heading. Use

• for lists. Use

  for prose. We need to ensure we don't repeat job title as heading. Not needed. We need to preserve all substantive info; we must not lose any detail. Let's craft About the role paragraph(s). Could be multiple

  elements. We'll include:

  ELM Utility Services is a team of over 1,900 employees nationwide.

  We are seeking a highly experienced Principal Engineer who combines deep technical expertise with strong ownership, systems thinking, and leadership through influence.

  We are especially interested in—but do not necessarily require—engineers who understand how to build mobile applications around real business domains, field workflows, and operational experience designing mobile solutions that reflect the way field teams actually work is highly valuable.

  We value engineers who think beyond individual features, take ownership of outcomes, collaborate across teams, and help evolve scalable, reliable platforms that support the company's long-term growth and mission.

  At ELM, our mission is important—helping keep our communities safe by reducing accidents involving underground utility infrastructure.

  Our engineering teams design, build, and operate enterprise-class software that powers critical operational and corporate workflows across the organization.

  As a Software Engineer at ELM, you are not just writing code—you are helping shape the systems that dispatch work, process field data, support regulatory compliance, improve operational efficiency, and ultimately contribute to public safety.

  We removed duplicate sentence about valuing engineers (we have one). Good. Now Responsibilities:

  Responsibilities

  then
  with each bullet. Now Requirements:

  Requirements

  then
  with each bullet (mandatory). We'll include all items from Education and Experience. Now Qualifications:

  Qualifications

  then
  with preferred qualifications. Now Benefits:

  Benefits

  then
  with benefits list. Now Pay:

  Pay

  then

  Starting wages for this position will be $120,000‑$160,000 depending on experience.

  (use en dash or hyphen? We'll keep as "$120,000-$160,000"). We must not include any extra fluff. Check for any leftover boilerplate: removed EEO lines, removed "Please visit our careers page..." etc. Check for duplicated lines: we have not repeated. Now ensure we haven't missed any substantive info: The posting also includes "Opportunity to lead and modernize production systems with meaningful operational impact" which we included in benefits list. Also "Long history of stable employment and promoting from within" included. Also "Bonuses for milestone anniversaries". Also "Company Paid Life Insurance". Also "Paid-Time Off (PTO) for vacation and sick time". Also "6 Paid Holidays". Also "401(k) plan". Also "Optional benefits like Medical, Dental, Vision, Life, Disability, FSA, H.S.A., and Teladoc." Also "Competitive pay based on experience" (we have Pay section; but we could also include as benefit but it's okay). We'll keep it in benefits list maybe