Principal Engineer - Software Development
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting.
The posting includes:
- Intro paragraph about Verizon, V Team, etc. Could be "About the role" or maybe "About the role" is appropriate.
- "What You’ll Be Doing..." section: responsibilities.
- "What We’re Looking For...": includes requirements, qualifications, skills, etc.
- "Where you’ll be working": hybrid schedule info.
- "Scheduled Weekly Hours 40": schedule.
- "Benefits And Compensation": benefits and pay.
- Salary range.
We need to avoid repeating job title as heading. No Job ID etc.
We need to include sections only if content exists.
We need to use for each section heading.
Inside sections: Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to drop EEO statement, benefits boilerplate? Actually benefits section we need to keep substantive benefits info. The posting includes benefits description: medical, dental, vision, etc. Also 401(k), holidays, personal days, parental leave, adoption assistance, tuition assistance, etc. Also mention premium pay etc. Also salary range.
We need to include Pay section if posting actually states them. It does: salary range $120,500 - $231,000. Also mentions incentive based position, potential to earn more, etc. So we should include Pay section.
Schedule: posting says "Scheduled Weekly Hours 40" and hybrid role: defined work location includes working from home and minimum of three days per week in the office. So we have schedule info.
Thus we will have sections: About the role (intro), Responsibilities (What You’ll Be Doing...), Requirements (maybe combine qualifications and skills?), Qualifications (maybe separate?), Skills (maybe separate?), Benefits, Pay, Schedule.
But we need to avoid thin sections. Could combine Requirements and Qualifications into one? However the instruction says use headings for those specific names if content exists. We have content for Requirements (the "What We’re Looking For..." includes bullet-like list of requirements). Also there are "Even better if you have one or more of the following:" which could be qualifications or preferred qualifications. Could treat as Qualifications.
Skills: maybe we can extract skills from responsibilities: building applications, AI toolchain, agentic workflows, data plumbing, evaluation harnesses, demo/ship/iterate. Could be a Skills section.
But we need to avoid duplication. Let's decide:
- About the role: intro paragraph(s) about Verizon, V Team, mission.
- Responsibilities: the "What You’ll Be Doing..." bullet list (though it's paragraph with bold headings). We'll convert each responsibility into
- .
- Requirements: the mandatory requirements list: Bachelor’s degree or four or more years of work experience; Six or more years of relevant experience; 5+ years of experience building and shipping production software end-to-end; Experience shipping LLM applications; Demonstrated experience integrating data across complex imperfect systems, strong SQL, cloud GCP, Looker.
- Qualifications: the "Even better if you have one or more of the following:" list (preferred qualifications). Could be separate.
- Skills: maybe we can combine responsibilities and qualifications? But we need to follow instruction: Use headings for those specific names if content exists. We have content for Skills? Could extract skills like: software development, LLM applications, prompt engineering, agent design, SQL, GCP, Looker, data integration, evaluation harnesses, CI/CD, stakeholder demo, etc. Could be a Skills section.
But we might be duplicating content. However instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we put skills in a separate section, we need to ensure we don't lose any info. Could we instead put skills within Responsibilities or Requirements? The instruction says use
- for any list of duties/requirements/benefits. So we can treat responsibilities as list, requirements as list, benefits as list. Skills could be a list as well.
But we need to avoid thin sections. If we create Skills section with just a few items, maybe it's okay. However we could also merge Skills into Responsibilities (since responsibilities already list skills). But the instruction says use headings for those specific names if content exists. It doesn't forbid merging content across headings; but we need to include a section only when posting has real, specific content for it. If we put skills content under Responsibilities, we still have a Skills section? No, we would not have Skills section then. That's okay if we don't have specific content for Skills beyond what's already covered. But we might lose explicit skill enumeration. However the responsibilities already enumerate skills implicitly. The instruction says preserve ALL substantive information; we can preserve them under Responsibilities. So we may not need a separate Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule.
Now we need to format.
We need to strip boilerplate: EEO statement, "Equal Employment Opportunity Verizon is an equal opportunity employer..." etc. Also "Where you’ll be working" we need to keep schedule info but not the heading? We'll put schedule info under Schedule section.
We need to keep "Scheduled Weekly Hours 40" and hybrid details.
We need to keep benefits description.
We need to keep salary range.
We need to keep "Depending on the role, employees have the opportunity to receive compensation in the form of premium pay such as overtime, shift differential, holiday pay, allowances, etc." and "Newly hired employees receive up to 15 days of vacation per year..." etc. That's benefits.
We need to avoid duplication: The benefits paragraph includes many items; we can list them as
- .
Now craft HTML.
We'll start with
About the role
then ...
containing the intro paragraphs (maybe two paragraphs). We'll combine them.
Intro paragraphs:
"When you join Verizon You want more out of a career. A place to share your ideas freely — even if they’re daring or different. Where the true you can learn, grow, and thrive. At Verizon, we power and empower how people live, work and play by connecting them to what brings them joy. We do what we love — driving innovation, creativity, and impact in the world. Our V Team is a community of people who anticipate, lead, and believe that listening is where learning begins. In crisis and in celebration, we come together — lifting our communities and building trust in how we show up, everywhere & always. Want in? Join the #VTeamLife."
We can keep as one .
Now Responsibilities:
Responsibilities
then - each responsibility.
Responsibilities list from posting:
- Build applications from specifications: Take completed business requirements specifications and deliver working software against them as a hands-on individual contributor (write code, configure platforms, wire data, and demo results).
- Build and operate the AI toolchain: Own internal tooling making the spec-to-build loop repeatable, including structured intake requirements-interview agents, reusable prompt/context/evaluation scaffolding, and build telemetry instrumentation.
- Scale Automation Through Agentic Workflows: Design, build, and deploy agents on the Kairos platform, leveraging the enterprise ecosystem to ensure consistency, reusability, rapid iteration, and maximum speed-to-value.
- Build necessary data plumbing: Integrate against imperfect upstream systems (SQL Server, BigQuery/EDW, GCP services, Looker, vendor APIs), managing schema drift, partial coverage, and inconsistent definitions while ensuring proper data lineage and governance.
- Prove it works before it is trusted: Build evaluation harnesses alongside features (shadow-mode testing, precision/recall measurement, override-feedback loops, human-in-the-loop approval paths).
- Demo, ship, and iterate weekly: Ship high-value features to staging weekly and demo to stakeholders on a standing cadence while navigating operational and policy complexity.
We'll keep each as
- .
Now Requirements:
Requirements
then - each.
List:
- Bachelor’s degree or four or more years of work experience.
- Six or more years of relevant experience required, demonstrated through one or a combination of work and/or military experience, or specialized training.
- 5+ years of experience building and shipping production software end-to-end, demonstrating clear personal ownership, identifying specific users impacted, and delivering measurable business outcomes.
- Experience shipping Large Language Model (LLM) applications to end users, applying hands-on expertise in prompt and context engineering, retrieval mechanisms, agent design, and system evaluation.
- Demonstrated experience integrating data across complex, imperfect systems, leveraging strong SQL skills, practical data agility, and deep comfort navigating cloud environments (GCP) and business intelligence tools (Looker or equivalent).
Now Qualifications (preferred):
Qualifications
then - each from "Even better if you have one or more of the following:" list.
Items:
- 10+ years of relevant engineering experience building, shipping, and scaling enterprise software.
- A Bachelor's degree in Information Technology, Information Systems, Computer Science, or a related technical field.
- Direct experience working alongside business operators in a highly embedded capacity, such as a forward-deployed engineer, solutions engineer, or founding engineer.
- Exposure to regulated-data domains, including telecom CPNI, eDiscovery, financial compliance, or healthcare.
- Proven experience operationalizing and scaling AI systems in production environments, with a strong emphasis on system feedback loops and continuous improvement.
- Experience working with physical security, Operational Technology (OT), or critical-infrastructure technology.
- A verifiable track record operating in high-consequence environments, securely handling highly sensitive information (such as law enforcement data or executive location information).
- Exceptional "spec literacy", including the proven experience reading business processes, asking targeted probing questions to surface hidden edge cases, and drafting precise technical specifications.
- A proven track record of operating with high autonomy, consistently clearing your own blockers without a program-management layer and escalating issues by proposing solutions rather than just reporting status updates.
Now Benefits:
Benefits
then - each benefit.
From posting:
- medical, dental, vision, short and long term disability, basic life insurance, supplemental life insurance, AD&D insurance, identity theft protection, pet insurance and group home & auto insurance.
- matched 401(k) savings plan
- up to 8 company paid holidays per year
- up to 6 personal days per year
- paid parental leave
- adoption assistance
- tuition assistance
- other incentives (award-winning total rewards package)
- Depending on the role, employees have the opportunity to receive compensation in the form of premium pay such as overtime, shift differential, holiday pay, allowances, etc.
- Newly hired employees receive up to 15 days of vacation per year, which grows with additional service.
- For part-timers, your coverage will vary as you may be eligible for some of these benefits depending on your individual circumstances.
We could combine some.
We'll list each as separate
- maybe grouping similar.
Now Pay:
Pay
then with salary range and other pay details.
Content:
- The annual salary range for the location(s) listed on this job requisition based on a full-time schedule is: $120,500.00 - $231,000.00.
- This is an incentive based position with the potential to earn more.
- For part-time roles, your compensation will be adjusted to reflect your hours.
We'll include that.
Now Schedule:
Schedule
then with hybrid role and weekly hours.
Content:
- In this hybrid
- for any list of duties/requirements/benefits, and
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to drop EEO statement, benefits boilerplate? Actually benefits section we need to keep substantive benefits info. The posting includes benefits description: medical, dental, vision, etc. Also 401(k), holidays, personal days, parental leave, adoption assistance, tuition assistance, etc. Also mention premium pay etc. Also salary range. We need to include Pay section if posting actually states them. It does: salary range $120,500 - $231,000. Also mentions incentive based position, potential to earn more, etc. So we should include Pay section. Schedule: posting says "Scheduled Weekly Hours 40" and hybrid role: defined work location includes working from home and minimum of three days per week in the office. So we have schedule info. Thus we will have sections: About the role (intro), Responsibilities (What You’ll Be Doing...), Requirements (maybe combine qualifications and skills?), Qualifications (maybe separate?), Skills (maybe separate?), Benefits, Pay, Schedule. But we need to avoid thin sections. Could combine Requirements and Qualifications into one? However the instruction says use headings for those specific names if content exists. We have content for Requirements (the "What We’re Looking For..." includes bullet-like list of requirements). Also there are "Even better if you have one or more of the following:" which could be qualifications or preferred qualifications. Could treat as Qualifications. Skills: maybe we can extract skills from responsibilities: building applications, AI toolchain, agentic workflows, data plumbing, evaluation harnesses, demo/ship/iterate. Could be a Skills section. But we need to avoid duplication. Let's decide: - About the role: intro paragraph(s) about Verizon, V Team, mission. - Responsibilities: the "What You’ll Be Doing..." bullet list (though it's paragraph with bold headings). We'll convert each responsibility into
- .
- Requirements: the mandatory requirements list: Bachelor’s degree or four or more years of work experience; Six or more years of relevant experience; 5+ years of experience building and shipping production software end-to-end; Experience shipping LLM applications; Demonstrated experience integrating data across complex imperfect systems, strong SQL, cloud GCP, Looker.
- Qualifications: the "Even better if you have one or more of the following:" list (preferred qualifications). Could be separate.
- Skills: maybe we can combine responsibilities and qualifications? But we need to follow instruction: Use headings for those specific names if content exists. We have content for Skills? Could extract skills like: software development, LLM applications, prompt engineering, agent design, SQL, GCP, Looker, data integration, evaluation harnesses, CI/CD, stakeholder demo, etc. Could be a Skills section.
But we might be duplicating content. However instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we put skills in a separate section, we need to ensure we don't lose any info. Could we instead put skills within Responsibilities or Requirements? The instruction says use
- for any list of duties/requirements/benefits. So we can treat responsibilities as list, requirements as list, benefits as list. Skills could be a list as well.
But we need to avoid thin sections. If we create Skills section with just a few items, maybe it's okay. However we could also merge Skills into Responsibilities (since responsibilities already list skills). But the instruction says use headings for those specific names if content exists. It doesn't forbid merging content across headings; but we need to include a section only when posting has real, specific content for it. If we put skills content under Responsibilities, we still have a Skills section? No, we would not have Skills section then. That's okay if we don't have specific content for Skills beyond what's already covered. But we might lose explicit skill enumeration. However the responsibilities already enumerate skills implicitly. The instruction says preserve ALL substantive information; we can preserve them under Responsibilities. So we may not need a separate Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule.
Now we need to format.
We need to strip boilerplate: EEO statement, "Equal Employment Opportunity Verizon is an equal opportunity employer..." etc. Also "Where you’ll be working" we need to keep schedule info but not the heading? We'll put schedule info under Schedule section.
We need to keep "Scheduled Weekly Hours 40" and hybrid details.
We need to keep benefits description.
We need to keep salary range.
We need to keep "Depending on the role, employees have the opportunity to receive compensation in the form of premium pay such as overtime, shift differential, holiday pay, allowances, etc." and "Newly hired employees receive up to 15 days of vacation per year..." etc. That's benefits.
We need to avoid duplication: The benefits paragraph includes many items; we can list them as
- .
Now craft HTML.
We'll start with
About the role
then...
containing the intro paragraphs (maybe two paragraphs). We'll combine them. Intro paragraphs: "When you join Verizon You want more out of a career. A place to share your ideas freely — even if they’re daring or different. Where the true you can learn, grow, and thrive. At Verizon, we power and empower how people live, work and play by connecting them to what brings them joy. We do what we love — driving innovation, creativity, and impact in the world. Our V Team is a community of people who anticipate, lead, and believe that listening is where learning begins. In crisis and in celebration, we come together — lifting our communities and building trust in how we show up, everywhere & always. Want in? Join the #VTeamLife." We can keep as one. Now Responsibilities:
Responsibilities
then- each responsibility. Responsibilities list from posting: - Build applications from specifications: Take completed business requirements specifications and deliver working software against them as a hands-on individual contributor (write code, configure platforms, wire data, and demo results). - Build and operate the AI toolchain: Own internal tooling making the spec-to-build loop repeatable, including structured intake requirements-interview agents, reusable prompt/context/evaluation scaffolding, and build telemetry instrumentation. - Scale Automation Through Agentic Workflows: Design, build, and deploy agents on the Kairos platform, leveraging the enterprise ecosystem to ensure consistency, reusability, rapid iteration, and maximum speed-to-value. - Build necessary data plumbing: Integrate against imperfect upstream systems (SQL Server, BigQuery/EDW, GCP services, Looker, vendor APIs), managing schema drift, partial coverage, and inconsistent definitions while ensuring proper data lineage and governance. - Prove it works before it is trusted: Build evaluation harnesses alongside features (shadow-mode testing, precision/recall measurement, override-feedback loops, human-in-the-loop approval paths). - Demo, ship, and iterate weekly: Ship high-value features to staging weekly and demo to stakeholders on a standing cadence while navigating operational and policy complexity. We'll keep each as
- .
Now Requirements:
Requirements
then- each.
List:
- Bachelor’s degree or four or more years of work experience.
- Six or more years of relevant experience required, demonstrated through one or a combination of work and/or military experience, or specialized training.
- 5+ years of experience building and shipping production software end-to-end, demonstrating clear personal ownership, identifying specific users impacted, and delivering measurable business outcomes.
- Experience shipping Large Language Model (LLM) applications to end users, applying hands-on expertise in prompt and context engineering, retrieval mechanisms, agent design, and system evaluation.
- Demonstrated experience integrating data across complex, imperfect systems, leveraging strong SQL skills, practical data agility, and deep comfort navigating cloud environments (GCP) and business intelligence tools (Looker or equivalent).
Now Qualifications (preferred):
Qualifications
then- each from "Even better if you have one or more of the following:" list.
Items:
- 10+ years of relevant engineering experience building, shipping, and scaling enterprise software.
- A Bachelor's degree in Information Technology, Information Systems, Computer Science, or a related technical field.
- Direct experience working alongside business operators in a highly embedded capacity, such as a forward-deployed engineer, solutions engineer, or founding engineer.
- Exposure to regulated-data domains, including telecom CPNI, eDiscovery, financial compliance, or healthcare.
- Proven experience operationalizing and scaling AI systems in production environments, with a strong emphasis on system feedback loops and continuous improvement.
- Experience working with physical security, Operational Technology (OT), or critical-infrastructure technology.
- A verifiable track record operating in high-consequence environments, securely handling highly sensitive information (such as law enforcement data or executive location information).
- Exceptional "spec literacy", including the proven experience reading business processes, asking targeted probing questions to surface hidden edge cases, and drafting precise technical specifications.
- A proven track record of operating with high autonomy, consistently clearing your own blockers without a program-management layer and escalating issues by proposing solutions rather than just reporting status updates.
Now Benefits:
Benefits
then- each benefit. From posting: - medical, dental, vision, short and long term disability, basic life insurance, supplemental life insurance, AD&D insurance, identity theft protection, pet insurance and group home & auto insurance. - matched 401(k) savings plan - up to 8 company paid holidays per year - up to 6 personal days per year - paid parental leave - adoption assistance - tuition assistance - other incentives (award-winning total rewards package) - Depending on the role, employees have the opportunity to receive compensation in the form of premium pay such as overtime, shift differential, holiday pay, allowances, etc. - Newly hired employees receive up to 15 days of vacation per year, which grows with additional service. - For part-timers, your coverage will vary as you may be eligible for some of these benefits depending on your individual circumstances. We could combine some. We'll list each as separate
- maybe grouping similar.
Now Pay:
Pay
thenwith salary range and other pay details. Content: - The annual salary range for the location(s) listed on this job requisition based on a full-time schedule is: $120,500.00 - $231,000.00. - This is an incentive based position with the potential to earn more. - For part-time roles, your compensation will be adjusted to reflect your hours. We'll include that. Now Schedule:
Schedule
thenwith hybrid role and weekly hours. Content: - In this hybrid
- each from "Even better if you have one or more of the following:" list.
Items:
- 10+ years of relevant engineering experience building, shipping, and scaling enterprise software.
- A Bachelor's degree in Information Technology, Information Systems, Computer Science, or a related technical field.
- Direct experience working alongside business operators in a highly embedded capacity, such as a forward-deployed engineer, solutions engineer, or founding engineer.
- Exposure to regulated-data domains, including telecom CPNI, eDiscovery, financial compliance, or healthcare.
- Proven experience operationalizing and scaling AI systems in production environments, with a strong emphasis on system feedback loops and continuous improvement.
- Experience working with physical security, Operational Technology (OT), or critical-infrastructure technology.
- A verifiable track record operating in high-consequence environments, securely handling highly sensitive information (such as law enforcement data or executive location information).
- Exceptional "spec literacy", including the proven experience reading business processes, asking targeted probing questions to surface hidden edge cases, and drafting precise technical specifications.
- A proven track record of operating with high autonomy, consistently clearing your own blockers without a program-management layer and escalating issues by proposing solutions rather than just reporting status updates.
Now Benefits:
- each.
List:
- Bachelor’s degree or four or more years of work experience.
- Six or more years of relevant experience required, demonstrated through one or a combination of work and/or military experience, or specialized training.
- 5+ years of experience building and shipping production software end-to-end, demonstrating clear personal ownership, identifying specific users impacted, and delivering measurable business outcomes.
- Experience shipping Large Language Model (LLM) applications to end users, applying hands-on expertise in prompt and context engineering, retrieval mechanisms, agent design, and system evaluation.
- Demonstrated experience integrating data across complex, imperfect systems, leveraging strong SQL skills, practical data agility, and deep comfort navigating cloud environments (GCP) and business intelligence tools (Looker or equivalent).
Now Qualifications (preferred):
- .
Now craft HTML.
We'll start with
- for any list of duties/requirements/benefits. So we can treat responsibilities as list, requirements as list, benefits as list. Skills could be a list as well.
But we need to avoid thin sections. If we create Skills section with just a few items, maybe it's okay. However we could also merge Skills into Responsibilities (since responsibilities already list skills). But the instruction says use headings for those specific names if content exists. It doesn't forbid merging content across headings; but we need to include a section only when posting has real, specific content for it. If we put skills content under Responsibilities, we still have a Skills section? No, we would not have Skills section then. That's okay if we don't have specific content for Skills beyond what's already covered. But we might lose explicit skill enumeration. However the responsibilities already enumerate skills implicitly. The instruction says preserve ALL substantive information; we can preserve them under Responsibilities. So we may not need a separate Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule.
Now we need to format.
We need to strip boilerplate: EEO statement, "Equal Employment Opportunity Verizon is an equal opportunity employer..." etc. Also "Where you’ll be working" we need to keep schedule info but not the heading? We'll put schedule info under Schedule section.
We need to keep "Scheduled Weekly Hours 40" and hybrid details.
We need to keep benefits description.
We need to keep salary range.
We need to keep "Depending on the role, employees have the opportunity to receive compensation in the form of premium pay such as overtime, shift differential, holiday pay, allowances, etc." and "Newly hired employees receive up to 15 days of vacation per year..." etc. That's benefits.
We need to avoid duplication: The benefits paragraph includes many items; we can list them as