Lead Software Engineer - job 12 of 44

As a Lead Software Engineer at MAP, your responsibilities entail building expertise on our 24/7 systems, collaborating with both development and product teams to streamline development processes, and automating production support activities. You’ll also be tasked with creating performance models for a highly scalable payment processing framework, ensuring that application performance is optimized, and contributing to capacity planning and disaster recovery.

To apply for the Lead Software Engineer position at MAP, candidates should possess a Bachelor's degree in Computer Science or Engineering, while a Master's degree is advantageous. Hands-on experience with Unix/Linux OS, along with coding knowledge in languages like Java or Python, is crucial. Familiarity with performance monitoring tools and exposure to Agile teams are also preferred qualifications.

Essential technologies for the Lead Software Engineer position at MAP include in-depth knowledge of Unix/Linux environments, proficiency with containerized microservices architecture, and experience with tools like LoadRunner, JMeter, and APM solutions such as AppDynamics and Dynatrace. Familiarity with monitoring tools like Splunk or Grafana will be an added advantage.

The work environment for a Lead Software Engineer at MAP is hybrid, allowing flexibility between remote work and in-office collaboration. You’ll engage with talented professionals in a fast-paced atmosphere while being supported by a culture of innovation and teamwork, which fosters both personal and professional growth.

Yes, the Lead Software Engineer role at MAP does involve on-call responsibilities, aligning with our commitment to maintaining high availability and performance for our merchant systems. This means you will need to be prepared for potential troubleshooting and performance monitoring outside of normal operating hours.

When answering this question, detail your hands-on experience with Unix/Linux, emphasizing your understanding of operating system internals and any specific tasks you managed, such as configurations, performance monitoring, or scripting to automate processes.

Discuss your strategies for capacity planning, such as analyzing performance metrics and forecasting future needs. Highlight your experience with disaster recovery methodologies, including how you create and test recovery plans to ensure system resilience.

Detail specific methods you’ve used to identify and resolve performance bottlenecks, such as utilizing APM tools, analyzing code, and implementing caching strategies. Present examples of how these actions led to measurable improvements.

Share your ongoing learning habits, whether it be through online courses, attending workshops, or staying engaged with professional communities. Mention specific technologies or tools you actively explore and implement in your projects.

Provide an example that illustrates your collaborative approach. Focus on your contributions to the project, how you balanced technical requirements with product goals, and the outcome of that relationship.

Explain your practical experience with containerization technologies such as Docker or Kubernetes, discussing how you've leveraged microservices for better scalability and maintainability of applications.

Describe your process for deployment, including pre-deployment checks, communication with team members, post-release monitoring strategies, and how you mitigate risks to ensure a smooth launch.

Discuss the challenge, how you identified it, the steps you took to troubleshoot, and the ultimate resolution. Emphasize your analytical skills and ability to remain calm under pressure.

Talk about the importance of automation in improving efficiency, detailing specific processes you’ve automated, the tools used, and how this impacted overall productivity in your previous roles.

Highlight your leadership style, focusing on mentoring junior developers, fostering a collaborative environment, and the impact of your leadership on team morale and project success.