Eric Collom Email & Phone Number

Minneapolis, Mn, Us

Minneapolis, Mn, Us

Washington, Dc, Us

Philadelphia, Pennsylvania, Us

• Built marketing iOS application to to bring in more customers. Used SwiftUI, RealityKit, SceneKit, Core Location, MapKit and HealthKit.• Technical writing - wrote multiple articles covering topics such as actors, property wrappers, swizzling, and block chain data permanence.• Maintained hybrid iOS and Android application built using Ionic, Capacitor, React, and Typescript.

New York, Ny, Us

• Consumer facing banking services application with over 100,000 users and 4.8 app store rating.• Led feature teams consisting of QA, back-end, and front-end engineers. Answered questions around implementation details, removed blockers and assisted engineers in getting their job done.• Team wanted to explore implementing new features in SwiftUI. Proposed solution to facilitate transition from UIKit to SwiftUI. This included styling, analytics and allowed for new SwiftUI code to be used in UIKit hybrid scenarios.• QA team had trouble duplicating bugs due to lack of network logging. Refactored networking code to include request and response logging which redacted customer personal private information. Also, added logging for decoding errors. This helped QA rapidly identify sources of certain bugs.

Minneapolis, Mn, Us

• Helped build out core functionality and architecture of new flagship application.• Application was having Core Data issues with efficiency, duplicate data creation, and schema design. Proposed a solution to fix schema design issues. This resulted in faster batch deleting, as well as removed edge cases where some objects could not be batch deleted. Additionally, cleaned up save code to be more concise and not duplicate objects.• Client was losing customers due to legacy Objective-C application being hard to use. Implemented new simplified workflow, that was built using Swift, that tied into legacy Objective-C code. Team increased test coverage from 0% to 8% and implemented black box testing to assure changes to legacy code did not break old UI and workflow. Received positive feedback from users.

Minneapolis, Minnesota, Us

• Improved application stability and reduced bugs by adding unit tests to current code, wrote tests for reported bugs, and used dependency injection in order to facilitate testing new code.• Improved application security before transitioning it from the B2B application store to the general store. Added API secrets along with obfuscation, masking, and honey pots.