Software Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, etc. We need to parse the job posting.
Let's extract relevant content.
The posting starts:
Overview Job Description Develops software consistent with Cisco's Design Thinking Principles, focusing on simplification and user experience, using secure coding practices and following software development best practices. Collaborates with design and product management teams to create the right solutions for customers. Creates technical design documentation for the team and contributes to user documentation for end users. Debugs and addresses software issues during development and in production systems to support customers. Brings new ideas for product innovation and helps improve software development processes.
What You'll Do Communicates status and issues to the teamShares experience and knowledge to support the teamPerforms routine assignments that require basic knowledge and exposure to fundamental theories, principles, and conceptsCollaborates effectively with own teamContributes to small projects and works with others on small features primarily focused on coding and testingDevelops an understanding of the software development lifecycle and various agile engineering practices (e.g., requirements analysis, design, coding, unit testing, acceptance testing), and assists on projects where these methods are appliedAnalyzes user requirements and works with others to understand impact on technical design featuresWrites correct code with assistanceSupports test code refining and rewriting as part of testing and debuggingAssists with tests for scaling for reliability and velocityApplies secure coding principles and follows secure coding guidelinesSupports more senior team members in troubleshooting and debugging issuesProficient in at least one large area of the codebase (multiple services in a pillar) with a high-level understanding of other components Minimum Qualifications Bachelors + 0 years of previous experience Requires basic knowledge of theories, principles and concepts within a technical discipline; has exposure to current technologies through coursework or internship. Preferred Qualifications Varies based on the team and business needs. Preferred qualifications are desired education, experience, and skills that are in addition to minimum qualifications. If an employer asks you to pay any kind of fee, please notify us immediately. Talentd does not charge any fee from applicants and we do not allow other companies to do so. Key Skills AgileTestingDebuggingcodingSecure CodingUX Related Tags Software EngineerFresherProduct and Engineering Browse More Jobs Jobs in Bangalore Education Requirements Bachelor's degree Eligible Batch Years 2026, 2025, 2024 Cisco Cisco Systems, Inc. is a globally renowned leader in networking technology, cybersecurity, and communications solutions. Founded in 1984, Cisco has played a pivotal role in shaping the internet and enterprise networking landscapes. With its mission to power an inclusive future for all, the company develops and sells a wide range of products and services, including routers, switches, cloud-based collaboration tools, and security solutions. Cisco serves enterprises, governments, and service providers worldwide, enabling digital transformation and secure connectivity. Headquartered in San Jose, California, USA, Cisco employs over 80,000 people globally and maintains a strong market position as one of the most influential multinational technology corporations. The company is consistently recognized for innovation, sustainability initiatives, and corporate social responsibility. Recent achievements include advancements in AI-driven networking, expansion of its cybersecurity portfolio, and strategic acquisitions to bolster its cloud and hybrid work offerings. Company Details Industry Technology Connect With Us Website cisco.com Related Jobs Technical Graduate Trainee NTT Data Location not specified ₹3.2L - ₹3.2L LPA 3 days ago Fresher ... etc.
We need to remove boilerplate: navigation, related jobs, etc. Keep only substantive info: Overview/Job Description, What You'll Do (responsibilities), Minimum Qualifications, Preferred Qualifications (though it says varies, but we might still include if there is content? It says "Varies based on the team and business needs." That's vague; we should not include a section if it's just placeholder. The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So Preferred Qualifications is vague "Varies based on the team and business needs." That's placeholder. So we should omit Preferred Qualifications section.
Key Skills: "AgileTestingDebuggingcodingSecure CodingUX". That's a list of skills but not separated. Could treat as list items? It's a string without spaces. Might be better to split? But we must preserve content exactly? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." We could keep as a paragraph or list. Since it's a list of skills, we could make - Agile
- Testing
... but that would be inventing separation. Better to keep as a paragraph: AgileTestingDebuggingcodingSecure CodingUX
. However that seems odd. Maybe we can keep as is.
Education Requirements: Bachelor's degree. Eligible Batch Years 2026, 2025, 2024. That's specific. Could be under Requirements or Qualifications? There's already Minimum Qualifications. Education Requirements could be part of Qualifications. But we have a heading for Qualifications. We could combine Minimum Qualifications and Education Requirements under Qualifications? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have Overview Job Description (could be About the role). What You'll Do (Responsibilities). Minimum Qualifications (Qualifications). Key Skills (Skills). Education Requirements (maybe also Qualifications). Could combine Education Requirements into Qualifications section.
We should not repeat job title as heading.
We need to output only HTML fragment.
Let's decide sections:
- About the role: from Overview Job Description paragraph.
- Responsibilities: from What You'll Do list (multiple sentences). Could break into - items each sentence? The content is a run-on sentence without punctuation. We could split by capital letters? Better to keep as
preserving the text. But instruction: Use
- for any list of duties/requirements/benefits. The "What You'll Do" is a list of duties, though not formatted as list. We could treat each clause as a list item. However we risk altering meaning. But we can infer each duty separated by capital letters? The text: "Communicates status and issues to the teamShares experience and knowledge to support the teamPerforms routine assignments that require basic knowledge and exposure to fundamental theories, principles, and conceptsCollaborates effectively with own teamContributes to small projects and works with others on small features primarily focused on coding and testingDevelops an understanding of the software development lifecycle and various agile engineering practices (e.g., requirements analysis, design, coding, unit testing, acceptance testing), and assists on projects where these methods are appliedAnalyzes user requirements and works with others to understand impact on technical design featuresWrites correct code with assistanceSupports test code refining and rewriting as part of testing and debuggingAssists with tests for scaling for reliability and velocityApplies secure coding principles and follows secure coding guidelinesSupports more senior team members in troubleshooting and debugging issuesProficient in at least one large area of the codebase (multiple services in a pillar) with a high-level understanding of other components"
We could split at each capital letter that starts a new verb? That's messy. Safer to keep as a paragraph
. The instruction says use
- for any list of duties/requirements/benefits. If we don't have clear list, we can use
. It's not a list; it's a paragraph of duties. So we can use
.
- Qualifications: combine Minimum Qualifications and Education Requirements. Minimum Qualifications: "Bachelors + 0 years of previous experience Requires basic knowledge of theories, principles and concepts within a technical discipline; has exposure to current technologies through coursework or internship." Education Requirements: "Bachelor's degree Eligible Batch Years 2026, 2025, 2024". We'll combine into a
or maybe
- for each? It's not a list but we could make list: Bachelor's degree, Eligible Batch Years 2026, 2025, 2024, Bachelors + 0 years of previous experience, Requires basic knowledge... etc. But that may be inventing structure. Safer to keep as paragraph.
- Skills: Key Skills: "AgileTestingDebuggingcodingSecure CodingUX". We'll put as
.
We should not include Benefits, Pay, Schedule as none present.
We must remove boilerplate like "If an employer asks you to pay any kind of fee..." etc. Also remove "Talentd does not charge any fee..." etc. Also remove "Related Tags", "Browse More Jobs", etc.
Also remove company description? The instruction: "Preserve ALL substantive information". The company description about Cisco is substantive? It's about the company, not the role. Might be considered boilerplate? It's not navigation/legal/EEO but it's generic company info. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly listed to remove, but it's not specific to the job. However it's substantive info about the employer. Might be okay to keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive about Cisco. But it's not directly about the job. However many job postings include company overview; it's likely considered part of the posting. The instruction didn't say to remove company overview. So we could keep it under a section like "About the company" but we don't have a heading for that. We could include it under About the role? Might be odd. Better to include as a separate section? Not in allowed headings. Could we add a
About Cisco
? Not in allowed list. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings. So we should not add other headings. So we should not include company description as a separate heading. Could we fold it into About the role? That would be mixing role description with company info, but maybe acceptable. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can fold minor metadata into a short
. Company description is not minor metadata; it's more substantial. But we have no heading for it. Perhaps we should drop it because it's not role-specific and we lack appropriate heading. The instruction: "Prefer a few substantive sections over many thin ones." So we could include company description as a paragraph under About the role? Might be okay.
But the instruction also says "Preserve ALL substantive information". If we drop company description, we lose substantive info. So better to include it somewhere. Since we don't have a heading for company, we could add a
after the sections, not under a heading. That's allowed: we can have plain
elements not under headings? The instruction says use
for section headings, - for any list,
for prose. It doesn't forbid having
outside headings. So we can output sections with headings and then a final <
AgileTestingDebuggingcodingSecure CodingUX
. However that seems odd. Maybe we can keep as is. Education Requirements: Bachelor's degree. Eligible Batch Years 2026, 2025, 2024. That's specific. Could be under Requirements or Qualifications? There's already Minimum Qualifications. Education Requirements could be part of Qualifications. But we have a heading for Qualifications. We could combine Minimum Qualifications and Education Requirements under Qualifications? The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content. We have Overview Job Description (could be About the role). What You'll Do (Responsibilities). Minimum Qualifications (Qualifications). Key Skills (Skills). Education Requirements (maybe also Qualifications). Could combine Education Requirements into Qualifications section. We should not repeat job title as heading. We need to output only HTML fragment. Let's decide sections: - About the role: from Overview Job Description paragraph. - Responsibilities: from What You'll Do list (multiple sentences). Could break into- items each sentence? The content is a run-on sentence without punctuation. We could split by capital letters? Better to keep as
preserving the text. But instruction: Use
- for any list of duties/requirements/benefits. The "What You'll Do" is a list of duties, though not formatted as list. We could treat each clause as a list item. However we risk altering meaning. But we can infer each duty separated by capital letters? The text: "Communicates status and issues to the teamShares experience and knowledge to support the teamPerforms routine assignments that require basic knowledge and exposure to fundamental theories, principles, and conceptsCollaborates effectively with own teamContributes to small projects and works with others on small features primarily focused on coding and testingDevelops an understanding of the software development lifecycle and various agile engineering practices (e.g., requirements analysis, design, coding, unit testing, acceptance testing), and assists on projects where these methods are appliedAnalyzes user requirements and works with others to understand impact on technical design featuresWrites correct code with assistanceSupports test code refining and rewriting as part of testing and debuggingAssists with tests for scaling for reliability and velocityApplies secure coding principles and follows secure coding guidelinesSupports more senior team members in troubleshooting and debugging issuesProficient in at least one large area of the codebase (multiple services in a pillar) with a high-level understanding of other components"
We could split at each capital letter that starts a new verb? That's messy. Safer to keep as a paragraph
. The instruction says use
- for any list of duties/requirements/benefits. If we don't have clear list, we can use
. It's not a list; it's a paragraph of duties. So we can use
. - Qualifications: combine Minimum Qualifications and Education Requirements. Minimum Qualifications: "Bachelors + 0 years of previous experience Requires basic knowledge of theories, principles and concepts within a technical discipline; has exposure to current technologies through coursework or internship." Education Requirements: "Bachelor's degree Eligible Batch Years 2026, 2025, 2024". We'll combine into a
or maybe
- for each? It's not a list but we could make list: Bachelor's degree, Eligible Batch Years 2026, 2025, 2024, Bachelors + 0 years of previous experience, Requires basic knowledge... etc. But that may be inventing structure. Safer to keep as paragraph.
- Skills: Key Skills: "AgileTestingDebuggingcodingSecure CodingUX". We'll put as
. We should not include Benefits, Pay, Schedule as none present. We must remove boilerplate like "If an employer asks you to pay any kind of fee..." etc. Also remove "Talentd does not charge any fee..." etc. Also remove "Related Tags", "Browse More Jobs", etc. Also remove company description? The instruction: "Preserve ALL substantive information". The company description about Cisco is substantive? It's about the company, not the role. Might be considered boilerplate? It's not navigation/legal/EEO but it's generic company info. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not explicitly listed to remove, but it's not specific to the job. However it's substantive info about the employer. Might be okay to keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is substantive about Cisco. But it's not directly about the job. However many job postings include company overview; it's likely considered part of the posting. The instruction didn't say to remove company overview. So we could keep it under a section like "About the company" but we don't have a heading for that. We could include it under About the role? Might be odd. Better to include as a separate section? Not in allowed headings. Could we add a
About Cisco
? Not in allowed list. The instruction says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we should stick to those? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings. So we should not add other headings. So we should not include company description as a separate heading. Could we fold it into About the role? That would be mixing role description with company info, but maybe acceptable. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can fold minor metadata into a short
. Company description is not minor metadata; it's more substantial. But we have no heading for it. Perhaps we should drop it because it's not role-specific and we lack appropriate heading. The instruction: "Prefer a few substantive sections over many thin ones." So we could include company description as a paragraph under About the role? Might be okay. But the instruction also says "Preserve ALL substantive information". If we drop company description, we lose substantive info. So better to include it somewhere. Since we don't have a heading for company, we could add a
after the sections, not under a heading. That's allowed: we can have plain
elements not under headings? The instruction says use
for section headings,
- for any list,
for prose. It doesn't forbid having
outside headings. So we can output sections with headings and then a final <
- for any list,
- for each? It's not a list but we could make list: Bachelor's degree, Eligible Batch Years 2026, 2025, 2024, Bachelors + 0 years of previous experience, Requires basic knowledge... etc. But that may be inventing structure. Safer to keep as paragraph.
- Skills: Key Skills: "AgileTestingDebuggingcodingSecure CodingUX". We'll put as
- for any list of duties/requirements/benefits. If we don't have clear list, we can use
- for any list of duties/requirements/benefits. The "What You'll Do" is a list of duties, though not formatted as list. We could treat each clause as a list item. However we risk altering meaning. But we can infer each duty separated by capital letters? The text: "Communicates status and issues to the teamShares experience and knowledge to support the teamPerforms routine assignments that require basic knowledge and exposure to fundamental theories, principles, and conceptsCollaborates effectively with own teamContributes to small projects and works with others on small features primarily focused on coding and testingDevelops an understanding of the software development lifecycle and various agile engineering practices (e.g., requirements analysis, design, coding, unit testing, acceptance testing), and assists on projects where these methods are appliedAnalyzes user requirements and works with others to understand impact on technical design featuresWrites correct code with assistanceSupports test code refining and rewriting as part of testing and debuggingAssists with tests for scaling for reliability and velocityApplies secure coding principles and follows secure coding guidelinesSupports more senior team members in troubleshooting and debugging issuesProficient in at least one large area of the codebase (multiple services in a pillar) with a high-level understanding of other components"
We could split at each capital letter that starts a new verb? That's messy. Safer to keep as a paragraph