Sr. Software Engineer

We need to output HTML fragment with headings for sections that have real content. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. The posting includes: Company Details (maybe not needed as heading? Not in list). Responsibilities (yes). Qualifications (yes). Preferred Qualifications (maybe part of Qualifications or separate? Could be under Qualifications). Additional Requirements (Location and Travel, Sponsorship Details). There's no explicit Benefits, Pay, Schedule. So we should not create those sections. We need to include About the role? The posting doesn't have a separate "About the role" paragraph; the responsibilities start after "We are seeking a highly motivated...". Could treat that as About the role? But we should only include sections when posting has real specific content. There is a paragraph describing role before responsibilities: "We are seeking a highly motivated and technically skilled Sr Software Engineer to join our Sales & Marketing team. In this role, you will design, develop, support, and modernize software solutions that enable critical Sales and Marketing business processes." That could be considered About the role. But the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role if there is content. Then Responsibilities, Qualifications (maybe combine Qualifications and Preferred Qualifications?), Additional Requirements (Location and Travel, Sponsorship Details). Could also include Requirements? The posting has "Qualifications" and "Preferred Qualifications". No separate "Requirements". So we can have Qualifications section containing both required and preferred? Might be better to split: Qualifications (required) and Preferred Qualifications (optional). But the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one Qualifications section with subpoints? But we need to use

• for any list of duties/requirements/benefits. So we can list responsibilities as ul, qualifications as ul (maybe separate required and preferred as separate ul? Could be two ul under same heading). That's okay. We must not repeat job title as heading. No Job ID. We must remove boilerplate: Company Details maybe not needed as heading; but we could include a short paragraph about company? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep company details? It's substantive. But we don't have a heading for company details; we could just put it as a

  before sections. However, the instruction says use

  for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but we should follow that pattern. Probably we can include a

  with company details. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes "The Company is an equal employment opportunity employer." That's EEO boilerplate; remove. Also "Sponsorship Details Sponsorship not Offered for this Role" - that's not boilerplate; it's specific info about sponsorship, keep. We need to preserve all substantive info: company URL, description, responsibilities, qualifications, preferred qualifications, location, sponsorship. Let's extract content: Company Details: - Company URL: https://www.berkleytechnologyservices.com/ - Berkley Technology Services (BTS) is the dynamic technology solution for W. R. Berkley Corporation, a Fortune 500 Commercial Lines Insurance Company. - With key locations in Urbandale, IA and Wilmington, DE, BTS provides innovative and customer-focused IT solutions to the majority of WRBC’s 60+ operating units across the globe. - BTS’s wide reach ensures that ideas and opinions are considered at every level of the organization to guarantee we find the best solutions possible. - Driven by a commitment to collaboration, BTS acts as consultants to our customers and Operating Units by providing comprehensive solutions that not only address the challenge at hand, but proactively plan for the “What’s Next” in our industry and beyond. - With a culture centered on innovation and entrepreneurial spirit, BTS stands as a community of technology leaders with eyes toward the future -- leaders who truly care about growing not only their team members, but themselves, and take pride in their employees who shine. - BTS offers endless ways to get involved and have the chance to grow your career into a wide range of roles you'd never known existed. - Come join us as we push forward into the future of industry leading technological solutions. - Berkley Technology Services: Right Team, Right Technology, Simple and Secure. That's a lot; we can keep as a paragraph or multiple paragraphs. Responsibilities: bullet list of duties. We need to extract responsibilities list from the text. Let's parse: After "Responsibilities" heading, we have: "We are seeking a highly motivated and technically skilled Sr Software Engineer to join our Sales & Marketing team. In this role, you will design, develop, support, and modernize software solutions that enable critical Sales and Marketing business processes. A primary focus of this position will be reviewing, refactoring, and enhancing existing C#/.NET code to improve maintainability, performance, scalability, and long-term supportability while reducing technical debt. This role will also be responsible for developing and supporting ETL processes, large-scale data movement initiatives, system integrations, and automation workflows utilizing SQL Server, Jenkins, and modern source control and CI/CD practices. The engineer will play a key role in application modernization efforts, including repository cleanup and migration to GitHub, while helping establish development standards and best practices across the team. Success in this position requires strong technical expertise , a problem-solving mindset, and close collaboration with Product Owners, business stakeholders, and development team to deliver reliable, scalable, and business-focused solutions. The individual will also participate in application support and on-call rotations to help ensure the stability and availability of critical Sales & Marketing systems." Then a list of bullet-like sentences (some start with verbs). Let's capture each as a list item: - Review, refactor, and modernize existing C#/.NET code to improve code quality, maintainability, performance, and supportability. - Design, develop, test, and maintain software applications supporting Sales & Marketing initiatives. - Define, document, and enforce development standards, design patterns, and coding best practices. - Design and implement enterprise system integrations and interfaces. - Design, develop, and support ETL processes for large-scale data movement between enterprise applications, CRM platforms, databases, and cloud services. - Design, develop, and maintain SQL Server databases. - Ensure data integrity, performance optimization, and secure data access. - Collaborate closely with Product Owners, Business Analysts, stakeholders, and end users to translate business requirements into technical solutions. - Design, execute, and analyze A/B tests or similar experiments to optimize features and user experience. - Perform and coordinate quality assurance (QA) testing and job regression testing prior to and after production deployments. - Support sprint planning, backlog refinement, and Agile ceremonies to ensure timely and high-quality delivery. - Support sprint execution by validating scope, estimating effort, and ensuring deliverables are production-ready. - Deliver high-quality customer support with a strong sense of urgency, ownership, and accountability. - Provide Tier 1 after-hours/on-call support by participating in application support and incident triage rotation. - Quickly adapt to new technologies, tools, and platforms. - Analyze and solve complex technical and business problems. - Work effectively within a distributed and virtual team environment. - Support continuous improvement initiatives across Sales & Marketing technology platforms. - Utilize Azure, Azure Service Bus, and Data Factory for cloud solutions. - Utilize Microsoft Copilot or other AI-assisted development tools. - Complete code reviews and pull request (PR) approvals for onshore and offshore resources on all changes prior to deployment. - Ensure PRs adhere to established coding standards, security practices, documentation expectations, and deployment guidelines. - Provide clear, constructive feedback to improve code quality, maintainability, and long-term supportability. That's responsibilities. Qualifications (required): "Strong technical background in C#/.NET, SQL Server, Python, and ETL/Data Integration, with experience developing applications, managing data solutions, and building data integration workflows. 3+ years of software development experience 3+ years of experience with cloud computing platforms, particularly Microsoft Azure. Experience participating in or leading code reviews and PR approval processes. Ability to work independently and deliver results with minimal supervision in a fast-paced environment. Excellent written and verbal communication skills with the ability to engage both technical and non-technical stakeholders. Strong customer service mindset, sense of urgency, and accountability. Excellent analytical, troubleshooting, and problem-solving skills. Proven ability to collaborate effectively within a distributed or offshore/onshore team model. Experience using Atlassian tools (Jira, Confluence, Bitbucket). Strong engineering judgment and attention to detail Ownership of code quality and production stability Bachelor’s degree with emphasis in related field or equivalent experience. Ability to influence development standards across teams Clear, respectful communication across global teams Customer-first orientation with a solution mindset Continuous improvement and modernization focus" We can list each as

  . Preferred Qualifications: "Experience with Jenkins for job scheduling, application deployment, automation, and data processing workflows. Experience with GitHub, GitHub Actions, and modern CI/CD practices. Experience with Microsoft Power Platform (Power Automate, Power Apps, Power Pages, Dataverse). Experience with Microsoft Dynamics 365 CRM or Salesforce Development. Experience designing and supporting enterprise CRM and marketing system interfaces. Experience working with Microsoft Copilot or other AI-assisted development tools. Experience working in Agile/Scrum development environments. Knowledge of or experience in the Property & Casualty (P&C) Insurance industry. Working knowledge of Entity Framework." Behavioral Core Competencies: list maybe but not required heading; could be part of Qualifications? Might be considered Qualifications as well. But we can include under Qualifications as additional bullet points. Additional Requirements: "Location and Travel: Urbandale, IA. Sponsorship Details Sponsorship not Offered for this Role" We can make a section maybe "Location and Sponsorship" or keep as

  . Since there is no specific heading for location in the list, but we could treat as "Additional Requirements". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should follow that pattern. However, "Additional Requirements" is not in the list but could be considered similar to Requirements. Might be okay to use

  for Additional Requirements. But we have no separate Requirements section; we have Qualifications. Could treat location and sponsorship as part of Qualifications? Probably better to make a separate section "Location and Sponsorship" but not in list. The instruction says prefer a few substantive sections over many thin ones. So maybe we can include location and sponsorship as a

  under Qualifications or after Qualifications. But we need to preserve all substantive info. We'll include a

  for location and sponsorship. Now, we need to avoid creating sections with filler like "commensurate with experience". Not present. We must not include Pay, Schedule, Benefits sections because not stated. We must not repeat job title as heading. We must not include markdown fences. Output only HTML fragment. Let's structure:

  Company details paragraph(s). Could be multiple

  but we can combine into one

  with line breaks? Better to keep as multiple

  for readability but still valid. We'll do:

  https://www.berkleytechnologyservices.com/

  Berkley Technology Services (BTS) is the dynamic technology solution for W. R. Berkley Corporation, a Fortune 500 Commercial Lines Insurance Company. With key locations in Urbandale, IA and Wilmington, DE, BTS provides innovative and customer-focused IT solutions to the majority of