Ich arbeite in Vollzeit bei Affinitas (Germany)
+ Top Firmenkultur (sehr familiär, international, freundlich, kooperativ)
+ Interessantes Produkt (Matchmaking = Singles in langfristige Beziehungen führen)
+ Seriös (TÜV-geprüft + diverse Auszeichnungen)
+ Wirtschaftlich stabil
+ Diverse Benefits (Friday Beers, Company Lunch, ...)
- Gehälter könnten etwas höher sein (steigern sich aber in der letzten Zeit)
Rat an das Management
Ich habe mich persönlich beworben. Der Vorgang dauerte 3 Wochen. Vorstellungsgespräch absolviert im Februar 2018 bei Affinitas (Germany) (Berlin).
Got contacted by a recruiter for a 45 min interview about my experience and some behaviours, then got invited to the first tech interview with a potential team mate.
He has asked me a couple of questions about Android and Testing, which I have answered completely, then I asked him their definition of "Senior" and what would that entail. Their response got me worried, because apparently it had to be someone who "accomplishes his goal regardless of an obstacle". Overall the impression I got was that they were looking for someone who would follow orders and live and breath coding. That worried me, since I didn't hear anything about helping PMs with prioritisation, growing younger team members and having a broad perspective on business and how tech fits into it.
My worries deepened when I got the test-assignment that was actually a full-stack task of writing both a backend and a client-app to make use of it. The code had to follow Clean Code principles and practices and had to be covered with tests first and foremost. This was a huge red flag for me, since I have started to realise what kind of people Affinitas is looking for - software "craftsmen", who dogmatically follow Uncle Bob's principles. I dug around and found out that their CTO is an old-school enterprise engineering manager, a big fan of the aforementioned Uncle Bob. I had problems in past with people like him before who would turn a simple two-man project into a cluster of layers, endless fights over dogmas and "craftsmanship", expectations of working through weekends and prioritisation of vanity metrics such as test coverage.
I decided to check my assumptions and see their website and lo and behold, it was a bug-riddled enterprise mammoth. Even their values page that mentioned quality and attention to detail had a couple of pretty bad UI bugs.
There were so many red flags I thought that I will not go there even if I get the offer unless they will be open to other perspectives of doing engineering. I decided to finish my task and expose their company to a different approach, where Product and UX are put first and foremost and tests are given their priority once the Product is delivered. When I have finished the task - the company stopped responding for two weeks and I have seen from my analytics tool that nobody was using the App that I wrote. In fact - as I learned later, the HR that was handling my communication channel had unexpectedly left the organisation without any notice.
After two weeks of fruitless attempts to get a hold of them and receive the feedback, I finally got it. They did not even want to invite me to discuss my project decisions - just rejected me outright. The feedback that I got seemed not to take into account the fact that I have built a launch-ready MVP in 3 days, completely with databases, cloud storage, multiple authentication types, sorting methods, crashes and analytics tracking... etc. Instead it focused on "unused class here" and "unused method there", "no tests" and other things that were purely stylistic. Apparently that was enough to just stop the interview process in it's tracks even though the app was polished and had clean, extendable architecture, followed SOLID principles and would definitely support writing their lovely tests at some point.
Fragen im Vorstellungsgespräch
Teilen Sie uns mit, wenn Arbeitsplatz- oder Branchenauszeichnungen nicht berücksichtigt wurden –