| 18 Oct 2023 |
 Alex | ScalaJobs.com | GrapheneDB is hiring a Senior Scala Engineer to work on graph databases as a service
Location: Remote UTC+0 to UTC+3
4 day work week
Find out more 👇
https://scalajobs.com/featured-jobs/GrapheneDB-Senior-Scala-Engineer-100percent-Remote-4-Day-Work-Week-jRMvSPAzpOQ0RxSgZDUH | 08:15:50 |
|  geirolz changed their display name from Geirolz to geirolz#0. | 10:51:47 |
| geirolz changed their display name from geirolz#0 to geirolz. | 10:51:50 |
| 19 Oct 2023 |
 som-snytt | 
Download image.png | 01:01:04 |
| som-snytt | Ah, I read it as "content/commas role". That would have been in my wheelhouse. | 01:01:04 |
| 20 Oct 2023 |
|  AlexITC | 03:29:55 |
| AlexITC | 03:29:57 |
| AlexITC | Etsy? | 03:29:58 |
|  derya changed their display name from derya to derya#0. | 21:38:28 |
| derya changed their profile picture. | 21:39:03 |
| derya changed their display name from derya#0 to derya. | 21:43:39 |
| 22 Oct 2023 |
 sethtisue | you could also try the monthly jobs thread on the Scala Reddit | 01:37:15 |
 julian.a.avar.c | Redacted or Malformed Event | 13:40:06 |
| julian.a.avar.c | https://tenor.com/view/emotions-spiritedaway-noface-wave-gif-4347416 | 19:19:31 |
| 24 Oct 2023 |
|  whiteturq | 19:11:38 |
| 25 Oct 2023 |
|  lafeychine changed their display name from Vincent Lafeychine to lafeychine. | 13:35:17 |
| 26 Oct 2023 |
|  progamermatt changed their display name from pgm to progamermatt. | 15:15:17 |
|  red2green changed their display name from red2green#0 to red2green. | 18:31:13 |
| 27 Oct 2023 |
|  txdv | 06:36:28 |
|  Chris Kipp | 06:40:01 |
| 29 Oct 2023 |
|  cu4381 changed their display name from cu4381#0 to cu4381. | 23:32:41 |
| 1 Nov 2023 |
|  potatoef changed their profile picture. | 16:21:39 |
 Mehdi | domschoen are you open to full remote? | 19:24:24 |
| 2 Nov 2023 |
| sethtisue | when I was involved with hiring, we would offer candidates a take-home challenge if they felt they had no other code they could bring in. but we made it clear that the preferred choice was to bring in some code they already had, that they would enjoy showing us and discussing with us | 15:59:01 |
| sethtisue | and that was partly because we felt it was unreasonable to demand people spend time on an arbitrary challenge, and partly because we actually would rather look at code they actually cared about and had chosen to show us, as more informative | 16:01:12 |
| sethtisue | * when I was involved with hiring (at multiple shops), we would offer candidates a take-home challenge if they felt they had no other code they could bring in. but we made it clear that the preferred choice was to bring in some code they already had, that they would enjoy showing us and discussing with us | 16:01:23 |
| sethtisue | so yeah, I think what you're describing reflects poorly on the company, but it might be a common enough practice that you can't afford to consider it a dealbreaker in every case, if you want the job enough? 🤷 | 16:03:03 |
| sethtisue | it might be a bureaucratic requirement from above that doesn't reflect the atmosphere on the team you'd actually be working on. (but if there is one such requirement, you can suspect there will be others...) | 16:04:40 |
| sethtisue | * it might be a bureaucratic requirement from above that doesn't reflect the atmosphere on the team you'd actually be working on. (but if there is one such example of bureaucratic nonsense already, you can suspect there will be others...) | 16:04:57 |
 daenyth | I think this is the most important part - the company is acting unreasonably, can you afford to pass based on that | 17:21:25 |
