Jobs · Wisconsin

Software Developer

Baird · Madison, WI · 3 wk ago
HybridFull-time
We need to output HTML fragment with sections only if real specific content. The posting content. We have sections: About the role (the first paragraph). Responsibilities? The posting includes "The Impact You'll Make" with subsections: Systems Analysis, Design & Development; Solution Delivery; Relationship & Stakeholder Management; Team Collaboration & Development; Engineering Excellence & Innovation. Those could be considered responsibilities. We can group them under a Responsibilities section with bullet points summarizing each? But we must not invent or summarize away detail; we must preserve all substantive information. However we can use
  • for any list of duties/requirements/benefits. The posting includes many paragraphs describing duties. We could break each bullet as a list item preserving the text. That would preserve detail. We need to avoid filler like "commensurate with experience". That appears in Compensation And Benefits section: "Compensation and bonus are commensurate with experience, performance and/or firm profitability". That's filler? It's not specific numbers, but it's actual statement. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting does have a Compensation And Benefits section with that sentence. It's somewhat vague but it's actual content. Should we include a Benefits section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state a Compensation And Benefits section with that sentence. So we could include a Benefits section with that sentence as a

    . However the rule also says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience"...). That suggests we should not create a Pay/Schedule/Benefits section if the content is just filler like that. The sentence is indeed filler. So we should omit that section. Similarly, there is no explicit Pay or Schedule details besides hybrid working arrangement (that's schedule). The posting mentions hybrid working arrangement: at least 3 days per week in office, remaining remote. That's schedule info. So we could include a Schedule section with that detail. It's specific: hybrid, 3 days office, rest remote. That's not filler. So include Schedule. Benefits: The posting mentions "You’ll have the opportunity to advance your career while enjoying our comprehensive benefits designed for your life, career and future." That's vague but still a statement about benefits. It's not specific like health insurance etc. Might be considered filler? It's not specific details. The rule says avoid filler/placeholder text like "commensurate with experience", "not specified", etc. "comprehensive benefits designed for your life, career and future" is vague but not exactly placeholder. However it's still generic. Safer to omit Benefits section because no concrete benefits listed. Thus sections: About the role (already present as heading? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we will have

    About the role

    then paragraph(s). Then

    Responsibilities

    with
    • items covering the duties from The Impact You'll Make sections. Then

      Requirements

      (or Qualifications?) The posting has "What You’ll Bring To Baird" which includes minimum experience, skills, education. That's qualifications. Could treat as Requirements or Qualifications. We'll use

      Requirements

      with list items. We also have Schedule section: hybrid working arrangement. We must not include Job ID etc. We must remove boilerplate like note to external recruiters, etc. We must preserve all substantive information; not invent or summarize away detail. So we need to keep the exact sentences? We can break them into list items but must keep the content. It's okay to rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should not summarize; we should keep the detail as is. Using list items with the sentences is okay; we are not summarizing, just extracting. Thus for Responsibilities, we can take each bullet from the sections: Systems Analysis..., Solution Delivery..., Relationship..., Team Collaboration..., Engineering Excellence... Each of those sections have multiple sentences. We could keep each sentence as separate list item, but that may be a lot. Better to keep each paragraph as list item preserving the sentences. That still preserves detail. Let's extract: Systems Analysis, Design & Development: - Design, develop, refactor and enhance readable, testable, extensible and maintainable software for Baird Online web and mobile experiences with limited guidance - Apply software development principles and best practices, including SOLID, DRY and single-responsibility principles, while building scalable front-end solutions using React, Next.js and related web technologies - Diagnose and resolve application issues across the client portal experience, create thorough development tests and write unit and component tests while identifying opportunities to improve functionality, reliability, performance, accessibility and maintainability - Use API, SQL and database concepts to support digital client solutions, translate tactical business needs into technical approaches and implement changes through Baird’s release management process Solution Delivery: - Estimate small to medium-sized user stories for Baird Online enhancements and break work into clear, manageable tasks that make progress visible - Prioritize the highest-value work for PWM clients and internal stakeholders, using available information to collaborate on timely decisions - Identify and help manage risks, issues, dependencies and milestones for a client-facing digital platform while applying craftsmanship practices such as pairing, code reviews and unit testing Relationship & Stakeholder Management: - Build collaborative relationships across IT and work effectively with PWM business partners, product owners, business analysts, project managers, quality analysts and developers - Navigate organizational dynamics with guidance to support informed decisions, client-focused outcomes and successful delivery across business and technology teams - Manage stakeholder expectations for medium-sized initiatives and tailor messages and communication styles to technical, product, business and leadership audiences Team Collaboration & Development: - Contribute to refinement sessions by helping create clear, well-written and consistently sized user stories for Baird Online features, applying Baird Delivery Fundamentals and a strong understanding of client-facing digital experiences - Help implement lifecycle management best practices, support continuous team improvement and mentor development interns or less experienced team members as opportunities arise Engineering Excellence & Innovation: - Actively contribute to continuous improvement activities that strengthen software development practices for modern web applications and client-facing digital platforms - Support the growth of Baird’s development capabilities through internal and external initiatives, including Deming, cross-team projects, modern front-end development communities and Milwaukee SPIN - Contribute to strategic initiatives, architectural patterns and best practices, including release management, application-layer security, Azure, API integration and practical uses for new technologies in the client portal experience Now Requirements/Qualifications from "What You’ll Bring To Baird": - Minimum of 5 years of demonstrated software development experience, including required hands-on modern web application development and experience building and supporting .NET applications working across multiple tiers using technologies such as the Microsoft technology stack, including object-oriented design, C#, MVC, ASP.NET, Web API and related Microsoft platform capabilities - Competence working with SQL Server and other database technologies that support web and mobile digital experiences - Hands-on experience developing modern front-end solutions with React and Next.js, including responsive user interfaces, reusable components, state management, CSS, accessibility considerations and front-end functionality that aligns with business and client experience requirements - Required experience with .NET application development and integration patterns, including partnering across front-end and backend development, working with web services, REST APIs, Web API, authentication patterns and SQL-backed applications - Understanding of web performance, browser behavior, accessibility and mobile-responsive design patterns, with the ability to create intuitive experiences for clients across devices - Passion for software development and experience supporting new development, application maintenance and production support for client-facing or high-visibility business applications - Experience collaborating with internal clients, product owners, business analysts, project managers, quality analysts and developers to gather requirements and successfully deliver software solutions - Creative problem-solving skills with an automation-focused mindset and experience reducing recurring work or enabling user self-service - A quality-focused approach with an interest in incremental delivery, continuous learning, secure coding practices, observability, performance and process improvement - A collaborative mindset with the ability to work effectively within and across teams in an Agile/Lean development environment supporting a large-scale client-facing platform - Strong verbal and written communication skills with the ability to communicate clearly and professionally with technical and business stakeholders - Bachelor’s degree in Computer Science, Computer Engineering or Software Engineering preferred, or equivalent experience Now Schedule: "This position offers a hybrid working arrangement based in either our Milwaukee or Madison office, with at least 3 days per week in the office and the remaining time remote. This schedule supports relationship building and collaboration across leaders and teams." We'll put that as

      under Schedule heading. Now About the role: The first paragraph(s) before "The Impact You'll Make". Let's extract: About The Role Build reliable, client-facing technology for Baird Online (BOL), the web and mobile portal used by Baird Private Wealth Management (PWM) clients to access their financial information and digital servicing capabilities. As an experienced Software Developer on the BOL team, you’ll create, enhance and support modern web applications that deliver intuitive, secure and high-performing digital experiences. At Baird, software development is a craft. You’ll collaborate with a strong developer community in an Agile/Lean environment, applying modern front-end practices, proven engineering practices and continuous learning to build high-quality, maintainable solutions for a highly visible client-facing platform. You’ll join a DevOps culture where IT is a valued business partner and developers are empowered to improve applications, strengthen delivery practices and contribute to the continued growth of our development capabilities. This position offers a hybrid working arrangement based in either our Milwaukee or Madison office, with at least 3 days per week in the office and the remaining time remote. This schedule supports relationship building and collaboration across leaders and teams. Baird is not currently hiring individuals for this position who now or in the future require sponsorship for employment visa status. Note to External Recruiters / Search Firms: Baird does not accept unsolicited resumes and will not compensate for any placement resulting from such submissions. Any unsolicited resumes received will not be treated as valid applications. We need to remove boilerplate like note to external recruiters, visa sponsorship line maybe? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The visa sponsorship line is likely a legal/EEO? It's about sponsorship; might be considered boilerplate. Probably remove. Also note to external recruiters is boilerplate. So we should keep the core description about role, responsibilities, hybrid arrangement etc. But hybrid arrangement also appears later; we might duplicate. We'll keep the description but not duplicate the hybrid arrangement maybe we can keep it once under Schedule. However the About the role paragraph includes hybrid arrangement sentence; we could keep it there but then Schedule would duplicate. Better to keep About the role without the hybrid arrangement line, and put hybrid arrangement under Schedule. But we must preserve all substantive information; removing that line would lose info. However we can keep it in Schedule section and not duplicate in About the role. The About the role paragraph still contains other substantive info. We'll edit out the hybrid arrangement sentence from About the role to avoid duplication. That's okay as we are not losing info because it's captured elsewhere. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove that sentence from About the role but put it under Schedule, we still preserve it. So fine. Thus About the role paragraph will be: Build reliable, client-facing technology for Baird Online (BOL), the web and mobile portal used by Baird Private Wealth Management (PWM) clients to access their financial information and digital servicing capabilities. As an experienced Software Developer on the BOL team, you’ll create, enhance and support modern web applications that deliver intuitive, secure and high-performing

Similar jobs

Software Developer

Everest InfotechEdison, NJ· 3 mo ago
Engineeringapply on everestinfotechllc.com

Software Developer

University of MichiganAnn Arbor, MI· 2 mo ago
$85k–$95k/yrapply on careers.umich.edu