Mobile Engineer

As a Mobile Engineer, you will contribute to the design, development, testing and distribution of our mobile SDKs for iOS mainly, However it is not limited to other SDK’s. Working individually and as a team, you will be developing mobile software components & frameworks. Advise on technical support and product adoption for clients in line with pre-sales, post-sales and the renewal processes. Responsibilities Support full software development lifecycle for new and existing mobile applications, SDKs. Build a highly secure, obfuscated static/dynamic library that is Apple App store compliant to be deployed on client mobile devices. Build reusable iOS software components and develop mobile frameworks based on best practices. Document application requirements, design, test, integration, and other related processes. Keep up with the latest mobile technologies, devices, tools and conventions. Collaborate with internal teams to troubleshoot client integration problems and analyze SDK performance in various iOS environments. Provide technical guidance to ensure successful SDK integration and adoption by clients. Participate in R&D efforts to study emerging mobile attack techniques and security bypass methods. Degree in Computer Science, Software Engineering, Information Technology or related fields Minimum 3 years' of relevant experience in mobile development Proficient on Swift and Objective C with a record of writing clean code Experience building maintainable and testable code bases, including API design, unit testing and UI testing techniques Experience in maintaining applications, crash analytics, remote debugging and continuous integration Familiar with Mobile development tools (iOS - Xcode, CocoaPods, CmdLine Tools and CI/CD etc. Additional Requirements plus to have: Experience in developing iOS SDKs (static or dynamic frameworks / XCFrameworks) Experience in mobile security and reverse engineering techniques like hooking, Jailbreaking etc., Familiarity with Apple platform security mechanisms and runtime behavior