Senior Software Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Schedule section with hybrid on-site location. Benefits: posting mentions nothing about benefits besides generic EEO etc. No specific benefits listed, so we should not create Benefits section. Skills: maybe we can include a Skills section if there is specific skill list. The posting includes many skill-like statements: proficiency in programming languages, version control, etc. Could be under Qualifications or Skills. The instruction: prefer a few substantive sections over many thin ones. We have Qualifications (required and desired). Could combine required and desired under Qualifications. Responsibilities is clearly present. Could also have an About the role (job summary). The job summary paragraph at start: "Curious Minds...". That's about the company and role. Could be About the role. We'll include About the role section with that prose.
We must not repeat job title as heading. So no heading for Senior Software Engineer.
We must not include Job ID/requisition numbers.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraphs, the privacy policy link, etc.
We need to preserve all substantive information: job summary, responsibilities list, qualifications (required and desired), pay range, schedule (hybrid on-site location). Also maybe mention "Global Banking Solutions engineering group", "Wilmington, NC". Also mention "AI tools" etc.
We need to format responsibilities as - . Qualifications as maybe
- for required and desired? Could separate Required and Desired as subheadings? But we should avoid many thin sections. Could just list all qualifications in a single list, maybe with notes. But we need to preserve required vs desired distinction. Could keep as two subheadings
? Not allowed? Only h3 for section headings. Could use inside - to denote Required/Desired. That's okay.
Similarly, we could have Skills section if we want to separate skill list, but we can incorporate into Qualifications.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
Curious Minds. Bold Ideas. Extraordinary Impact. We're transforming financial services through bold innovation and relentless execution. You bring the ideas and drive. We'll build what's next — together. nCino is looking for a Senior Software Engineer to join our Global Banking Solutions engineering group, where you will help build the products financial institutions rely on to serve their consumer and business customers. You will lead development work across the full software lifecycle, contribute to architectural decisions, uphold code quality standards, and mentor teammates along the way. This is a role for an engineer who wants real ownership over technical direction and the opportunity to influence both what gets built and how the broader engineering organization builds it. The ideal candidate brings strong full stack experience, a track record of delivering in complex environments, and the communication skills to work effectively across engineering, product, and design. You think carefully about scalability and maintainability, thrive in cross functional delivery, and are energized by work that has a direct impact on how financial institutions serve their communities across nCino's global banking product lines. This role is a hybrid on-site position at our Global Headquarters in Wilmington, NC.
But we already have schedule info; maybe we should move location to Schedule section. However the About the role includes that sentence; we could keep it there but then Schedule section would be duplicate. Better to separate: About the role includes company mission and role description, but not location. Then Schedule section includes hybrid on-site at Wilmington, NC. Let's adjust.
Thus About the role paragraph excludes the location sentence. We'll keep location in Schedule.
Now Responsibilities: list all bullet points from "Provide input on architectural decisions..." through "Leads the management of software dependencies..." etc. Need to capture all responsibilities. Let's extract them:
- Provide input on architectural decisions and guide team members around best practices.
- Incorporate the automated tests into applicable tickets and mentors other members of the team on automation strategies.
- Lead brainstorming sessions and propose innovative ideas and solutions.
- Identify opportunities & lead proof-of-concepts to demonstrate key functionality or validate critical technical aspects.
- Begin to consider scalability, maintainability, and best practices as the high-level design of the solution takes shape.
- Identify potential risks and provide mitigation strategies.
- Help choose technologies and tools used for the project.
- Be a technologist with an understanding of a range of languages, frameworks, and tools.
- Consistently design code that is aligned with the overall service architecture.
- Keep abreast of developments in the field and introduce new approaches and technologies.
- Understand the data model and design of the product.
- Facilitate communication and collaboration inside and outside their team.
- Heavily involved in Automated Testing and improves the best practices and metrics.
- Understand adoption and release barriers to entry for the product and technology.
- Support PM and team in developing a strategic launch and release plan with cross functional teams.
- Promote cross-team collaboration focused on taking end to end solutions to market and supporting Go-live activities.
- Help prioritize the system hygiene backlog, with a focus on improving both the product and the developer experience.
- Mitigate the introduction of additional hygiene through code reviews, ensuring team members adhere to coding standards.
- Leads the management of software dependencies, staying informed about industry updates and trends to ensure version compatibility
- Exhibit technical mastery and proficiency in multiple programming languages, frameworks, and tools relevant to our technology stack.
- Uphold the highest standards of code quality and follows industry best practices.
- Plays a pivotal role in driving technical excellence, innovation, and delivering high-quality software solutions.
- Defines personal continuous learning plans and provide customized plans for junior members of the team.
- Demonstrate expertise in independently completing complex tickets, mentor team members, and facilitating effective communication and collaboration.
- Proficient understanding of ETL processes, data modeling and data integration techniques
- Leverage AI tools and techniques to enhance software development activities, including code generation, testing, debugging, and optimization.
- Apply AI insights to identify patterns, automate repetitive tasks, and improve overall development efficiency and product quality.
- Evaluate and integrate AI/ML capabilities where appropriate to strengthen product functionality and user experience.
- Maintain awareness of emerging AI trends and best practices to inform continuous learning and innovation.
That's many. We'll put them in - .
Qualifications: Required and Desired.
Required:
- Bachelor’s Degree in Computer Science or a related field with 5+ years of experience/proficiency or a combination of education and experience
- Proficiency in at least one major programming language
- Experience with version control systems (e.g., Git) and collaboration tools
- Demonstrated commitment to quality and continuous improvement
- Strong problem-solving skills and the ability to work independently as well as in teams.
- Excellent communication skills with the ability to explain technical concepts to non-technical stakeholders.
Desired:
- Demonstrated experience with client-side JavaScript frameworks like Angular, React, Knockout, etc.
- Demonstrated knowledge of Agile/SCRUM and TDD development methodologies.
- Experience mentoring junior engineers and collaborating with cross-functional teams.
- Experience with AWS tools and technologies.
We could format as
- with Required: then sublist? But we can't nest headings inside li? Could do
- Required:
... but that's messy. Better to just list all qualifications, marking required vs desired in text. Could do two separate with headings but not allowed. Could use
Required:
... then Desired:
... That's okay as we are not using h3 for those.
Pay section: Pay
The Base Salary Range For This Job Is $107,900 - $183,400 USD
Schedule section: Schedule
This role is a hybrid on-site position at our Global Headquarters in Wilmington, NC.
We should not include Benefits section because no specific benefits.
Now ensure we didn't include boilerplate: removed EEO, privacy policy, etc.
Check for duplicated lines: we have not repeated.
Now output HTML fragment.
Let's craft final HTML:
About the role
Curious Minds. Bold Ideas. Extraordinary Impact. We're transforming financial services through bold innovation and relentless execution. You bring the ideas and drive. We'll build what's next — together. nCino is looking for a Senior Software Engineer to join our Global Banking Solutions engineering group, where you will help build the products financial institutions rely on to serve their consumer and business customers. You will lead development work across the full software lifecycle, contribute to architectural decisions, uphold code quality standards, and mentor teammates along the way. This is a role for an engineer who wants real ownership over technical direction and the opportunity to influence both what gets built and how the broader engineering organization builds it. The ideal candidate brings strong full stack experience, a track record of delivering in complex environments, and the communication skills to work effectively across engineering, product, and design. You think carefully about scalability and maintainability, thrive in cross functional delivery, and are energized by work that has a direct impact on how financial institutions serve their communities across nCino's global banking product lines.
Responsibilities
- Provide input on architectural decisions and guide team members around best practices.
- Incorporate the automated tests into applicable tickets and mentor other members of the team on automation strategies.
- Lead brainstorming sessions and propose innovative ideas and solutions.
- Identify opportunities & lead proof-of-concepts to demonstrate key functionality or validate critical technical aspects.
- Begin to consider scalability, maintainability, and best practices as the high-level design of the solution takes shape.
- Identify potential risks and provide mitigation strategies.
- Help choose technologies and tools used for the project.
- Be a technologist with an understanding of a range of languages, frameworks, and tools.
- Consistently design code that is aligned with the overall service architecture.
- Keep abreast of developments in the field and introduce new approaches and technologies.
- Understand the data model and design of the product.
- Facilitate communication and collaboration inside and outside their team.
- Heavily involved in Automated Testing and improves the best practices and metrics.
- Understand adoption and release barriers to entry for the product and technology.
- Support PM and team in developing a strategic launch and release plan with cross functional teams.
- Promote cross-team collaboration focused on taking end to end solutions to market and supporting Go-live activities.
- Help prioritize the system hygiene backlog, with a focus on improving both the product and the developer experience.
- Mitigate the introduction of additional hygiene through code reviews, ensuring team members adhere
- for required and desired? Could separate Required and Desired as subheadings? But we should avoid many thin sections. Could just list all qualifications in a single list, maybe with notes. But we need to preserve required vs desired distinction. Could keep as two subheadings
? Not allowed? Only h3 for section headings. Could use inside
- to denote Required/Desired. That's okay. Similarly, we could have Skills section if we want to separate skill list, but we can incorporate into Qualifications. We need to output only HTML fragment, no /, no markdown fences. Let's craft:
About the role
Curious Minds. Bold Ideas. Extraordinary Impact. We're transforming financial services through bold innovation and relentless execution. You bring the ideas and drive. We'll build what's next — together. nCino is looking for a Senior Software Engineer to join our Global Banking Solutions engineering group, where you will help build the products financial institutions rely on to serve their consumer and business customers. You will lead development work across the full software lifecycle, contribute to architectural decisions, uphold code quality standards, and mentor teammates along the way. This is a role for an engineer who wants real ownership over technical direction and the opportunity to influence both what gets built and how the broader engineering organization builds it. The ideal candidate brings strong full stack experience, a track record of delivering in complex environments, and the communication skills to work effectively across engineering, product, and design. You think carefully about scalability and maintainability, thrive in cross functional delivery, and are energized by work that has a direct impact on how financial institutions serve their communities across nCino's global banking product lines. This role is a hybrid on-site position at our Global Headquarters in Wilmington, NC.
But we already have schedule info; maybe we should move location to Schedule section. However the About the role includes that sentence; we could keep it there but then Schedule section would be duplicate. Better to separate: About the role includes company mission and role description, but not location. Then Schedule section includes hybrid on-site at Wilmington, NC. Let's adjust. Thus About the role paragraph excludes the location sentence. We'll keep location in Schedule. Now Responsibilities: list all bullet points from "Provide input on architectural decisions..." through "Leads the management of software dependencies..." etc. Need to capture all responsibilities. Let's extract them: - Provide input on architectural decisions and guide team members around best practices. - Incorporate the automated tests into applicable tickets and mentors other members of the team on automation strategies. - Lead brainstorming sessions and propose innovative ideas and solutions. - Identify opportunities & lead proof-of-concepts to demonstrate key functionality or validate critical technical aspects. - Begin to consider scalability, maintainability, and best practices as the high-level design of the solution takes shape. - Identify potential risks and provide mitigation strategies. - Help choose technologies and tools used for the project. - Be a technologist with an understanding of a range of languages, frameworks, and tools. - Consistently design code that is aligned with the overall service architecture. - Keep abreast of developments in the field and introduce new approaches and technologies. - Understand the data model and design of the product. - Facilitate communication and collaboration inside and outside their team. - Heavily involved in Automated Testing and improves the best practices and metrics. - Understand adoption and release barriers to entry for the product and technology. - Support PM and team in developing a strategic launch and release plan with cross functional teams. - Promote cross-team collaboration focused on taking end to end solutions to market and supporting Go-live activities. - Help prioritize the system hygiene backlog, with a focus on improving both the product and the developer experience. - Mitigate the introduction of additional hygiene through code reviews, ensuring team members adhere to coding standards. - Leads the management of software dependencies, staying informed about industry updates and trends to ensure version compatibility - Exhibit technical mastery and proficiency in multiple programming languages, frameworks, and tools relevant to our technology stack. - Uphold the highest standards of code quality and follows industry best practices. - Plays a pivotal role in driving technical excellence, innovation, and delivering high-quality software solutions. - Defines personal continuous learning plans and provide customized plans for junior members of the team. - Demonstrate expertise in independently completing complex tickets, mentor team members, and facilitating effective communication and collaboration. - Proficient understanding of ETL processes, data modeling and data integration techniques - Leverage AI tools and techniques to enhance software development activities, including code generation, testing, debugging, and optimization. - Apply AI insights to identify patterns, automate repetitive tasks, and improve overall development efficiency and product quality. - Evaluate and integrate AI/ML capabilities where appropriate to strengthen product functionality and user experience. - Maintain awareness of emerging AI trends and best practices to inform continuous learning and innovation. That's many. We'll put them in- .
Qualifications: Required and Desired.
Required:
- Bachelor’s Degree in Computer Science or a related field with 5+ years of experience/proficiency or a combination of education and experience
- Proficiency in at least one major programming language
- Experience with version control systems (e.g., Git) and collaboration tools
- Demonstrated commitment to quality and continuous improvement
- Strong problem-solving skills and the ability to work independently as well as in teams.
- Excellent communication skills with the ability to explain technical concepts to non-technical stakeholders.
Desired:
- Demonstrated experience with client-side JavaScript frameworks like Angular, React, Knockout, etc.
- Demonstrated knowledge of Agile/SCRUM and TDD development methodologies.
- Experience mentoring junior engineers and collaborating with cross-functional teams.
- Experience with AWS tools and technologies.
We could format as
- with Required: then sublist? But we can't nest headings inside li? Could do
- Required:
- Provide input on architectural decisions and guide team members around best practices.
- Incorporate the automated tests into applicable tickets and mentor other members of the team on automation strategies.
- Lead brainstorming sessions and propose innovative ideas and solutions.
- Identify opportunities & lead proof-of-concepts to demonstrate key functionality or validate critical technical aspects.
- Begin to consider scalability, maintainability, and best practices as the high-level design of the solution takes shape.
- Identify potential risks and provide mitigation strategies.
- Help choose technologies and tools used for the project.
- Be a technologist with an understanding of a range of languages, frameworks, and tools.
- Consistently design code that is aligned with the overall service architecture.
- Keep abreast of developments in the field and introduce new approaches and technologies.
- Understand the data model and design of the product.
- Facilitate communication and collaboration inside and outside their team.
- Heavily involved in Automated Testing and improves the best practices and metrics.
- Understand adoption and release barriers to entry for the product and technology.
- Support PM and team in developing a strategic launch and release plan with cross functional teams.
- Promote cross-team collaboration focused on taking end to end solutions to market and supporting Go-live activities.
- Help prioritize the system hygiene backlog, with a focus on improving both the product and the developer experience.
- Mitigate the introduction of additional hygiene through code reviews, ensuring team members adhere
- ... but that's messy. Better to just list all qualifications, marking required vs desired in text. Could do two separate
- with headings
but not allowed. Could use
Required:
- ... then
Desired:
- ... That's okay as we are not using h3 for those.
Pay section:
Pay
The Base Salary Range For This Job Is $107,900 - $183,400 USD
Schedule section:Schedule
This role is a hybrid on-site position at our Global Headquarters in Wilmington, NC.
We should not include Benefits section because no specific benefits. Now ensure we didn't include boilerplate: removed EEO, privacy policy, etc. Check for duplicated lines: we have not repeated. Now output HTML fragment. Let's craft final HTML:About the role
Curious Minds. Bold Ideas. Extraordinary Impact. We're transforming financial services through bold innovation and relentless execution. You bring the ideas and drive. We'll build what's next — together. nCino is looking for a Senior Software Engineer to join our Global Banking Solutions engineering group, where you will help build the products financial institutions rely on to serve their consumer and business customers. You will lead development work across the full software lifecycle, contribute to architectural decisions, uphold code quality standards, and mentor teammates along the way. This is a role for an engineer who wants real ownership over technical direction and the opportunity to influence both what gets built and how the broader engineering organization builds it. The ideal candidate brings strong full stack experience, a track record of delivering in complex environments, and the communication skills to work effectively across engineering, product, and design. You think carefully about scalability and maintainability, thrive in cross functional delivery, and are energized by work that has a direct impact on how financial institutions serve their communities across nCino's global banking product lines.
Responsibilities
- with Required: then sublist? But we can't nest headings inside li? Could do
- to denote Required/Desired. That's okay. Similarly, we could have Skills section if we want to separate skill list, but we can incorporate into Qualifications. We need to output only HTML fragment, no /, no markdown fences. Let's craft: