I work in ecommerce and I feel it’s somewhere in between. We need to build for seo optimizations for the category/product experiences yet there is a lot of application like intersections, especially on the category filtering and the product sku selections. Quickshops, In store pickup modals, user specific recommendations trays, add and edit reviews et all. Different caching for server render at the edge vs personalized components adds another layer. Being able to serve with a shared routing scheme both client side (for improved performance) and server side for faster initial page load and seo on non-Google crawlers is a tough problem. Especially when you add in client hydration of the redux store. That parse time is a real killer on mobile. You add in service workers and prefetching and the complexity ratchets up further. The other issue we deal with is marketing pixels and trackers. But that’s another story. There is a ton of complexity in building a highly functioning ecommerce site.
Is it really worth the trade-off? I remember eCommerce sites trying to do similar levels of interactivity with Flash too. I just think, for a catalog site, it seems like you're trying to swim upstream. Especially on mobile.
The URBN Mobile Engineering Team is responsible for creating and delivering the URBN brand applications (UO, Free People, etc.) as well as a suite of applications that power our retail experiences. We are located in a new building on the URBN campus in the Philadelphia Navy Yard.
The mobile team is leading change at URBN using the latest SDK features, cross-functional collaboration, and hard work. The engineer for this position should be someone who has shipped multiple applications to the app store; that can collaborate and influence designers, product owners, as well as peers; someone who can translate features and work to other members of the company. Good ideas come from everywhere and the mobile team expects open mindedness when approaching a solution.
The right engineer for this position should be passionate about Objective-C, while having the ability to pickup other languages across our stack (Java, JavaScript, Python) if needed. Futhering the existing automation and testing suites will be one of the main goals of this candidate, so experience is a must. The mobile team engineers also have strong opinions
Guidelines:
- Experience with the software development cycle: product specification, design, implementation, QA, release, and maintenance.
- 2+ years professional experience in creating native iOS applications, preferably ones that have been approved for release in the App Store.
- Familiarity with common libraries and Cocoa design patterns.
- A strong desire for developing high quality applications utilizing unit and integration testing techniques
- A strong passion for learning and adapting to new technologies.
- Ability to multi-task and context switch when necessary
We are carefully growing a fantastic team here at URBN and there has never been a more exciting time to get involved. We hope you'll come join in the fun!
Please send your CV and Github account user to: talent@urbn.com
This is why I moved our standup to Skype. Even if people are away from their computer, you can join a group chat via Skype mobile from the car (handsfree of course). I agree with some of the other points, but if you start to get a good rhythm on how the meeting is run, overages can be minimized. I couldn't imagine not doing this meeting at least as virtual meeting. The last thing I need is to be archiving E-Mails as PDFs.
