Applications/Systems Engineer, Senior
City of Tacoma · Tacoma, WA · 1 mo ago
Information Technology$114k–$160k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions, selection process, supplemental info, etc. Keep substantive info: description of role, responsibilities, qualifications, desirable skills, knowledge/skills, compensation & benefits (pay details). Also maybe "About the role" from first paragraph. Let's parse.
The posting:
Position Description Tacoma Power's Power Management division is looking for an Applications/Systems Engineer, Senior to join their team! This position is responsible for the development and maintenance of the departmental computing and functional systems capability for the Resource Operations & Trading Group, which is a mission critical 24/7 operation. The Resource Operations and Trading Group optimizes Tacoma Power's resource portfolio through efficient, reliable dispatch of generation resources to maximize wholesale energy sales revenue. The wholesale energy trading activities directly impact Tacoma Power's ability to maintain low and stable rates to our customers. This position develops new software tools, helps troubleshoot production issues, implements defect fixes, and adds new features. The individual within this role will also be called upon to assist in software project quality assurance, business analyst activities and/or other support tasks. As one of the developers on the team, this position is responsible for the systems as used by the business users within Power Management. This position is extremely customer focused, relies on experience and industry best practices for support and judgment to plan and accomplish goals. This role reports to the Power Management Systems Engineering Manager. The Power Management Systems Engineering workgroup is a small team that develops custom software, integrates vendor solutions and supports the technical systems implemented for the power management operations at Tacoma Power. This is a busy workgroup that is often taking on specific technical industry challenges to solve the fast-paced problems emerging in the new energy markets.
Key Responsibilities
Develop, implement, and maintain software and system solutions for data collection, processing, and reporting, ensuring compliance with NERC and CIP requirements.
Provide production support for internal systems and third-party platforms, ensuring reliability and resolving user issues promptly.
Integrate third-party solutions into existing system architecture and software platforms.
Implement and maintain data warehousing and reporting solutions to support Resource Operations & Trading activities.
Facilitate secure and effective data sharing with utilities, regulatory agencies, and internal stakeholders.
Research, analyze, and prepare technical reports, specifications, and documentation to support system development and operations.
Continuously evaluate and adopt emerging technologies to enhance applications, tools, and processes.
Qualifications
Minimum Education* Bachelor's degree
Minimum Experience* 4 years of software development, software architecture and database/data warehouse experience
Relevant education and experience may substitute for one another on a year-for-year basis
Licensing, Certifications And Other Requirements As Assigned: Washington State Driver's License
Depending on assignment, some positions may require the ability to pass additional background checks and/or obtain additional certifications, with maintenance thereafter
Desirable Skills & Qualifications
SQL Server & SQL Server Reporting Services
Data Warehousing / SQL Server Analysis Services
ETL, Dataflows, Service Oriented Architecture
Software Development & Support
REST, WCF, SOAP, XML, gRPC
Scheduler Based Integration Platforms
Azure DevOps, Octopus, Git & other Source Control tools
CI/CD Pipeline architecture & deployment
.Net Framework / C#, .NET Core, Blazor, Entity Framework, ORM Tools
Nuget Package management
EIM & ETRM systems & software (OATI & PCI)
Stored procedures
Software Architecture
Infrastructure, Windows Server Maintenance, Certificate Management, VMWare Knowledge & Skills
Knowledge, Skills, And Abilities
Perform code reviews and provide constructive feedback and coaching to other developers to develop their skillsets.
Research, document, and apply new technologies
Multitask and prioritize multiple complex workplace projects.
Establish and maintain cooperative and effective working relationships with co-workers and peers in the electric industry.
Analyze situations accurately and adopt and effective course of action.
Integrate information from various sources and develop solutions that effectively satisfy competing objectives.
Plan and organize work.
Manage multiple priorities and meet deadlines.
Build a strong sense of teamwork and purpose within work groups.
Clearly communicate, orally and in writing, complex or contentious issues.
Establish and maintain cooperative working relationships across Tacoma Power.
Independently coordinate and facilitate discussions between work groups to resolve technical problems requiring diverse knowledge areas.
Compensation & Benefits
Pay Details: Annual Salary: $113,568.00 - $159,910.40
Employee Benefits | City of Tacoma
[then a long benefits description]
We need to include Benefits and Pay sections only if posting actually states them. It does state Pay Details and benefits description. So we can have a Pay section with salary range, and a Benefits section summarizing benefits (medical, dental, vision, paid leave, retirement, etc). We should not include generic filler like "commensurate with experience". We have actual specifics.
We must not include application instructions, selection process, supplemental info, EEO, etc. So we cut out everything after "Compensation & Benefits" that is not part of benefits description? Actually the benefits description is part of that section. We need to extract the benefits details: "The City of Tacoma provides excellent medical, dental and vision plans for the whole family; paid holidays and paid leave; participation in the Tacoma Employees' Retirement System (alternate plan for Police/Fire); continuing education and advancement opportunities and a growing variety of City-sponsored health and wellness opportunities and incentives. Medical Coverage: For eligible employees and their families, including domestic partners and dependent children age 26 or younger. Dental Coverage: For eligible employees and their families, including domestic partners and dependent children age 26 or younger. Vision Coverage: For eligible employees and their eligible dependents. Paid Leave: City employees are entitled to received paid holidays, sick/vacation leave or personal time off (PTO), depending upon union affiliation and appointment type. Insurance Plans: Employees are covered by a long-term disability plan. Short-term and expanded long-term disability insurance plans are also available to employees. The State Industrial Insurance Act also covers employees. Deferred Compensation: Income can be set aside on a pretax basis and invested for supplementation of normal retirement income. Retirement: All employees of the City, except members of the Police and Fire services, Tacoma Rail and certain project employees, are included in the Tacoma Employees' Retirement System. Information on the Tacoma Employees' Retirement System can be found at www.cityoftacoma.org or by calling (253) 502-8200. Other Employment Information Direct Deposit: Employees are paid on a bi-weekly schedule by direct deposit. Salary Increases: Based on satisfactory job performance, the City provides for a regular progression of salary increases for most classifications according to the salary schedule. Union Affiliation: Many job classifications are covered by union security provisions which require union membership, dues, or payment of equivalent service fees. Note: The provisions of this job announcement do not constitute an expressed or implied contract. Any provision contained herein may be modified and/or revoked without notice."
We should keep substantive benefit info but maybe trim overly generic lines? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all benefit details as given. However we can format as
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions, selection process, supplemental info, etc. Keep substantive info: description of role, responsibilities, qualifications, desirable skills, knowledge/skills, compensation & benefits (pay details). Also maybe "About the role" from first paragraph. Let's parse.
The posting:
Position Description Tacoma Power's Power Management division is looking for an Applications/Systems Engineer, Senior to join their team! This position is responsible for the development and maintenance of the departmental computing and functional systems capability for the Resource Operations & Trading Group, which is a mission critical 24/7 operation. The Resource Operations and Trading Group optimizes Tacoma Power's resource portfolio through efficient, reliable dispatch of generation resources to maximize wholesale energy sales revenue. The wholesale energy trading activities directly impact Tacoma Power's ability to maintain low and stable rates to our customers. This position develops new software tools, helps troubleshoot production issues, implements defect fixes, and adds new features. The individual within this role will also be called upon to assist in software project quality assurance, business analyst activities and/or other support tasks. As one of the developers on the team, this position is responsible for the systems as used by the business users within Power Management. This position is extremely customer focused, relies on experience and industry best practices for support and judgment to plan and accomplish goals. This role reports to the Power Management Systems Engineering Manager. The Power Management Systems Engineering workgroup is a small team that develops custom software, integrates vendor solutions and supports the technical systems implemented for the power management operations at Tacoma Power. This is a busy workgroup that is often taking on specific technical industry challenges to solve the fast-paced problems emerging in the new energy markets.
Key Responsibilities
Develop, implement, and maintain software and system solutions for data collection, processing, and reporting, ensuring compliance with NERC and CIP requirements.
Provide production support for internal systems and third-party platforms, ensuring reliability and resolving user issues promptly.
Integrate third-party solutions into existing system architecture and software platforms.
Implement and maintain data warehousing and reporting solutions to support Resource Operations & Trading activities.
Facilitate secure and effective data sharing with utilities, regulatory agencies, and internal stakeholders.
Research, analyze, and prepare technical reports, specifications, and documentation to support system development and operations.
Continuously evaluate and adopt emerging technologies to enhance applications, tools, and processes.
Qualifications
Minimum Education* Bachelor's degree
Minimum Experience* 4 years of software development, software architecture and database/data warehouse experience
Relevant education and experience may substitute for one another on a year-for-year basis
Licensing, Certifications And Other Requirements As Assigned: Washington State Driver's License
Depending on assignment, some positions may require the ability to pass additional background checks and/or obtain additional certifications, with maintenance thereafter
Desirable Skills & Qualifications
SQL Server & SQL Server Reporting Services
Data Warehousing / SQL Server Analysis Services
ETL, Dataflows, Service Oriented Architecture
Software Development & Support
REST, WCF, SOAP, XML, gRPC
Scheduler Based Integration Platforms
Azure DevOps, Octopus, Git & other Source Control tools
CI/CD Pipeline architecture & deployment
.Net Framework / C#, .NET Core, Blazor, Entity Framework, ORM Tools
Nuget Package management
EIM & ETRM systems & software (OATI & PCI)
Stored procedures
Software Architecture
Infrastructure, Windows Server Maintenance, Certificate Management, VMWare Knowledge & Skills
Knowledge, Skills, And Abilities
Perform code reviews and provide constructive feedback and coaching to other developers to develop their skillsets.
Research, document, and apply new technologies
Multitask and prioritize multiple complex workplace projects.
Establish and maintain cooperative and effective working relationships with co-workers and peers in the electric industry.
Analyze situations accurately and adopt and effective course of action.
Integrate information from various sources and develop solutions that effectively satisfy competing objectives.
Plan and organize work.
Manage multiple priorities and meet deadlines.
Build a strong sense of teamwork and purpose within work groups.
Clearly communicate, orally and in writing, complex or contentious issues.
Establish and maintain cooperative working relationships across Tacoma Power.
Independently coordinate and facilitate discussions between work groups to resolve technical problems requiring diverse knowledge areas.
Compensation & Benefits
Pay Details: Annual Salary: $113,568.00 - $159,910.40
Employee Benefits | City of Tacoma
[then a long benefits description]
We need to include Benefits and Pay sections only if posting actually states them. It does state Pay Details and benefits description. So we can have a Pay section with salary range, and a Benefits section summarizing benefits (medical, dental, vision, paid leave, retirement, etc). We should not include generic filler like "commensurate with experience". We have actual specifics.
We must not include application instructions, selection process, supplemental info, EEO, etc. So we cut out everything after "Compensation & Benefits" that is not part of benefits description? Actually the benefits description is part of that section. We need to extract the benefits details: "The City of Tacoma provides excellent medical, dental and vision plans for the whole family; paid holidays and paid leave; participation in the Tacoma Employees' Retirement System (alternate plan for Police/Fire); continuing education and advancement opportunities and a growing variety of City-sponsored health and wellness opportunities and incentives. Medical Coverage: For eligible employees and their families, including domestic partners and dependent children age 26 or younger. Dental Coverage: For eligible employees and their families, including domestic partners and dependent children age 26 or younger. Vision Coverage: For eligible employees and their eligible dependents. Paid Leave: City employees are entitled to received paid holidays, sick/vacation leave or personal time off (PTO), depending upon union affiliation and appointment type. Insurance Plans: Employees are covered by a long-term disability plan. Short-term and expanded long-term disability insurance plans are also available to employees. The State Industrial Insurance Act also covers employees. Deferred Compensation: Income can be set aside on a pretax basis and invested for supplementation of normal retirement income. Retirement: All employees of the City, except members of the Police and Fire services, Tacoma Rail and certain project employees, are included in the Tacoma Employees' Retirement System. Information on the Tacoma Employees' Retirement System can be found at www.cityoftacoma.org or by calling (253) 502-8200. Other Employment Information Direct Deposit: Employees are paid on a bi-weekly schedule by direct deposit. Salary Increases: Based on satisfactory job performance, the City provides for a regular progression of salary increases for most classifications according to the salary schedule. Union Affiliation: Many job classifications are covered by union security provisions which require union membership, dues, or payment of equivalent service fees. Note: The provisions of this job announcement do not constitute an expressed or implied contract. Any provision contained herein may be modified and/or revoked without notice."
We should keep substantive benefit info but maybe trim overly generic lines? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all benefit details as given. However we can format as - for list items. The benefits paragraph is prose; we could keep as
but could also break into list. The rule: Use
- for any list of duties/requirements/benefits, and
for prose. So we need to decide if benefits are a list. The benefits description includes multiple items; we could treat as a list. But the instruction says use
- for any list of duties/requirements/benefits. So we should convert benefits into a list. However we must preserve all substantive information; we can break each sentence into a list item.
Similarly for Responsibilities and Desirable Skills & Qualifications and Knowledge, Skills, Abilities we should use lists.
Qualifications: we have minimum education, experience, licensing etc. Could be list.
We need sections: About the role (maybe from first paragraph), Responsibilities, Qualifications, Skills (maybe combine Desirable Skills & Qualifications and Knowledge, Skills, Abilities), Benefits, Pay.
We should not create Schedule section because not present.
We need to avoid headings with filler. So we will include only those sections with content.
Let's craft HTML:
About the role
... (the initial description)
Responsibilities
- Develop, implement, and maintain software and system solutions for data collection, processing, and reporting, ensuring compliance with NERC and CIP requirements.
- Provide production support for internal systems and third-party platforms, ensuring reliability and resolving user issues promptly.
- Integrate third-party solutions into existing system architecture and software platforms.
- Implement and maintain data warehousing and reporting solutions to support Resource Operations & Trading activities.
- Facilitate secure and effective data sharing with utilities, regulatory agencies, and internal stakeholders.
- Research, analyze, and prepare technical reports, specifications, and documentation to support system development and operations.
- Continuously evaluate and adopt emerging technologies to enhance applications, tools, and processes.
Qualifications
- Bachelor's degree (minimum education)
- 4 years of software development, software architecture and database/data warehouse experience (minimum experience)
- Relevant education and experience may substitute for one another on a year-for-year basis
- Washington State Driver's License (as assigned)
- Depending on assignment, some positions may require the ability to pass additional background checks and/or obtain additional certifications, with maintenance thereafter
Skills
We could combine Desirable Skills & Qualifications and Knowledge, Skills, Abilities into one Skills section. But we might split into Desirable Skills and Knowledge, Skills, Abilities. However the instruction: prefer a few substantive sections over many thin ones. So maybe combine into one Skills section with two sublists? But we cannot add extra headings beyond allowed ones? The allowed headings list includes Skills. So we can put all skill-related items under Skills.
Thus we need to list:
Desirable Skills & Qualifications items:
- SQL Server & SQL Server Reporting Services
- Data Warehousing / SQL Server Analysis Services
- ETL, Dataflows, Service Oriented Architecture
- Software Development & Support
- REST, WCF, SOAP, XML, gRPC
- Scheduler Based Integration Platforms
- Azure DevOps, Octopus, Git & other Source Control tools
- CI/CD Pipeline architecture & deployment
- .Net Framework / C#, .NET Core, Blazor, Entity Framework, ORM Tools
- Nuget Package management
- EIM & ETRM systems & software (OATI & PCI)
- Stored procedures
- Software Architecture
- Infrastructure, Windows Server Maintenance, Certificate Management, VMWare
Knowledge, Skills, And Abilities items:
- Perform code reviews and provide constructive feedback and coaching to other developers to develop their skillsets.
- Research, document, and apply new technologies
- Multitask and prioritize multiple complex workplace projects.
- Establish and maintain cooperative and effective working relationships with co-workers and peers in the electric industry.
- Analyze situations accurately and adopt and effective course of action.
- Integrate information from various sources and develop solutions that effectively satisfy competing objectives.
- Plan and organize work.
- Manage multiple priorities and meet deadlines.
- Build a strong sense of teamwork and purpose within work groups.
- Clearly communicate, orally and in writing, complex or contentious issues.
- Establish and maintain cooperative working relationships across Tacoma Power.
- Independently coordinate and facilitate discussions between work groups to resolve technical problems requiring diverse knowledge areas.
We'll put all as - under Skills.
Benefits
but could also break into list. The rule: Use
- for any list of duties/requirements/benefits, and
for prose. So we need to decide if benefits are a list. The benefits description includes multiple items; we could treat as a list. But the instruction says use
- for any list of duties/requirements/benefits. So we should convert benefits into a list. However we must preserve all substantive information; we can break each sentence into a list item.
Similarly for Responsibilities and Desirable Skills & Qualifications and Knowledge, Skills, Abilities we should use lists.
Qualifications: we have minimum education, experience, licensing etc. Could be list.
We need sections: About the role (maybe from first paragraph), Responsibilities, Qualifications, Skills (maybe combine Desirable Skills & Qualifications and Knowledge, Skills, Abilities), Benefits, Pay.
We should not create Schedule section because not present.
We need to avoid headings with filler. So we will include only those sections with content.
Let's craft HTML:
About the role
... (the initial description)
Responsibilities
- Develop, implement, and maintain software and system solutions for data collection, processing, and reporting, ensuring compliance with NERC and CIP requirements.
- Provide production support for internal systems and third-party platforms, ensuring reliability and resolving user issues promptly.
- Integrate third-party solutions into existing system architecture and software platforms.
- Implement and maintain data warehousing and reporting solutions to support Resource Operations & Trading activities.
- Facilitate secure and effective data sharing with utilities, regulatory agencies, and internal stakeholders.
- Research, analyze, and prepare technical reports, specifications, and documentation to support system development and operations.
- Continuously evaluate and adopt emerging technologies to enhance applications, tools, and processes.
Qualifications
- Bachelor's degree (minimum education)
- 4 years of software development, software architecture and database/data warehouse experience (minimum experience)
- Relevant education and experience may substitute for one another on a year-for-year basis
- Washington State Driver's License (as assigned)
- Depending on assignment, some positions may require the ability to pass additional background checks and/or obtain additional certifications, with maintenance thereafter
Skills
We could combine Desirable Skills & Qualifications and Knowledge, Skills, Abilities into one Skills section. But we might split into Desirable Skills and Knowledge, Skills, Abilities. However the instruction: prefer a few substantive sections over many thin ones. So maybe combine into one Skills section with two sublists? But we cannot add extra headings beyond allowed ones? The allowed headings list includes Skills. So we can put all skill-related items under Skills. Thus we need to list: Desirable Skills & Qualifications items: - SQL Server & SQL Server Reporting Services - Data Warehousing / SQL Server Analysis Services - ETL, Dataflows, Service Oriented Architecture - Software Development & Support - REST, WCF, SOAP, XML, gRPC - Scheduler Based Integration Platforms - Azure DevOps, Octopus, Git & other Source Control tools - CI/CD Pipeline architecture & deployment - .Net Framework / C#, .NET Core, Blazor, Entity Framework, ORM Tools - Nuget Package management - EIM & ETRM systems & software (OATI & PCI) - Stored procedures - Software Architecture - Infrastructure, Windows Server Maintenance, Certificate Management, VMWare Knowledge, Skills, And Abilities items: - Perform code reviews and provide constructive feedback and coaching to other developers to develop their skillsets. - Research, document, and apply new technologies - Multitask and prioritize multiple complex workplace projects. - Establish and maintain cooperative and effective working relationships with co-workers and peers in the electric industry. - Analyze situations accurately and adopt and effective course of action. - Integrate information from various sources and develop solutions that effectively satisfy competing objectives. - Plan and organize work. - Manage multiple priorities and meet deadlines. - Build a strong sense of teamwork and purpose within work groups. - Clearly communicate, orally and in writing, complex or contentious issues. - Establish and maintain cooperative working relationships across Tacoma Power. - Independently coordinate and facilitate discussions between work groups to resolve technical problems requiring diverse knowledge areas. We'll put all as - under Skills.
Benefits
- for any list of duties/requirements/benefits. So we should convert benefits into a list. However we must preserve all substantive information; we can break each sentence into a list item.
Similarly for Responsibilities and Desirable Skills & Qualifications and Knowledge, Skills, Abilities we should use lists.
Qualifications: we have minimum education, experience, licensing etc. Could be list.
We need sections: About the role (maybe from first paragraph), Responsibilities, Qualifications, Skills (maybe combine Desirable Skills & Qualifications and Knowledge, Skills, Abilities), Benefits, Pay.
We should not create Schedule section because not present.
We need to avoid headings with filler. So we will include only those sections with content.
Let's craft HTML: