Our client is a SaaS Security scale-up that meets the growing demand for security, privacy, efficiency, and user-friendliness in secure information sharing. Their platform is a SaaS application written in Scala that serves the Angular Typescript web application and C# Microsoft apps. They manage their (AWS at the moment) infrastructure as code: if it's not under version control in git, it does not exist. And the other way around.
We expect you to have an opinion on tech. We expect you to pick your own hardware and operating system, because that's how you get productive. Having the best tools at your disposal, you're prepared to question everything you see and do not understand. If it can be improved, you’ll re-prioritize and start improving from within.
You're entering the office around 9.30h. Usually you're earlier, but because of the rainy weather you decided to grab you first coffee at home while checking the output of the daily backup tasks. The backup of GitLab failed because the server ran out of temp disk space.
Once you arrive at the office a colleague already removed some old log files and restarted the backup task. This allows you to focus on the database locking issue you discovered yesterday. After querying the application logs in Kibana you come to the conclusion that one code path in the backend can easily be consolidated to do only one write operation instead of two. You write a fix and a test and you ask backend engineer from the End User team to review your code. It's time to have lunch because in the afternoon you have a meeting on how to set up and improve the auto scaling of the backend service.
Later in the afternoon you discuss the performance and platform related bug reports during the daily stand up. Your review of this morning was accepted, but your peer insisted on writing better scaladoc. After adding a few useful comment lines you merge your branch. A release to production can wait for tomorrow, so it's time to go home.