Senior Software Developer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information.
Let's craft sections:
- About the role? Could combine intro paragraph: mission, location, hybrid, benefits? But we have separate Benefits and Schedule sections. Maybe we have an "About the role" section with the introductory mission statement and location/hybrid? However the rule: Prefer a few substantive sections over many thin ones. We could have sections: Job Summary, Responsibilities, Qualifications, Benefits, Schedule, Physical/Essential Job Functions, Our Company. That's many but each substantive.
But we could combine some: maybe "Job Summary" includes the summary paragraph. "Major Responsibilities" as list. "Qualifications" as list. "Benefits" as list. "Schedule" as short p. "Physical/Essential Job Functions" as list. "Our Company" as p.
We should not include "About the role" if we already have Job Summary. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content exists. We have Responsibilities, Qualifications, Benefits, Schedule. Also we could have "Job Summary" not in the list but we can still use h3? The examples are not exhaustive; we can use any heading but they gave examples. Safer to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Responsibilities, Qualifications, Benefits, Schedule. We don't have Skills separate; we could put skills under Qualifications. We don't have Requirements separate; we could put under Qualifications. We don't have About the role; we could use that for introductory mission and location/hybrid? But we already have Schedule for hybrid. About the role could contain mission statement and location. Let's do About the role: includes mission statement, location, hybrid work model? But Schedule separate for hybrid. Might duplicate. Better to put location/hybrid in About the role and Schedule maybe not needed if we already mention hybrid there. However rule: include Schedule only if posting actually states them. It does state hybrid work model. Could be in About the role. But we can still have Schedule section with that detail; not duplicate.
We need to avoid filler. Let's decide:
Sections:
- About the role (h3): mission statement, location (Salt Lake City, UT), hybrid work model.
- Responsibilities (h3): list of major responsibilities.
- Qualifications (h3): list of qualifications (education/experience, technical skills, bonus, etc.)
- Benefits (h3): list of benefits.
- Schedule (h3): hybrid work model (maybe redundant but okay). Could omit Schedule and put hybrid in About the role. But we need to follow instruction: prefer few substantive sections over many thin ones. Having both About the role and Schedule may be thin. Better to combine: About the role includes mission, location, hybrid. Then we don't need separate Schedule. So we will not include Schedule heading.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Physical/Essential Job Functions, Our Company.
But Physical/Essential Job Functions not in examples but we can still use h3; it's substantive.
Now we need to format lists.
Let's extract content.
About the role prose: "Our team is looking to hire a senior level developer to help in our life saving mission of providing training to support to emergency dispatch services across the globe. If you’re ready to take your career to the next level while making a worthwhile impact, consider joining our team! This role is based in Salt Lake City, UT and has a hybrid work model."
We could also mention benefits? But we have separate Benefits.
Responsibilities: list items from "Major Responsibilities". Need to deduplicate duplicates.
List:
- Design and develop efficient software components for complex tasks without supervision.
- Take a high-level idea or business need, identify the underlying problem and the outcome actually wanted, and carry it through to a working, maintainable solution rather than building to the literal request.
- Steer technical direction on projects toward reusable, maintainable systems rather than one-off implementations.
- Assist in the design of application architecture, including structure, data models, and integration points, so features can be added without rework as the system grows.
- Own the integrity of code shipped on assigned projects, serving as the responsible point of contact if something breaks.
- Effectively manage development projects and report on progress.
- Effectively troubleshoot and diagnose complex software problems.
- Ensure website designs are compliant with the major browsers.
- Design intuitive and responsive web-based user interfaces.
- Anticipate, identify, and mitigate problem areas.
- Develop prototypes and proofs of concept for end users.
- Meet with users to define application requirements.
- Provide direction and guidance to less experienced staff.
- Conduct thorough, final-stage code reviews and give approval before changes are merged.
- Performs testing of websites.
- Other duties as assigned.
We should keep "Other duties as assigned." maybe keep.
Qualifications: need to parse.
Education and/or Experience: 5+ years of relevant software development experience, including 2+ years owning projects end to end: setting technical direction, refining requirements, and carrying features through launch into continuing maintenance and support.
Able to mentor/train Software Dev I and Dev II employees.
Strong hands-on experience across the stack: TypeScript and JavaScript with frameworks such as Vue and Nuxt, HTML and CSS screen layouts, server-side web services and APIs (including WCF), and MS SQL Server (T-SQL) and MySQL databases.
Real-world coding experience delivering and maintaining production software, with the depth to work effectively without AI assistance.
Proven experience directing AI development tools to build and ship complex projects, not just isolated snippets or boilerplate: breaking large problems into workable pieces, supplying the right context and specifications, and iterating toward a sound design.
Ability to critically review and validate AI-generated code, recognizing when output is incorrect, insecure, or poorly structured, and knowing the underlying technology well enough to correct it.
Solid experience with website security and security best practices.
Ability to write flexible, reusable, and documented code.
Strong analytical abilities.
Strong customer service attitude.
Proficiency with Git, including branching and pull request workflows, and the ability to troubleshoot and resolve repository problems such as merge conflicts, bad merges, and damaged history.
Strong understanding of REST architecture, and experience contributing to application-level design decisions on real projects: data models, service boundaries, and integration points, with attention to performance and long-term maintainability.
Bonus: Experience with SCORM and developing learning platforms.
Bonus: Experience with Azure (projects, web apps, blob storage, pipelines, releases, permissions).
We need to make list items; each bullet can be a sentence or phrase.
Physical/Essential Job Functions: list:
- Ability to resolve technical problems efficiently
- Coding, collaborating, developing prototypes and projects from start to final product
- Ability to communicate technical concepts to both users and programmers effectively
- Problem-solving
- Frequent computer and telephone use
- Sitting for long periods of time
- Concentrating for long periods of time
- Infrequent travel of less than 5% may be required.
Note duplicate "Ability to resolve technical problems efficiently" appears twice; keep once.
Our Company: prose: "As one of Utah's Top Places to work, IAED is a small, fast-growing provider of consulting, training, and software products for the public safety market. IAED is based in the U.S. in downtown Salt Lake City, Utah. We offer a comprehensive benefits package including medical, dental, and matching 401(k) programs, etc."
We removed EEO.
Now Benefits: list: health, dental, vision, pet, and legal insurance, PTO, company contributions to a 401K and more.
We can phrase as list items.
Now we need to output HTML fragment only.
Let's craft.
About the role
Our team is looking to hire a senior level developer to help in our life saving mission of providing training to support emergency dispatch services across the globe. If you’re ready to take your career to the next level while making a worthwhile impact, consider joining our team! This role is based in Salt Lake City, UT and has a hybrid work model.
Responsibilities
- Design and develop efficient software components for complex tasks without supervision.
- Take a high-level idea or business need, identify the underlying problem and the outcome actually wanted, and carry it through to a working, maintainable solution rather than building to the literal request.
- Steer technical direction on projects toward reusable, maintainable systems rather than one-off implementations.
- Assist in the design of application architecture, including structure, data models, and integration points, so features can be added without rework as the system grows.
- Own the integrity of code shipped on assigned projects, serving as the responsible point of contact if something breaks.
- Effectively manage development projects and report on progress.
- Effectively troubleshoot and diagnose complex software problems.
- Ensure website designs are compliant with the major browsers.
- Design intuitive and responsive web-based user interfaces.
- Anticipate, identify, and mitigate problem areas.
- Develop prototypes and proofs of concept for end users.
- Meet with users to define application requirements.
- Provide direction and guidance to less experienced staff.
- Conduct thorough, final-stage code reviews and give approval before changes are merged.
- Perform testing of websites.
- Other duties as assigned.
Qualifications
- 5+ years of relevant software development experience, including 2+ years owning projects end to end: setting technical direction, refining requirements, and carrying features through launch into continuing maintenance and support.
- Able to mentor/train Software Dev I and Dev II employees.
for prose. We need to preserve all substantive information. Let's craft sections: - About the role? Could combine intro paragraph: mission, location, hybrid, benefits? But we have separate Benefits and Schedule sections. Maybe we have an "About the role" section with the introductory mission statement and location/hybrid? However the rule: Prefer a few substantive sections over many thin ones. We could have sections: Job Summary, Responsibilities, Qualifications, Benefits, Schedule, Physical/Essential Job Functions, Our Company. That's many but each substantive. But we could combine some: maybe "Job Summary" includes the summary paragraph. "Major Responsibilities" as list. "Qualifications" as list. "Benefits" as list. "Schedule" as short p. "Physical/Essential Job Functions" as list. "Our Company" as p. We should not include "About the role" if we already have Job Summary. The instruction: use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those headings if content exists. We have Responsibilities, Qualifications, Benefits, Schedule. Also we could have "Job Summary" not in the list but we can still use h3? The examples are not exhaustive; we can use any heading but they gave examples. Safer to use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Responsibilities, Qualifications, Benefits, Schedule. We don't have Skills separate; we could put skills under Qualifications. We don't have Requirements separate; we could put under Qualifications. We don't have About the role; we could use that for introductory mission and location/hybrid? But we already have Schedule for hybrid. About the role could contain mission statement and location. Let's do About the role: includes mission statement, location, hybrid work model? But Schedule separate for hybrid. Might duplicate. Better to put location/hybrid in About the role and Schedule maybe not needed if we already mention hybrid there. However rule: include Schedule only if posting actually states them. It does state hybrid work model. Could be in About the role. But we can still have Schedule section with that detail; not duplicate. We need to avoid filler. Let's decide: Sections: - About the role (h3): mission statement, location (Salt Lake City, UT), hybrid work model. - Responsibilities (h3): list of major responsibilities. - Qualifications (h3): list of qualifications (education/experience, technical skills, bonus, etc.) - Benefits (h3): list of benefits. - Schedule (h3): hybrid work model (maybe redundant but okay). Could omit Schedule and put hybrid in About the role. But we need to follow instruction: prefer few substantive sections over many thin ones. Having both About the role and Schedule may be thin. Better to combine: About the role includes mission, location, hybrid. Then we don't need separate Schedule. So we will not include Schedule heading. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Physical/Essential Job Functions, Our Company. But Physical/Essential Job Functions not in examples but we can still use h3; it's substantive. Now we need to format lists. Let's extract content. About the role prose: "Our team is looking to hire a senior level developer to help in our life saving mission of providing training to support to emergency dispatch services across the globe. If you’re ready to take your career to the next level while making a worthwhile impact, consider joining our team! This role is based in Salt Lake City, UT and has a hybrid work model." We could also mention benefits? But we have separate Benefits. Responsibilities: list items from "Major Responsibilities". Need to deduplicate duplicates. List: - Design and develop efficient software components for complex tasks without supervision. - Take a high-level idea or business need, identify the underlying problem and the outcome actually wanted, and carry it through to a working, maintainable solution rather than building to the literal request. - Steer technical direction on projects toward reusable, maintainable systems rather than one-off implementations. - Assist in the design of application architecture, including structure, data models, and integration points, so features can be added without rework as the system grows. - Own the integrity of code shipped on assigned projects, serving as the responsible point of contact if something breaks. - Effectively manage development projects and report on progress. - Effectively troubleshoot and diagnose complex software problems. - Ensure website designs are compliant with the major browsers. - Design intuitive and responsive web-based user interfaces. - Anticipate, identify, and mitigate problem areas. - Develop prototypes and proofs of concept for end users. - Meet with users to define application requirements. - Provide direction and guidance to less experienced staff. - Conduct thorough, final-stage code reviews and give approval before changes are merged. - Performs testing of websites. - Other duties as assigned. We should keep "Other duties as assigned." maybe keep. Qualifications: need to parse. Education and/or Experience: 5+ years of relevant software development experience, including 2+ years owning projects end to end: setting technical direction, refining requirements, and carrying features through launch into continuing maintenance and support. Able to mentor/train Software Dev I and Dev II employees. Strong hands-on experience across the stack: TypeScript and JavaScript with frameworks such as Vue and Nuxt, HTML and CSS screen layouts, server-side web services and APIs (including WCF), and MS SQL Server (T-SQL) and MySQL databases. Real-world coding experience delivering and maintaining production software, with the depth to work effectively without AI assistance. Proven experience directing AI development tools to build and ship complex projects, not just isolated snippets or boilerplate: breaking large problems into workable pieces, supplying the right context and specifications, and iterating toward a sound design. Ability to critically review and validate AI-generated code, recognizing when output is incorrect, insecure, or poorly structured, and knowing the underlying technology well enough to correct it. Solid experience with website security and security best practices. Ability to write flexible, reusable, and documented code. Strong analytical abilities. Strong customer service attitude. Proficiency with Git, including branching and pull request workflows, and the ability to troubleshoot and resolve repository problems such as merge conflicts, bad merges, and damaged history. Strong understanding of REST architecture, and experience contributing to application-level design decisions on real projects: data models, service boundaries, and integration points, with attention to performance and long-term maintainability. Bonus: Experience with SCORM and developing learning platforms. Bonus: Experience with Azure (projects, web apps, blob storage, pipelines, releases, permissions). We need to make list items; each bullet can be a sentence or phrase. Physical/Essential Job Functions: list: - Ability to resolve technical problems efficiently - Coding, collaborating, developing prototypes and projects from start to final product - Ability to communicate technical concepts to both users and programmers effectively - Problem-solving - Frequent computer and telephone use - Sitting for long periods of time - Concentrating for long periods of time - Infrequent travel of less than 5% may be required. Note duplicate "Ability to resolve technical problems efficiently" appears twice; keep once. Our Company: prose: "As one of Utah's Top Places to work, IAED is a small, fast-growing provider of consulting, training, and software products for the public safety market. IAED is based in the U.S. in downtown Salt Lake City, Utah. We offer a comprehensive benefits package including medical, dental, and matching 401(k) programs, etc." We removed EEO. Now Benefits: list: health, dental, vision, pet, and legal insurance, PTO, company contributions to a 401K and more. We can phrase as list items. Now we need to output HTML fragment only. Let's craft.
About the role
Our team is looking to hire a senior level developer to help in our life saving mission of providing training to support emergency dispatch services across the globe. If you’re ready to take your career to the next level while making a worthwhile impact, consider joining our team! This role is based in Salt Lake City, UT and has a hybrid work model.
Responsibilities
- Design and develop efficient software components for complex tasks without supervision.
- Take a high-level idea or business need, identify the underlying problem and the outcome actually wanted, and carry it through to a working, maintainable solution rather than building to the literal request.
- Steer technical direction on projects toward reusable, maintainable systems rather than one-off implementations.
- Assist in the design of application architecture, including structure, data models, and integration points, so features can be added without rework as the system grows.
- Own the integrity of code shipped on assigned projects, serving as the responsible point of contact if something breaks.
- Effectively manage development projects and report on progress.
- Effectively troubleshoot and diagnose complex software problems.
- Ensure website designs are compliant with the major browsers.
- Design intuitive and responsive web-based user interfaces.
- Anticipate, identify, and mitigate problem areas.
- Develop prototypes and proofs of concept for end users.
- Meet with users to define application requirements.
- Provide direction and guidance to less experienced staff.
- Conduct thorough, final-stage code reviews and give approval before changes are merged.
- Perform testing of websites.
- Other duties as assigned.
Qualifications
- 5+ years of relevant software development experience, including 2+ years owning projects end to end: setting technical direction, refining requirements, and carrying features through launch into continuing maintenance and support.
- Able to mentor/train Software Dev I and Dev II employees.