Intermediate Software Developer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits unless stated. Benefits are stated, so include Benefits section. Pay not mentioned, so omit. Schedule not mentioned, omit.
We need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (list of duties). Qualifications (list). Skills? Could combine with qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Skills if there is content. There's mention of "You Can Expect To" which is responsibilities. Also "We are especially interested in candidates with experience in the following areas: Cloud Services, such as AWS, Azure, and GCP DevOps pipelines Salesforce GIS". That could be Skills or Requirements. We'll treat as Skills.
We need to extract all substantive info.
Let's parse the posting:
First paragraph: "Our Development team focuses on implementation, using a test-driven design and development approach. Developers work in pairs on a variety of projects, rotating pair partners and/or projects on a weekly basis. At Menlo, it's not as important to be an expert in any particular language as to be willing and able to learn new languages when needed. Sharing your technical and project knowledge with other team members is a natural part of the process, preventing any one person from becoming a tower of knowledge."
Then "About The Role Job Title: Intermediate Software Developer Location: In-person at our office in Ann Arbor, MI Employment Type: Full-Time Level: Intermediate". We should not repeat job title as heading. We can include location, employment type, level maybe in a short paragraph under About the role.
Then description: "We're looking for an Intermediate Software Developer who can thrive in a collaborative, paired environment. You have enough experience to contribute confidently to technical discussions, solve problems with limited guidance, and help others grow, but you're still excited to learn new technologies, approaches, and domains. At Menlo, developers work in pairs on a variety of projects, rotating pair partners and/or projects on a weekly basis. We believe that sharing technical and project knowledge is essential to building strong teams and preventing any one person from becoming a tower of knowledge. This role requires a unique balance of technical skills, interpersonal and consultative skills, and service minded thinking. You'll play a central role in communicating technical recommendations to clients, engaging in feedback with your peers, and producing high-quality, full-stack software solutions. We are especially interested in candidates with experience in the following areas: Cloud Services, such as AWS, Azure, and GCPDevOps pipelinesSalesforceGIS"
Then "You Can Expect To spend your time working in a paired context with other team members and, at times, directly with clientsTo spend the majority of your time coding and executing related development tasks, including TDDTo rotate across a diverse portfolio of projects, domains, and technologiesTo estimate, design, develop, test, and deploy high-quality softwareTo participate actively in technical discussions and contribute to project-level decisionsTo work collaboratively and cross-functionally across the team to drive project successTo participate in and lead project activities such as daily stand-ups, show-and-tell sessions, planning games, and technical discussionsTo help newer developers grow by sharing technical knowledge and providing constructive feedbackTo proactively identify and communicate technical risks, blockers, and opportunities to the project teamTo contribute to system design and implementation decisions while knowing when to seek input from more experienced team membersTo work with clients and teammates to understand problems and translate them into effective technical solutionsTo continually improve your technical skills while helping others learn what you know"
Then "Qualifications 3+ years of professional software development experienceExperience working on software projects from requirements through implementation and deliveryStrong understanding of software development fundamentals, testing, and maintainable codeComfortable working in unfamiliar codebases and learning new technologiesAble to contribute to or lead technical design and architecture discussionsStrong communication and collaboration skillsEnjoys sharing knowledge and helping less-experienced teammates develop their skillsFamiliarity with and/or interest in Agile development, XP, TDD, and pair programmingA “make mistakes sooner” attitudeAsks questions often and is willing to challenge assumptions respectfullyCommitment to work full time, in-person in Ann Arbor, MI (This is not a hybrid or remote work assignment)Our interview process requires candidates to fulfill a trial period on-site in Ann Arbor, MI"
Then "Nice To Have Prior experience with pair programming and/or TDDExperience working in a consulting or client-services environmentExperience mentoring or informally leading other developersExperience working across multiple programming languages or technology stacksExperience working directly with clients or non-technical stakeholdersExperience with cloud services, DevOps, Salesforce or GIS"
Then "Benefits Health insurance (73% - 87% subsidized with HSA options and generous employer contribution)Life & disability insurancePaid time off (20 days annually)10 paid holidays per year401(k) - with employer contribution (Traditional and Roth)Parking is reimbursedMenlo values work/life balance, and uses a unique paired staffing approach as a mechanism for employee development, cross-training, and delivering high-quality work products."
We need to output HTML fragment with sections.
We'll create:
About the role
... (prose)
Then maybe Responsibilities
with - list from "You Can Expect To". Need to split each bullet.
Then
Skills
with list from "We are especially interested in candidates with experience in the following areas:" plus maybe also from Nice To Have? Could treat Nice To Have as additional skills but maybe separate? Could include under Skills as well. But we might also have a Qualifications
list.
Qualifications list from "Qualifications" section.
Nice To Have could be included under Skills or maybe as a separate section? The instruction says we can include Skills section. We could put Nice To Have under Skills as additional.
We must not create sections with filler. Ensure we have substantive content.
Let's extract each.
About the role prose: combine first paragraph and the description about role before responsibilities.
First paragraph: "Our Development team focuses on implementation, using a test-driven design and development approach. Developers work in pairs on a variety of projects, rotating pair partners and/or projects on a weekly basis. At Menlo, it's not as important to be an expert in any particular language as to be willing and able to learn new languages when needed. Sharing your technical and project knowledge with other team members is a natural part of the process, preventing any one person from becoming a tower of knowledge."
Then after About The Role heading we have description: "We're looking for an Intermediate Software Developer who can thrive in a collaborative, paired environment. You have enough experience to contribute confidently to technical discussions, solve problems with limited guidance, and help others grow, but you're still excited to learn new technologies, approaches, and domains. At Menlo, developers work in pairs on a variety of projects, rotating pair partners and/or projects on a weekly basis. We believe that sharing technical and project knowledge is essential to building strong teams and preventing any one person from becoming a tower of knowledge. This role requires a unique balance of technical skills, interpersonal and consultative skills, and service minded thinking. You'll play a central role in communicating technical recommendations to clients, engaging in feedback with your peers, and producing high-quality, full-stack software solutions. We are especially interested in candidates with experience in the following areas: Cloud Services, such as AWS, Azure, and GCPDevOps pipelinesSalesforceGIS"
We could combine into one paragraph.
Responsibilities list: from "You Can Expect To". The text appears concatenated without spaces. Need to split by "To". Let's extract each bullet:
- spend your time working in a paired context with other team members and, at times, directly with clients
- spend the majority of your time coding and executing related development tasks, including TDD
- rotate across a diverse portfolio of projects, domains, and technologies
- estimate, design, develop, test, and deploy high-quality software
- participate actively in technical discussions and contribute to project-level decisions
- work collaboratively and cross-functionally across the team to drive project success
- participate in and lead project activities such as daily stand-ups, show-and-tell sessions, planning games, and technical discussions
- help newer developers grow by sharing technical knowledge and providing constructive feedback
- proactively identify and communicate technical risks, blockers, and opportunities to the project team
- contribute to system design and implementation decisions while knowing when to seek input from more experienced team members
- work with clients and teammates to understand problems and translate them into effective technical solutions
- continually improve your technical skills while helping others learn what you know
We'll make - for each.
Skills list: from "We are especially interested in candidates with experience in the following areas: Cloud Services, such as AWS, Azure, and GCPDevOps pipelinesSalesforceGIS". This seems messy: "Cloud Services, such as AWS, Azure, and GCPDevOps pipelinesSalesforceGIS". Probably intended: Cloud Services (AWS, Azure, GCP), DevOps pipelines, Salesforce, GIS. We'll split: Cloud Services (AWS, Azure, GCP), DevOps pipelines, Salesforce, GIS.
Also Nice To Have list: Prior experience with pair programming and/or TDD, Experience working in a consulting or client-services environment, Experience mentoring or informally leading other developers, Experience working across multiple programming languages or technology stacks, Experience working directly with clients or non-technical stakeholders, Experience with cloud services, DevOps, Salesforce or GIS.
We could combine these into Skills section, maybe separate into Required Skills and Nice-to-have? But we only have Skills heading. Could list all under Skills, maybe separate with note? But we must not invent headings like "Nice to have". Could incorporate into Skills as bullet points, maybe label? But we should preserve info; we can include them as bullets without labeling.
Thus Skills bullets:
- Cloud Services (AWS, Azure, GCP)
- DevOps pipelines
- Salesforce
- GIS
- Pair programming and/or TDD (nice to have)
- Consulting or client-services experience (nice to have)
- Mentoring or informally leading other developers (nice to have)
- Working across multiple programming languages or technology stacks (nice to have)
- Working directly with clients or non-technical stakeholders (nice to have)
- Experience with cloud services, DevOps, Salesforce or GIS (nice to have) (some overlap)
But we might be duplicating. Better to separate: Required Skills from the "especially interested" list; Nice To Have as separate bullets under Skills but maybe we can add a note? However we cannot add extra headings. Could just list all under Skills, but some are nice-to-have. It's okay.
Qualifications list: from "Qualifications". Need to split each item.
Text: "3+ years of professional software development experienceExperience working on software projects from requirements through implementation and deliveryStrong understanding of software development fundamentals, testing, and maintainable codeComfortable working in unfamiliar codebases and learning new technologiesAble to contribute to or lead technical design and architecture discussionsStrong communication and collaboration skillsEnjoys sharing knowledge and helping less-experienced teammates develop their skillsFamiliarity with and/or interest in Agile development, XP, TDD, and pair programmingA “make mistakes sooner” attitudeAsks questions often and is willing to challenge assumptions respectfullyCommitment to work full time, in-person in Ann Arbor, MI (This is not a hybrid or remote work assignment)Our interview process requires candidates to fulfill a trial period on-site in Ann Arbor, MI"
We need to split by capital letters? Let's manually list:
- 3+ years of professional software development experience
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits unless stated. Benefits are stated, so include Benefits section. Pay not mentioned, so omit. Schedule not mentioned, omit. We need sections: About the role (maybe from "About The Role" paragraph). Responsibilities (list of duties). Qualifications (list). Skills? Could combine with qualifications? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Skills if there is content. There's mention of "You Can Expect To" which is responsibilities. Also "We are especially interested in candidates with experience in the following areas: Cloud Services, such as AWS, Azure, and GCP DevOps pipelines Salesforce GIS". That could be Skills or Requirements. We'll treat as Skills. We need to extract all substantive info. Let's parse the posting: First paragraph: "Our Development team focuses on implementation, using a test-driven design and development approach. Developers work in pairs on a variety of projects, rotating pair partners and/or projects on a weekly basis. At Menlo, it's not as important to be an expert in any particular language as to be willing and able to learn new languages when needed. Sharing your technical and project knowledge with other team members is a natural part of the process, preventing any one person from becoming a tower of knowledge." Then "About The Role Job Title: Intermediate Software Developer Location: In-person at our office in Ann Arbor, MI Employment Type: Full-Time Level: Intermediate". We should not repeat job title as heading. We can include location, employment type, level maybe in a short paragraph under About the role. Then description: "We're looking for an Intermediate Software Developer who can thrive in a collaborative, paired environment. You have enough experience to contribute confidently to technical discussions, solve problems with limited guidance, and help others grow, but you're still excited to learn new technologies, approaches, and domains. At Menlo, developers work in pairs on a variety of projects, rotating pair partners and/or projects on a weekly basis. We believe that sharing technical and project knowledge is essential to building strong teams and preventing any one person from becoming a tower of knowledge. This role requires a unique balance of technical skills, interpersonal and consultative skills, and service minded thinking. You'll play a central role in communicating technical recommendations to clients, engaging in feedback with your peers, and producing high-quality, full-stack software solutions. We are especially interested in candidates with experience in the following areas: Cloud Services, such as AWS, Azure, and GCPDevOps pipelinesSalesforceGIS" Then "You Can Expect To spend your time working in a paired context with other team members and, at times, directly with clientsTo spend the majority of your time coding and executing related development tasks, including TDDTo rotate across a diverse portfolio of projects, domains, and technologiesTo estimate, design, develop, test, and deploy high-quality softwareTo participate actively in technical discussions and contribute to project-level decisionsTo work collaboratively and cross-functionally across the team to drive project successTo participate in and lead project activities such as daily stand-ups, show-and-tell sessions, planning games, and technical discussionsTo help newer developers grow by sharing technical knowledge and providing constructive feedbackTo proactively identify and communicate technical risks, blockers, and opportunities to the project teamTo contribute to system design and implementation decisions while knowing when to seek input from more experienced team membersTo work with clients and teammates to understand problems and translate them into effective technical solutionsTo continually improve your technical skills while helping others learn what you know" Then "Qualifications 3+ years of professional software development experienceExperience working on software projects from requirements through implementation and deliveryStrong understanding of software development fundamentals, testing, and maintainable codeComfortable working in unfamiliar codebases and learning new technologiesAble to contribute to or lead technical design and architecture discussionsStrong communication and collaboration skillsEnjoys sharing knowledge and helping less-experienced teammates develop their skillsFamiliarity with and/or interest in Agile development, XP, TDD, and pair programmingA “make mistakes sooner” attitudeAsks questions often and is willing to challenge assumptions respectfullyCommitment to work full time, in-person in Ann Arbor, MI (This is not a hybrid or remote work assignment)Our interview process requires candidates to fulfill a trial period on-site in Ann Arbor, MI" Then "Nice To Have Prior experience with pair programming and/or TDDExperience working in a consulting or client-services environmentExperience mentoring or informally leading other developersExperience working across multiple programming languages or technology stacksExperience working directly with clients or non-technical stakeholdersExperience with cloud services, DevOps, Salesforce or GIS" Then "Benefits Health insurance (73% - 87% subsidized with HSA options and generous employer contribution)Life & disability insurancePaid time off (20 days annually)10 paid holidays per year401(k) - with employer contribution (Traditional and Roth)Parking is reimbursedMenlo values work/life balance, and uses a unique paired staffing approach as a mechanism for employee development, cross-training, and delivering high-quality work products." We need to output HTML fragment with sections. We'll create:
About the role
... (prose)
Then maybeResponsibilities
with- list from "You Can Expect To". Need to split each bullet.
Then
Skills
with list from "We are especially interested in candidates with experience in the following areas:" plus maybe also from Nice To Have? Could treat Nice To Have as additional skills but maybe separate? Could include under Skills as well. But we might also have aQualifications
list. Qualifications list from "Qualifications" section. Nice To Have could be included under Skills or maybe as a separate section? The instruction says we can include Skills section. We could put Nice To Have under Skills as additional. We must not create sections with filler. Ensure we have substantive content. Let's extract each. About the role prose: combine first paragraph and the description about role before responsibilities. First paragraph: "Our Development team focuses on implementation, using a test-driven design and development approach. Developers work in pairs on a variety of projects, rotating pair partners and/or projects on a weekly basis. At Menlo, it's not as important to be an expert in any particular language as to be willing and able to learn new languages when needed. Sharing your technical and project knowledge with other team members is a natural part of the process, preventing any one person from becoming a tower of knowledge." Then after About The Role heading we have description: "We're looking for an Intermediate Software Developer who can thrive in a collaborative, paired environment. You have enough experience to contribute confidently to technical discussions, solve problems with limited guidance, and help others grow, but you're still excited to learn new technologies, approaches, and domains. At Menlo, developers work in pairs on a variety of projects, rotating pair partners and/or projects on a weekly basis. We believe that sharing technical and project knowledge is essential to building strong teams and preventing any one person from becoming a tower of knowledge. This role requires a unique balance of technical skills, interpersonal and consultative skills, and service minded thinking. You'll play a central role in communicating technical recommendations to clients, engaging in feedback with your peers, and producing high-quality, full-stack software solutions. We are especially interested in candidates with experience in the following areas: Cloud Services, such as AWS, Azure, and GCPDevOps pipelinesSalesforceGIS" We could combine into one paragraph. Responsibilities list: from "You Can Expect To". The text appears concatenated without spaces. Need to split by "To". Let's extract each bullet: - spend your time working in a paired context with other team members and, at times, directly with clients - spend the majority of your time coding and executing related development tasks, including TDD - rotate across a diverse portfolio of projects, domains, and technologies - estimate, design, develop, test, and deploy high-quality software - participate actively in technical discussions and contribute to project-level decisions - work collaboratively and cross-functionally across the team to drive project success - participate in and lead project activities such as daily stand-ups, show-and-tell sessions, planning games, and technical discussions - help newer developers grow by sharing technical knowledge and providing constructive feedback - proactively identify and communicate technical risks, blockers, and opportunities to the project team - contribute to system design and implementation decisions while knowing when to seek input from more experienced team members - work with clients and teammates to understand problems and translate them into effective technical solutions - continually improve your technical skills while helping others learn what you know We'll make- for each. Skills list: from "We are especially interested in candidates with experience in the following areas: Cloud Services, such as AWS, Azure, and GCPDevOps pipelinesSalesforceGIS". This seems messy: "Cloud Services, such as AWS, Azure, and GCPDevOps pipelinesSalesforceGIS". Probably intended: Cloud Services (AWS, Azure, GCP), DevOps pipelines, Salesforce, GIS. We'll split: Cloud Services (AWS, Azure, GCP), DevOps pipelines, Salesforce, GIS. Also Nice To Have list: Prior experience with pair programming and/or TDD, Experience working in a consulting or client-services environment, Experience mentoring or informally leading other developers, Experience working across multiple programming languages or technology stacks, Experience working directly with clients or non-technical stakeholders, Experience with cloud services, DevOps, Salesforce or GIS. We could combine these into Skills section, maybe separate into Required Skills and Nice-to-have? But we only have Skills heading. Could list all under Skills, maybe separate with note? But we must not invent headings like "Nice to have". Could incorporate into Skills as bullet points, maybe label? But we should preserve info; we can include them as bullets without labeling. Thus Skills bullets: - Cloud Services (AWS, Azure, GCP) - DevOps pipelines - Salesforce - GIS - Pair programming and/or TDD (nice to have) - Consulting or client-services experience (nice to have) - Mentoring or informally leading other developers (nice to have) - Working across multiple programming languages or technology stacks (nice to have) - Working directly with clients or non-technical stakeholders (nice to have) - Experience with cloud services, DevOps, Salesforce or GIS (nice to have) (some overlap) But we might be duplicating. Better to separate: Required Skills from the "especially interested" list; Nice To Have as separate bullets under Skills but maybe we can add a note? However we cannot add extra headings. Could just list all under Skills, but some are nice-to-have. It's okay. Qualifications list: from "Qualifications". Need to split each item. Text: "3+ years of professional software development experienceExperience working on software projects from requirements through implementation and deliveryStrong understanding of software development fundamentals, testing, and maintainable codeComfortable working in unfamiliar codebases and learning new technologiesAble to contribute to or lead technical design and architecture discussionsStrong communication and collaboration skillsEnjoys sharing knowledge and helping less-experienced teammates develop their skillsFamiliarity with and/or interest in Agile development, XP, TDD, and pair programmingA “make mistakes sooner” attitudeAsks questions often and is willing to challenge assumptions respectfullyCommitment to work full time, in-person in Ann Arbor, MI (This is not a hybrid or remote work assignment)Our interview process requires candidates to fulfill a trial period on-site in Ann Arbor, MI" We need to split by capital letters? Let's manually list: - 3+ years of professional software development experience