1,516 karma · joined October 18, 2011
https://parallelthoughts.xyz
https://twitter.com/mgill25
Interview process is 3 parts:
1. We do a semi-technical first call with you - getting to know your professional and technical experience, what you're looking for, presenting the team, and some high level design/architecture thinking.
2. If we want to proceed, we send you a coding challenge (Easy/Med/Hard all 3 types of problems - and the time setting is relatively relaxed). You can take that on your own time.
3. If you clear that, then it's just getting to know all of the team. Everyone talks to you/get to know you/tell you about the role etc. This is time consuming but not heavy on the technical side.
That's it. Then we make a decision.
We also have a team member in the US, so really, for the right candidate, we are flexible about the location. But it's really the exception rather than the rule, so we are leaning EU first right now unfortunately. But that shouldn't discourage you from applying!
My team at TomTom is hiring Senior Software Engineers to work on a Global-Scale Traffic Prediction System. It's a pretty cool setup and work-life balance is great. We work on very large scale traffic data - the code you write will produce what drivers see on their navigation systems.
We're doing Scala / Java / Python / Spark / Terraform / Azure / Github Actions
At least in my team, the focus is on solving problems - so if you can solve a problem using $YourFavoriteTech, and help onboard the rest of the team, you'll get the freedom to do so.
Combination of Data/ML Engineers, Data Scientists, and Full Stack Engineers. We have the entire Machine Learning life cycle - from labelling to prediction.
Job spec says Amsterdam and Berlin, but I think we're pretty flexible if you're anywhere, and you're good.
Positions:
- Senior Software Engineer https://www.tomtom.com/careers/jobdetails/JR0009102/sr-softw...
- Senior Data Engineer https://www.tomtom.com/careers/jobdetails/JR0009122/sr-data-...
- Full Stack Software Engineer (Java/JVM) https://www.tomtom.com/careers/jobdetails/JR0007891/full-sta...
Feel free to send me an email. Contact Information is in my profile.
Perhaps I should throw out my CLRS and Skiena and invent everything in those books from scratch?
It's an Arms race because people like you have turned it into one. You're not solving Nobel prize winning problems, so stop expecting people to magically invent on the spot novel algorithms for things they've never seen before.
Some people are good at it and some are not.
Like holy crap, it's a very well written and well thought out piece of software. And it's fast. I'm all about the Rust hype, but Kitty reduced latency drastically.
The problem with DSLs and Config languages is that someone will inevitably try to use them in a way they are not designed to be used, and then circumvent the way you're "supposed to" do things. Not only do you lose all the advances in tooling, but people will end up reinventing things that already exist in the other languages.
PS: Of course, I'll pick Static Typing every time.
a) Learning K8s and Helm Concepts (both different things)
b) Reading/Debugging K8s and Helm YAML (both different things)
c) Ending up at Helm Chart Configs (another config)
d) Figuring out how to set all this to helm me deploy the solution I needed and customize it acc to my needs
...all within the span of a few weeks.
So by the time I got to some GitHub repos which were using Jsonnet, I was basically done. I'm sure it has its uses and given enough time and experience, I can see how to utilize it more effectively.
I went into the rabbithole of terraform/HCL and came up with Terragrunt to do dynamic code generation. Combining it together with generous use of `make` keeps me sane, but it's not a long term solution.
Even now, there are things within the system where the boundaries should be separate, but they aren't.
We literally got exhausted and burned out writing our automation, and decided to leave it as it is and then slowly build it up over the next few months. :/
PS: You're 100% right re K8s/YAML. It feels like everything in the Kubernetes world is optimized for writing the code just once. Which, of course, is easy if you already know how all the various bits fit together (true in any system).
But Reading/Debugging kubernetes world is a dreadful experience.
Edit: typo
We're far too invested into Terraform at this point to learn yet another tool. Oh well. Hopefully the next time I have to implement something like this, K8s ecosystem would also have similar tools (or maybe I just missed something)
We (a colleague and I) basically learned Terraform, then Kubernetes, and then Helm in an extremely stressful environment. I wouldn't recommend that to most people. (Also, I can hear "you don't need k8s", but tbh, it makes the difficult things possible, and that's what we needed).
I've done Ops in bare-metal environments before, and at least there, even if there were new skills to learn, the environment just wasn't so hostile for beginners, and the learning curve was simpler.
The YAML (or heaven forbid, jsonnet) does *not* help. TBH, I'm convinced if the IaC bits were done in a regular Java/Go/Rust SDK style instead of mixing and matching YAML glued together via labels and tags, I would have had a much easier time.
The positive side of that is that now the IaC bits are mature enough that even the Data Scientists in our team write their own Terraform code, and I've upskilled myself quite a lot. I'm slowly going back to solving Storage/Data/ML issues, which I enjoy a lot more.
Maybe I'm just becoming a cranky Software Dev as I enter my 30s. I do _not_ enjoy reading YAML.
Question to experienced Rust people: What are some cool use-cases that you've seen for Macros?
Of course, one guy was prepared and literally _ran_ to the FEX. We walked and then waited 30 mins for the next one to arrive. :)
Took a vacation to Rome and Venice, and just 5 days away from home were enough to decompress. Feeling really good now.
Wish I had more time for open source contributions, but marriage + work are almost leaving no time at all. Got something going but the big tasks require a lot more dedicated effort.
Now thinking of new places to go on vacation in Southern Europe to escape from the cold :)
> Some candidates make it hard because they want to keep persevering, keep thinking
Yeah, amazing that some candidates want to demonstrate their perseverance even in face of problems that they find challenging. Crazy right?
But what surprised me immediately and the thing I'm absolutely loving is the error handling (https://twitter.com/mgill25/status/1416720958988210177) and the comptime features.
I've done Rust and while I love what it's doing, getting into low-level C-world without the overhead of a language like Rust feels liberating.
*AWS* - Lots of sales calls, but eventually redirected us to a "partner", who came up with basically a lift-and-shift.
*GCP* - The Regional Business Head was in direct contact. We were provided almost limitless access to a very helpful and experienced Customer Engineer - who spent _weeks_ with us, designing architecture, doing presentations, giving us learning material and eventually was instrumental in my team's increased capability and skill level to do the new infra design. Both came to visit the office several times. Eventually more senior engineers got involved.
We were also repeatedly given generous credit extensions. And best of all - there was a GCP summit in the country, during which I literally had a sit-down with PMs from a lot of GCP's product offerings - including Spanner, BigTable. 1:1 video calls with PMs from FileStore, Dataflow and BigQuery as well as early access to some key features.
Worth noting that we were hardly a "big" customer, or a huge money spender. Perhaps it was the technical challenge that interested them, or perhaps the reputation of the company/founder in the region. Whatever it was, I've had great experience with GCP.
Of course engineers have a tendency to over-engineer solutions. I don't think anyone is surprised by that. But this "oh you don't need it, I've used it at <bigcorp>, and you're not that" thinking just rubs me wrong. Especially when it's backed up by hollow arguments like the ones in this post.
This entire article can be surmised by "You don't need Kafka because the throughput seems to be low". To which the retort can be many: they might be building for the future - to integrate more systems, they might have fan-out use cases, they might want to have a log to replay in case of disasters - so on and so forth. All well documented and very valid use cases of Kafka.
But of course, "You don't need Kafka" because <reasons>.
A very bad taste in the mouth indeed.
So far, it's allowed me to dive deep into how Map Reduce works, I even presented GFS in a local Distributed Systems group, and was able to understand Raft. I'm currently doing Raft labs (which is when the Pandemic happened). I've designed some sharding schemes in my previous company and worked a lot on Streaming systems but learning the theory behind everything is amazing.
If there are people here who would like to put a serious joint effort into doing this course, I would absolutely 100% be interested in it. Doing this alone from my apartment in a foreign country gets a bit tricky vs doing it in a group setting. :)