I build the parts that break under load. Collaborative editing that survives two people typing into the same line, search that understands what you meant instead of what you typed, and APIs that fail loudly rather than quietly.
Final year CS at NSUT. Currently a software development intern at Spinny, working on service booking flows and the APIs behind their Voice AI agents.
liveTwo people can type into the same line at the same moment and neither of them loses a word. Ask the chat a question and it answers from 200+ messages in under 100ms, quoting the ones it used. Both of those are harder than they sound, and this is how I got them working.
liveIt reads your resume, then interviews you out loud and follows up on what you actually said. The model was the easy part. The hard part was working out when you had finished talking, because getting that wrong is the difference between a conversation and a form with a microphone.
liveBooking a table looks like CRUD until two people grab the same slot in the same second. This one settles availability at write time against the database, so the loser gets a real reason instead of a double booking, and both of them get an email either way.
The systems half of the syllabus is the part that stuck. Operating systems and networks explain the behaviour you otherwise learn by being surprised in production, and databases explain most of the rest.
Mostly C++. This is the part of my week that has not changed since first year.
Open to SDE roles. If you're building something that has to actually hold up under load, I'd like to hear about it.