Luxoft is a global leader in high-end software development.
Luxoft is looking for talents with a passion for technology & ready to create original solutions. Once on board, you are invited to expand your knowledge & skills, offering you a continuous learning experience helping you stretch your potential.
So if you’re enthusiastic by the idea of accessing cutting edge technology & innovation to make an impact, why don't you join us?
- Implementation of good quality solutions, enhancements and improvements to the platform
- Manage production issues escalations to bring the system back from the outages and ensure impact elimination
- Solid Java Core knowledge
- Good SQL knowledge
- Unix and scripting skills
- Ability to manage a team as well as delivery and support processes
- Excellent communication skills
- Analytical thinking and Problem solving skills
- Leadership skills
- Investment banking background would be a big plus
Project assumes small features, enhancements, audit items implemenation, infrastructure upgrades and stability improvements. Dedicated focus on production stability
Other systems:
Upstream they've mentioned external data sources like Bloomberg, they do feed in/from FX. They feed into/from regulators and reporting institutions as well. Some feeds are flat files sent over FTP (that'd be replaced with a more secure solution).
This particular system is a reference data source for some flows downstream.
Part of system's functionality is transforming and normalizing data, settlement, etc.
Technical debt is known and huge.
GS is in the beginning of a massive infrastructure upgrade - as they said they are looking to replace hardware, software and middleware.
OS is Solaris, databases are Sybase (currently 12, targeting to upgrade to 15).
They do have a dedicated team of Sybase DBAs. For the system we discussed there is no data processing on the DB, mostly in Java.
Some databases are shared with other systems .
For Sybase upgrade they would need a lot of performance testing - not automated (previously relied on iwatch).
Spawning new environments is semi-automated, env. is built manually (no docker, no continuous deployment), then the deployment may be triggered.
Builds run on Jenkins
They clearly articulated they won't need .Net expertise in this team of 5 - there is some UI team, later on they plan to move all UIs to their Angular-based framework.
They seem to run ETL on a proprietary EMS, new projects however use Kafka for messaging.
Priorities for the team:
- Bring the system back up ASAP from any outages which not managed by L1 and 2 support line
- Critical backlog items processing
- Tech debt elimination.
Processes:
Team to manage full cycle from requirements analysis to deployment down to post-support activities
As part of business continuity they exercise DR regularly, developers take part in that. Failover itself is more or less automated, many things are still manual.
Replaying the feeds in case of outages is done by L2/L1 with the help of some tools.
SoD/CoB rituals performed by L2/L1
They have some ITSM and problem tracking software, not sure these are integrated.
Knowledge Base resides in Confluence.
Tendency is to release monthly.
There is some steering committee running weekly to prioritize the work (devs not involved).
There are regional leads - these are the people with extensive domain knowledge and some tech expertise as well.
Changes are reviewed and/or requested by regional leads.
Other systems:
Upstream systems list contains external data sources like Bloomberg, they do feed in/from FX. They feed into/from regulators and reporting institutions as well. Some feeds are flat files sent over FTP (that'd be replaced with a more secure solution).
This particular system is a reference data source for some flows downstream.