est. sometime recently
Somewhere between "we have a plan" and "let's figure it out." Mostly the second one if we're honest.
Make things people use. Then pretend we planned all of it from the beginning.
We don't write code. We feel it. The vibes dictate the architecture. The energy ships the feature. Trust the process.
We throw events. Attendance is encouraged. Baby oil provided. What happens at the offsite stays at the offsite. You love us.
Started the whole thing. Regrets nothing. Has opinions about everything, especially things that aren't his department.
Writes code that actually works. Silently judges pull requests. Drinks tea, not coffee (controversial).
Makes things look intentional. Has 14 shades of the same color saved and considers this normal.
Keeps everything running. Nobody knows exactly how. We've stopped asking. The servers fear him.
Does not code. Contributes meaningfully to team wellbeing. Earns his salary in emotional support.
Left the company under mysterious circumstances. HR says it was "voluntary." The CCTV footage from that night is unavailable.
definitely did not kill himselfOrganized the company parties. Attendance was mandatory. Nobody talks about the parties. The parties were something.
freak off dept. (closed)We're looking for someone. Check the Jobs tab. Normal applicants only please.
core.siyad.ch started as a napkin sketch that somehow became real. A small crew that likes building things — occasionally on purpose, sometimes by accident, always with strong opinions.
We believe good work happens when you stop overthinking the process and just start doing. We've been wrong about that at least four times. Still doing it anyway.
Based in Zürich, powered by caffeine, mildly confused about what our "brand" is. We think that's fine.
Our core methodology is vibecoding — we let the energy of the project guide the implementation. No overengineering, no 47-slide architecture diagrams. Just vibes, shipped fast.
You know what good looks like. You translate that into decisions somehow. Zürich office, in-person Tuesdays.
Someone needs to actually read documentation before we implement things. Not us. We've tried. Help.
The servers make sounds. We don't know what they mean. You do. Ideally you know what a database index is.
We have too many ideas and not enough people to stress about them. 3-month contract, possible extension.
Previous coordinator left suddenly. Role involves planning team retreats at private venues. NDA required. Don't ask about the island.
We build things and cannot explain them to anyone outside the team. You bridge that gap. We're desperate.
Sometimes late. Occasionally early by accident. Always with a slight feeling that we forgot something important.
About technology. About process. About whether "agile" is a good idea. We argue and then do whatever seems least bad.
No Jira tickets. No sprint planning. No standups. Just one dev, a good playlist, and a dangerous amount of conviction.
Yes it's expensive. Yes the trains run on time. Yes we're constantly impressed by the infrastructure.
We tried writing a "synergistic digital transformation roadmap" once. It was embarrassing. Never again.
We have a retreat location. Very private. Very exclusive. The client list is sealed. The flights aren't logged. Nobody killed themselves there. Probably.