I Put My Resume in a Couchbase Bucket and Got Hired by the Cluster
When your job application has better replication than your LinkedIn profile.
I was tired of sending PDFs into the void, so I did what any reasonable engineer would do: I stored my resume as a JSON document in a Couchbase bucket and set up a Sync Gateway endpoint for recruiters.
My resume document had nested arrays for skills, an embedded document for each job, and a TTL on my references because honestly, after 90 days they forget who you are anyway.
The recruiters loved it. One said, "I've never seen a candidate with built-in conflict resolution." I told her that was just my experience working in open-plan offices. She didn't laugh. I got the job anyway.
The interview was unusual. They asked me to whiteboard a query. I wrote: SELECT * FROM candidates WHERE years_experience >= 5 AND bullshit_tolerance = "high" AND salary_expectations IS NOT VALUED. They said that last clause was "concerning but relatable."
For the system design round, they asked how I'd build a scalable hiring pipeline. I said: "Store each applicant as a document. Use Eventing to auto-reject anyone who lists 'proficient in Microsoft Word' as a skill. Set up XDCR to replicate promising candidates to the hiring manager's cluster in a different region." They offered me the job on the spot.
My employee profile is now Document #4,721 in the hr_employees collection. I have a primary index and three secondary indexes. My performance reviews are stored as sub-documents so my manager can do partial reads without seeing my salary. The system works perfectly.
The only downside is that my onboarding was an UPSERT. There's no record of my first day. I just... appeared in the collection. Like I was always there. Which, if you think about it, is the most Couchbase way to start a job.