Now, back to you, our new Senior Android Developer...

You're a software developer with over 5 years of professional experience, with most of those being spent working on Android. You know how to write easy-to-maintain software while still keeping an eye on the roadmap. 

 

You'll help us write and maintain features in our Android app. We believe in the power of native user interfaces on each platform, and are incredibly excited about Jetpack Compose, but we’re also the sort of folks who get excited about elegantly sharing business logic across all our platforms. To that end, we have a home-built shared library based on Typescript and SQLite that uses the V8 engine. You don't have to be an expert on TypeScript or SQL, but being curious about how things work on that layer definitely helps. 

 

We’re already spiking on integrating Kotlin Multiplatform as well, and have some exciting proof-of-concept code committed to all of our platforms, so this is also a great time to get in at the start of a big Kotlin push.

 

Some technologies we use on Android:

• minSdkVersion 23


• Kotlin for all new code


• Moving towards a unidirectional data flow architecture


• ViewBinding


• Integrating with V8 JS engine


• RxJava, Dagger, Robolectric


• Bitrise CI


• Github


• SQLite (and thus SQL)


• Typescript

• Write code that is easy for other developers and your future self to understand and use.


• Have extensive experience with Kotlin and Java.


• Have shipped or helped ship at least one significant app for Android.


• Have excellent debugging skills. You know how to find problems, and how to architect apps so that problems are unlikely, but discoverable if they do happen.


• Are self-motivated and thrive with directions like:


• "This part of the program is too slow. Can you find out why?"  


• "This component needs to be re-architected to allow for new feature X. How do you think we should do it?"


• “Our code needs to call into a Javascript library, but that Javascript library is crashing because it can’t find the setTimeout function. Can you investigate?”


• Are excited to work across multiple platforms with different technologies.


• Have an understanding of algorithms and data structures that goes beyond arrays and “for loops”. That doesn’t mean you have to be a computer science PhD or even that you have to know “Big O” notation, but you should know when to use a Dictionary/Map, and why finding an element in a sorted array is faster than finding an element in an unsorted array.


• Are a senior developer who can point to strong experience where you’ve exemplified the bullet points above.


• Feel right at home with Git/Github, and can happily talk about the pros and cons of different Git branching models and workflows.