Team Lead - React/Node-JS
Location: Brisbane, Australia or remote
You will be working in a team of developers, alongside a team of domain experts and test analysts to provide a world class solution for libraries and information industry
You will be spending 70% of your time in development with the other 30% managing the roadmap and engaging with our customer success team to align our development with customer and market expectations. You will focus on continuous improvement, strategy, code reviews and the implementation of coding standards and quality measures.
We use React, Node-JS, XML, SOAP, REST API's, JSON, Cache' Objectscript, Python and some C#
Responsibilities:
- Management of the development roadmap and product direction
- Product specification and design using agile methodologies
- External integrations including social media, eResources and integrations to third party open source modules
- Undertake R&D to research and investigate new software tools, libraries and other emerging features such as ML
We are looking for:
- Minimum degree level qualification with good organisational/time management skills
- Thorough knowledge of modern web based technologies
- C# & Cache' ObjectScript an advantage
- German language an advantage
- Thorough understanding of the browser DOM
- Knowledge technologies such as Vue, Angular and Redux, an advantage, as well as Github/Gitlab and unit testing environments
- Full Australian work rights
The Product:
LIBERO is fully web based, highly functional and developed on a scalable platform allowing it to run on most devices. LIBERO is deployed nationally within Australia and internationally, particularly the EU and Germany. It services the needs a varied range of organisations.
The Company:
Insight Informatics is a flexible company focused on providing the best solutions to libraries (see: https://libero.com.au). Whilst our office is in Brisbane, most of us work remotely.
Please forward a covering letter summarising your key strengths along with your CV to sam@libero.com.au
I was a UQ student 2005-08 and can confirm you got 150mb/month quota with the option to buy more at $10/gb. If you lived on campus that was your only option for Internet.
Thanks for confirming this. My 2009 date was off, it was actually 2007 and I glad you clarified for me. My 200 MB/month was based on rough memory and I thought I might have made it up.
Hmmm.. I made the pipes move up and down and now the neural network isn't doing so well :P
I've added "vertical velocity of next pipe" and "distance until next pipe" as inputs as well as upped the hidden layer neurons to 4 - anyone have any other ideas to improve its performance?
Insight Informatics | http://libero.com.au/ | Full Time | Brisbane/Gold Coast or REMOTE (within Australia)
We're an established company of 15 responsible for delivering a world-class Library Management Platform to Public, Corporate and University Libraries around Australia, Germany, Italy, Switzerland, UK and UAE. Our mission is to provide the best set of tools that empower libraries to build communities, simplify their day to day running and provide exactly what their members need.
We're looking for a Front-End Developer
- You'd be joining our five-person development team.
- Our app is 100% web-based. Currently it's an MVC style framework + unstructured javascript. You'd be helping us transition to an API-first system with a React.js based frontend
- More importantly, there's a massive scope for UX improvements along the way which have a real impact on our users
Shoot us an email at seb@libero.com.au to chat if you're interested.
Insight Informatics | http://libero.com.au/ | Full Time | Brisbane/Gold Coast or REMOTE (within Australia)
We're an established company of 15 responsible for delivering a world-class Library Management Platform to Public, Corporate and University Libraries around Australia, Germany, Italy, Switzerland, UK and UAE. Our mission is to provide the best set of tools that empower libraries to build communities, simplify their day to day running and provide exactly what their members need.
We're looking for:
Front-End Developer
- You'd be joining our five-person development team.
- Our app is 100% web-based. Currently it's an MVC style framework + unstructured javascript. You'd be helping us transition to an API-first system with a React.js based frontend
- More importantly, there's a massive scope for UX improvements along the way which have a real impact on our users
Sales/Business Development
- This isn't my area of expertise, but if you email sam@libero.com.au he can take it from there
Shoot us an email at seb@libero.com.au to chat if you're interested.
Version Free sounds amazing - I can see the pros of being able to add/deprecate fields at the same API endpoint, but I find most of the reason we version our API is for field type changes as the data schema naturally evolves. We need to keep track of finer grained data in existing fields that wasn't originally thought of.
To take the Star Wars example at https://github.com/facebook/graphql and build on it. Let's say after this is deployed we need to expose a Planet's population as well. Now homePlanet goes from being a String to a Planet { name population } object.
This type change would break existing clients - the only real solution I can think of is introducing the planet object as PlanetDetails (essentially PlanetV2) and deprecating planet, but that's just back to versioning.
I feel like there must be a better way to deal with it? Interestingly, the graphql format allows this to be differentiated (as the old API won't request an object), but there appears to be no provision to union two non-objects into a single field?
Sure there are strong similarities to versioning, but I think the difference is in how callers get migrated. In GraphQL you can update each callsite incrementally. Imagine half the app has been converted to calling PlanetDetails {name} and the other half still calls homePlanet. That's totally fine -- the app will totally work, compile, run, everything.
Whereas contrasting with REST versioning or traditional versioning, it becomes quite difficult to mix API versions internally (each callsite needs to specify their desired api version before specifying fields) or impossible outright. If the latter, you're then forced to migrate all at once from a given version to another, which requires a ton of coordination across teams and big scary "flip the switch" moments.
This gets worse as you scale up your org, which is why GraphQL has served FB well.
Yeah, introducing a new field and deprecating the old one seems like the best option here. The nice thing is that while this introduces new functionality, there's still only one version of the server; if you query for `homePlanet`, you always get the name, if you query for `homePlanetDetails`, you always get the planet object. This is particularly useful for tooling, since the API response is a function only of the access token and the query.
Insight Informatics - http://libero.com.au/ - Brisbane, Australia or REMOTE (within Australia)
We're a team of 12 responsible for delivering a world-class Library Management Platform to Public, Corporate and University Libraries around Australia, Germany, Italy, Switzerland and the United Kingdom. Our mission is to provide the best set of tools that empower libraries to build communities, simplify their day to day running and provide exactly what their members need.
Front-End Developer: We're entirely web-based and have been prototyping our latest stuff with React.js - our customers love what we've come up with so far. We're after experienced people passionate about user experience to invent new ways to interact with your library, as well as build upon what we have at the moment.
Shoot us an email at seb@libero.com.au to chat if you're interested, or even if you were/still are that kid that likes hanging out at the library.
