FAQs
What are the key responsibilities of a Software Development Engineer in the AB Pricing Tech team?
The key responsibilities include participating in the full development cycle from design to delivery, evaluating and making decisions on technologies and tools, mentoring junior development engineers, collaborating with Senior and Principal Engineers to define architectural plans, driving team decisions on build vs. re-use, and setting standards for handling operational load.
What are the basic qualifications required for this position?
The basic qualifications include at least 3 years of non-internship professional software development experience, and a minimum of 2 years of experience in design or architecture of new and existing systems, including knowledge of design patterns, reliability, and scaling.
What preferred qualifications enhance a candidate's application for this role?
Preferred qualifications that enhance a candidate's application include 3+ years of experience in the full software development life cycle, proficiency in a modern programming language such as Java, C++, or C#, experience in object-oriented design, and contribution to both new and current systems architecture and design.
What programming languages are most relevant for this Software Development Engineer position?
The most relevant programming languages for this position include Java, C++, and C#, with a focus on object-oriented design experience.
Is experience with code reviews and source control management important for this role?
Yes, experience with coding standards, code reviews, source control management, build processes, testing, and operations is important, as it reflects understanding and contribution to the full software development life cycle.
Will there be opportunities to mentor junior engineers in this role?
Yes, one of the key responsibilities of this role includes coaching and mentoring junior development engineers.
How will this role contribute to the team's architectural plans?
This role will contribute by directly collaborating with Senior Engineers and Principal Engineers to define the architectural plans for the next three years and by driving decisions on whether to build new solutions or reuse existing systems.
What does the phrase "operational load" refer to in this job description?
"Operational load" refers to the ongoing day-to-day demands and performance tasks that the software and systems must handle, and the role involves setting standards and mechanisms for effectively managing that load.
How important is collaboration with other teams, such as Retail and Seller Pricing teams, in this role?
Collaboration is very important as it drives decisions on build vs. re-use and ensures that the solutions developed meet the broader needs of the organization and its various stakeholders.
Can candidates without prior mentoring experience apply for this position?
While mentoring experience is preferred, candidates with strong technical skills and experience may still apply as long as they are willing to take on a mentorship role.