Ask and answer with peers.
Each case study had the problem, what I tried that didn't work, and one metric. One interviewer said it was the first portfolio they'd read all the way through. Anyone else cut down and see results?
It went out in March and usage is around 6 percent. My PM says that's normal. I can't tell whether to keep pushing it or move on. What did you do when something you built didn't land?
Then I wrote the list of people I'd message, which I'd been putting off. The second thing that helped was a two-hour daily cap on applications so the search didn't eat every day. Week one was rough. Week two I could actually think.
The docs were out of date. The postmortems were where the real system showed up. I spent two afternoons on the last 40 and the architecture finally made sense. Anyone have a faster way into an unfamiliar system?
I felt awful for a week. Then I found out the interviewer who liked me wrote three paragraphs in the notes. I'm still not sure what to take from that. Has anyone gotten a surprise offer after a rough round?
Right now I say where I studied, then my job, then what I'm looking for. It comes out like a recitation. I've heard present, past, why this role, but I'd like to hear what it sounds like in a real room. Share yours if you have one.
Instead of one number I give a range and name the part I'm least sure about. My lead said it's the first estimate she's trusted from me. I'm still not great at it, but I'm not hiding the unknowns anymore.
Nobody asked for it. A new hire thanked me in standup because my notes on the billing job saved them a day. Short notes beat long wiki pages for me. Does anyone's team actually read what they write?
We picked a random problem and took turns driving. My partner caught my habit of jumping into code before naming the inputs. Now we swap every Thursday. Anyone found a way to find pairs who don't turn it into a monologue?
It logs company, role, date, and one thing I'd change about the application. I didn't expect that last column to matter most. Seeing the same weak spot show up in three rejections is what got me to fix my cover letter. Still a small thing, but it's the one habit that stuck.
The higher number was a team where I'd ramp up alone. The lower one had a senior engineer who spent two hours with me on day one. I think I underrated how much a good first six months pays back in skill. Not saying it's right for everyone. Anyone else trade cash for a better learning curve?
I spent about nine months learning it at night after work. The harder job was translating what I'd done into data language. I rewrote every bullet as 'we tracked X to reduce Y' and my callback rate changed. The portfolio is still rough, but the pivot is real now.
One candidate had a beautiful README and a messy service, and I almost ranked them high. Now we score the three things we asked for and only look at presentation if it stops someone running the thing. Does anyone have a take-home rubric that has held up?
On a question about TCP retries I said 'I don't know, but here's how I'd find out' and walked through how I'd check. The interviewer seemed fine and moved on. I never got the round's feedback, so I can't tell if it cost me. What have you seen actually work?
Before the one-on-one I wrote three things: what I'm already doing at the next level, what's still missing, and when I'd like an answer. She said Q1 and gave me two specifics to work on. Not a guarantee, but it's the first time I haven't walked out feeling vague. Sharing the format in case it helps.
I prepped for test pyramid diagrams and a whiteboard. What they actually asked was how I'd decide a flaky test isn't worth fixing. I froze for a second and then talked through cost versus signal. Got the offer, but I'd prep that question harder next time. What's the one you didn't expect in a…
Nothing broke, which was almost worse. My senior's tip was to write down what 'normal' looks like before the shift so you're comparing against something instead of your gut. I did that on a sticky note. It helped more than I expected. Anyone have a better way to stop spiralling at 3am?
Every Friday I write three lines: what I shipped, who I helped, and what broke and how I fixed it. Nothing fancy. When review season came around I had a folder of evidence instead of a fuzzy memory of the last six months. Tip: put the link to the PR or ticket next to each line so you can find it…
I've heard it's the first line, but I'd love specifics from people who actually screen: Font or layout? Length? Gaps or job hopping? Something else? I'm fixing mine before the next round and would rather take advice from someone who's been on the other side of the table.
Keep a list of every problem you got wrong or needed a hint on. Every Sunday, redo them without looking at anything, and note which ones you can now do in under twenty minutes. It took three weeks before the list started shrinking. Somewhere in there I stopped feeling like I was running on a…
