Software Engineer Specialist for FIS® Securities Lending Processing Platform - job 1 of 2

As a Software Engineer Specialist at FIS Global, your primary responsibilities will include designing, programming, debugging, and modifying software enhancements for the Securities Lending Processing Platform. You will interact with product managers to clearly define requirements and necessary modifications, and you'll participate in software design meetings to establish technical requirements, ensuring that your contributions effectively impact the workspace.

To apply for the Software Engineer Specialist position at FIS Global, you should have a Bachelor’s degree in Computer Engineering, Computer Science, or a related discipline, along with relevant work experience. Proficiency in HP NonStop Cobol development is essential, as well as an understanding of financial industry practices and regulations.

Yes, for the Software Engineer Specialist role at FIS Global, proficiency in HP NonStop Cobol development is required. Additionally, familiarity with languages and tools like SQL MP, TAL, and TACL will give you an edge as these are valuable in determining technical specifications and designing solutions.

At FIS Global, a Software Engineer Specialist can expect substantial opportunities for career advancement. As part of an innovative company focused on fintech, employees are encouraged to engage in continuous learning and development initiatives, making it possible to progress into roles with greater responsibility, such as senior engineering positions or management roles in technology.

Absolutely! FIS Global is committed to championing diversity and creating an inclusive workplace that values contributions from all backgrounds. As a Software Engineer Specialist, you will be part of a team that fosters a respectful and collaborative culture, ensuring that everyone's ideas and insights are welcomed and valued.

When approaching debugging, I systematically replicate the issue to understand the conditions under which it occurs. I then use tools and logs to trace back the problem, ensuring that I gather as much data as possible to identify the root cause. It's about maintaining a logical flow and not rushing the process to ensure quality results.

In my last role, I worked on a complex integration project that required a deep understanding of both front-end and back-end systems. I faced significant challenges with API compatibility, but by employing a proactive communication strategy with my team and thorough testing, we successfully resolved the issues and delivered the project ahead of schedule.

I primarily use tools like UML for software design, Jira for project management, and Git for version control. These tools help streamline collaboration with my team and allow us to maintain clarity and organization throughout the development cycle.

To ensure maintainability and scalability, I adhere to best practices, such as writing clean, well-documented code and utilizing design patterns. My approach includes thorough testing and peer reviews to ensure that the code can be easily understood and modified in the future without introducing errors.

I prioritize tasks based on deadlines and complexity, allocating time blocks to focus on each project while ensuring flexibility for unforeseen issues. Regular check-ins and updates with my team help maintain alignment and adapt to any necessary shifts in priorities.

User experience is critical in software development as it directly affects user satisfaction and engagement. By placing the user at the center of development, we ensure that the product is intuitive, meets their needs, and enhances productivity, ultimately leading to greater adoption and success in the market.

I invest time in continuous learning through online courses, attending workshops, and following industry trends via tech blogs and forums. Engaging in coding challenges and contributing to open-source projects also allow me to refine my skills and explore new technologies.

I have extensive experience collaborating within diverse teams, utilizing tools like Slack and Zoom to facilitate communication. I believe in fostering transparency and open dialogue, which helps ensure that everyone is aligned on project goals and can freely share insights and feedback.

I view constructive criticism as an opportunity for growth. During code reviews, I remain open-minded and receptive to feedback, recognizing that it helps to strengthen my skills and improve the overall quality of our work. I take notes and seek clarification whenever needed to fully understand the suggestions provided.

When defining technical requirements for software applications, I start by gathering input from stakeholders, conducting interviews, and analyzing existing systems. I then outline the specifications in clear, detailed documentation, ensuring that all team members understand the requirements and how they align with the project goals.