Permit Technician I/II/III- C (EDV)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info. Remove boilerplate like application instructions, contact info? The instructions say remove application instructions. The contact info for technical issues and HR contact is application instructions? Probably yes, remove. Also remove "Job Posting End Date". Also remove "If you experience technical issues..." etc. Also remove "Important: To be eligible..." etc? That's part of requirements? It's about eligibility; maybe keep as part of Requirements? It says applicants must meet minimum qualifications; that's redundant. Could keep as note but maybe it's boilerplate. Safer to keep only substantive: minimum qualifications, responsibilities, pay, benefits, schedule.
We need to avoid duplicating lines. The posting repeats similar text for each level. We can combine? But must preserve all substantive info; we can summarize? The instruction: "Do NOT invent or summarize away detail." So we cannot summarize away detail; we must keep all details. However we can combine similar bullet points if they are same across levels? Might be considered summarizing. Safer to keep each level's details separately.
We need to decide sections: About the role (job summary). Responsibilities: we have description of duties for each level. Could list bullet points per level? Might be long. Could have subheadings? Not allowed; only h3 for section headings. Could embed paragraphs describing each level.
We could have
About the role
with paragraphs describing each level's summary. Then Responsibilities
with bullet list of duties (maybe combine common duties). But we need to preserve all detail; if we combine we might lose level-specific nuance. However the duties are similar across levels with increasing responsibility. Could we list bullet points per level? Could do nested lists? Not prohibited. Use - for any list. Could have multiple
sections.
Simplify: Provide three subsections within Responsibilities using ? Not allowed. Only h3 for section headings. So we cannot use headings for sub-sections. Could use
with bold? Not allowed? Not prohibited but better to keep plain.
We could list responsibilities as paragraphs per level.
Similarly Requirements: list minimum qualifications per level.
Pay: list salary ranges per level.
Benefits: mention full-time contract benefits same as regular full-time, renewable one-year.
Schedule: full-time.
Let's craft.
We must not include markdown fences. Just raw HTML.
Let's produce:
About the role
Permit Technician I-C: Under the direction of the Customer Service Supervisor, performs responsible work involving the processing and issuance of permits and/or review and issuance of Business Tax Receipts within the Permitting Services Division. Utilizes customer service skills, exercises discretion, and incorporates tact and diplomacy to explain basic code requirements and office policies in person, over the phone, and electronically.
Permit Technician II-C: Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits. Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and upon completion through observation, discussions, and review of reports.
Permit Technician III-C: Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits. Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and upon completion through observation, discussions, and review of reports.
But note II and III descriptions are identical? Actually they are same text; maybe a copy error. We'll keep as is.
Responsibilities: maybe we can list duties as bullet points common across levels: processing permits, reviewing applications, customer service, explaining code requirements, discretion, tact, diplomacy, general office work, computer work, public contact, performance review. But that would be summarizing; risk of losing detail. However the detail is essentially same across levels; summarizing may be acceptable? The instruction: "Do NOT invent or summarize away detail." Summarizing could be considered summarizing away detail. Safer to keep the paragraphs as responsibilities (they already describe duties). So we could rename section to "Responsibilities" and keep same paragraphs.
But then we have duplicate content between About the role and Responsibilities. Might be redundant but okay.
Alternatively we could treat About the role as summary (short) and Responsibilities as detailed duties. The posting already has detailed duties in the paragraphs; we could split: About the role: brief summary (maybe first sentence). Responsibilities: the rest.
Let's extract: For each level, first sentence is summary: "Under the direction of the Customer Service Supervisor, performs responsible work involving the processing and issuance of permits and/or review and issuance of Business Tax Receipts within the Permitting Services Division." For II and III: "Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits."
We could keep that as About the role, and then Responsibilities: rest of sentences.
Let's do that.
Now Requirements: list minimum qualifications per level as bullet list? Could be - for each level's qualifications.
We'll produce:
Requirements
- Permit Technician I-C: High School Diploma/G.E.D. Certificate and six (6) months of customer service experience involving public contact, preferably in zoning, building, engineering, fire protection, planning, business tax receipts, or related areas; or an equivalent combination of education, training, and experience. Must effectively communicate both verbally and in written form, and possess basic computer skills.
- Permit Technician II-C: High School Diploma/G.E.D. Certificate and two (2) years of customer service experience involving considerable public contact, preferably in zoning, building, engineering, occupational licensing, fire permitting, planning, or related areas; or an equivalent combination of education, training, and experience. Must effectively communicate both verbally and in written form, and possess basic computer skills.
- Permit Technician III-C: High School Diploma/G.E.D. Certificate and three (3) years of customer service experience involving considerable public contact, preferably in zoning, building, engineering, occupational licensing, fire permitting, planning, or related areas; or an equivalent combination of education, training, and experience. Must effectively communicate both verbally and in written form, and possess basic computer skills.
Pay: list salary ranges.
Pay
- Permit Technician I: $18.92 – $24.12 per hour
- Permit Technician II: $21.09 – $26.90 per hour
- Permit Technician III: $22.27 – $28.40 per hour
Benefits: mention full-time contract with same benefits as regular full-time, contracts renewable for one year.
Benefits
This is a full-time CONTRACT position with the same benefits as Regular full-time. Most contracts are renewable for terms of one year.
Schedule: full-time.
Schedule
Full-time
We should not include any boilerplate like contact info, end date, application instructions, etc.
Check for any leftover: we removed "Job Posting End Date - Applications will no longer be accepted starting 09-25-2026". Removed contact lines. Removed "If you experience technical issues...". Removed "Important: To be eligible..." etc. Removed "If this posting indicates a degree is required..." etc.
We kept all substantive info: job summary, responsibilities, qualifications, pay, benefits, schedule.
Check duplication: About the role paragraphs we wrote; Responsibilities we didn't include yet. Actually we omitted Responsibilities section. We need to include Responsibilities. We have About the role (summary). We need Responsibilities (detailed duties). Let's add Responsibilities section with the remaining sentences after the first sentence for each level.
Let's craft:
For I-C: after first sentence: "Utilizes customer service skills, exercises discretion, and incorporates tact and diplomacy to explain basic code requirements and office policies in person, over the phone, and electronically."
For II-C: after first sentence: "Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and upon completion through observation, discussions, and review of reports."
For III-C: same as II-C.
We'll put these in or
? They are prose, so .
Thus:
About the role
Permit Technician I-C: Under the direction of the Customer Service Supervisor, performs responsible work involving the processing and issuance of permits and/or review and issuance of Business Tax Receipts within the Permitting Services Division.
Permit Technician II-C: Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits.
Permit Technician III-C: Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits.
Responsibilities
Permit Technician I-C: Utilizes customer service skills, exercises discretion, and incorporates tact and diplomacy to explain basic code requirements and office policies in person, over the phone, and electronically.
Permit Technician II-C: Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and upon completion through observation, discussions, and review of reports.
Permit Technician III-C: Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and
for prose. We need to preserve all substantive info. Remove boilerplate like application instructions, contact info? The instructions say remove application instructions. The contact info for technical issues and HR contact is application instructions? Probably yes, remove. Also remove "Job Posting End Date". Also remove "If you experience technical issues..." etc. Also remove "Important: To be eligible..." etc? That's part of requirements? It's about eligibility; maybe keep as part of Requirements? It says applicants must meet minimum qualifications; that's redundant. Could keep as note but maybe it's boilerplate. Safer to keep only substantive: minimum qualifications, responsibilities, pay, benefits, schedule. We need to avoid duplicating lines. The posting repeats similar text for each level. We can combine? But must preserve all substantive info; we can summarize? The instruction: "Do NOT invent or summarize away detail." So we cannot summarize away detail; we must keep all details. However we can combine similar bullet points if they are same across levels? Might be considered summarizing. Safer to keep each level's details separately. We need to decide sections: About the role (job summary). Responsibilities: we have description of duties for each level. Could list bullet points per level? Might be long. Could have subheadings? Not allowed; only h3 for section headings. Could embed paragraphs describing each level. We could have
About the role
with paragraphs describing each level's summary. ThenResponsibilities
with bullet list of duties (maybe combine common duties). But we need to preserve all detail; if we combine we might lose level-specific nuance. However the duties are similar across levels with increasing responsibility. Could we list bullet points per level? Could do nested lists? Not prohibited. Use- for any list. Could have multiple
- sections.
Simplify: Provide three subsections within Responsibilities using
- for each level's qualifications.
We'll produce:
Requirements
- Permit Technician I-C: High School Diploma/G.E.D. Certificate and six (6) months of customer service experience involving public contact, preferably in zoning, building, engineering, fire protection, planning, business tax receipts, or related areas; or an equivalent combination of education, training, and experience. Must effectively communicate both verbally and in written form, and possess basic computer skills.
- Permit Technician II-C: High School Diploma/G.E.D. Certificate and two (2) years of customer service experience involving considerable public contact, preferably in zoning, building, engineering, occupational licensing, fire permitting, planning, or related areas; or an equivalent combination of education, training, and experience. Must effectively communicate both verbally and in written form, and possess basic computer skills.
- Permit Technician III-C: High School Diploma/G.E.D. Certificate and three (3) years of customer service experience involving considerable public contact, preferably in zoning, building, engineering, occupational licensing, fire permitting, planning, or related areas; or an equivalent combination of education, training, and experience. Must effectively communicate both verbally and in written form, and possess basic computer skills.
Pay
- Permit Technician I: $18.92 – $24.12 per hour
- Permit Technician II: $21.09 – $26.90 per hour
- Permit Technician III: $22.27 – $28.40 per hour
Benefits
This is a full-time CONTRACT position with the same benefits as Regular full-time. Most contracts are renewable for terms of one year.
Schedule: full-time.Schedule
Full-time
We should not include any boilerplate like contact info, end date, application instructions, etc. Check for any leftover: we removed "Job Posting End Date - Applications will no longer be accepted starting 09-25-2026". Removed contact lines. Removed "If you experience technical issues...". Removed "Important: To be eligible..." etc. Removed "If this posting indicates a degree is required..." etc. We kept all substantive info: job summary, responsibilities, qualifications, pay, benefits, schedule. Check duplication: About the role paragraphs we wrote; Responsibilities we didn't include yet. Actually we omitted Responsibilities section. We need to include Responsibilities. We have About the role (summary). We need Responsibilities (detailed duties). Let's add Responsibilities section with the remaining sentences after the first sentence for each level. Let's craft: For I-C: after first sentence: "Utilizes customer service skills, exercises discretion, and incorporates tact and diplomacy to explain basic code requirements and office policies in person, over the phone, and electronically." For II-C: after first sentence: "Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and upon completion through observation, discussions, and review of reports." For III-C: same as II-C. We'll put these inor
- ? They are prose, so
. Thus:
About the role
Permit Technician I-C: Under the direction of the Customer Service Supervisor, performs responsible work involving the processing and issuance of permits and/or review and issuance of Business Tax Receipts within the Permitting Services Division.
Permit Technician II-C: Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits.
Permit Technician III-C: Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits.
Responsibilities
Permit Technician I-C: Utilizes customer service skills, exercises discretion, and incorporates tact and diplomacy to explain basic code requirements and office policies in person, over the phone, and electronically.
Permit Technician II-C: Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and upon completion through observation, discussions, and review of reports.
Permit Technician III-C: Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and
? Not allowed. Only h3 for section headings. So we cannot use headings for sub-sections. Could use
with bold? Not allowed? Not prohibited but better to keep plain. We could list responsibilities as paragraphs per level. Similarly Requirements: list minimum qualifications per level. Pay: list salary ranges per level. Benefits: mention full-time contract benefits same as regular full-time, renewable one-year. Schedule: full-time. Let's craft. We must not include markdown fences. Just raw HTML. Let's produce:
About the role
Permit Technician I-C: Under the direction of the Customer Service Supervisor, performs responsible work involving the processing and issuance of permits and/or review and issuance of Business Tax Receipts within the Permitting Services Division. Utilizes customer service skills, exercises discretion, and incorporates tact and diplomacy to explain basic code requirements and office policies in person, over the phone, and electronically.
Permit Technician II-C: Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits. Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and upon completion through observation, discussions, and review of reports.
Permit Technician III-C: Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits. Work involves general office, clerical, and computer work as assigned. Has considerable public contact and must exercise discretion, tact, and diplomacy in explaining code requirements and answering questions in person and over the phone. Work is performed under general supervision. Performance is reviewed while in progress and upon completion through observation, discussions, and review of reports.
But note II and III descriptions are identical? Actually they are same text; maybe a copy error. We'll keep as is. Responsibilities: maybe we can list duties as bullet points common across levels: processing permits, reviewing applications, customer service, explaining code requirements, discretion, tact, diplomacy, general office work, computer work, public contact, performance review. But that would be summarizing; risk of losing detail. However the detail is essentially same across levels; summarizing may be acceptable? The instruction: "Do NOT invent or summarize away detail." Summarizing could be considered summarizing away detail. Safer to keep the paragraphs as responsibilities (they already describe duties). So we could rename section to "Responsibilities" and keep same paragraphs. But then we have duplicate content between About the role and Responsibilities. Might be redundant but okay. Alternatively we could treat About the role as summary (short) and Responsibilities as detailed duties. The posting already has detailed duties in the paragraphs; we could split: About the role: brief summary (maybe first sentence). Responsibilities: the rest. Let's extract: For each level, first sentence is summary: "Under the direction of the Customer Service Supervisor, performs responsible work involving the processing and issuance of permits and/or review and issuance of Business Tax Receipts within the Permitting Services Division." For II and III: "Performs responsible specialized clerical work involving the receipt, review, and processing applications for zoning, building, sewer connection, public works improvements, fire, occupational licensing, and other permits." We could keep that as About the role, and then Responsibilities: rest of sentences. Let's do that. Now Requirements: list minimum qualifications per level as bullet list? Could be - for each level's qualifications.
We'll produce: