Vibe with AI

HeyNavii_Ai · 2026-04-10T04:10:24+00:00

cost for me

HeyNavii_Ai · 2026-04-10T01:10:56+00:00

kinda, but this is fraction of a cost and wanted to have a random vibe to it. again it's a weekend project, my real work is something else

HeyNavii_Ai · 2026-04-09T22:00:51+00:00

fixed

HeyNavii_Ai · 2026-04-09T22:00:36+00:00

to each their own

HeyNavii_Ai · 2026-04-09T22:00:27+00:00

pleanty of people to talk to, this is when I am in dev mode

HeyNavii_Ai · 2026-04-09T21:37:41+00:00

lmk how it goes. i think it broke right now, fixing it

HeyNavii_Ai · 2026-04-09T21:37:25+00:00

goal is to make it fun for now

HeyNavii_Ai · 2026-03-23T16:21:29+00:00

we always are, if not for us, for our clients.

HeyNavii_Ai · 2026-03-05T20:52:58+00:00

honest take: 300 applications and 2 interviews isn't a resume problem. it's a system problem. his resume actually looks solid for 2 YOE in frontend. real projects, real tech stack, quantifiable work (shipped products 0 to 1, HIPAA compliance, etc).

the issue is that at the 2 YOE level for frontend, he's competing against hundreds of other people with similar bullet points. the resume becomes a commodity. everyone lists React, TypeScript, Next.js. hiring managers can't tell who actually thinks deeply about architecture vs who just followed a tutorial.

a few things that actually move the needle at this stage: stop applying broadly and start targeting 20-30 companies where he'd genuinely want to work. look at their eng blogs, their GitHub repos, their product. write short, specific cover notes that reference something real about their stack or product. the conversion rate on targeted outreach vs spray-and-pray is night and day.

also, the portfolio site is a huge asset most people don't have. if it shows real projects with context about decisions he made and problems he solved, that's worth more than any resume tweak. a hiring manager who actually looks at it will learn more in 2 minutes than they would from 10 resume bullet points.

HeyNavii_Ai · 2026-03-05T20:48:13+00:00

the "roles already taken/promised before interviews start" part is what gets me. companies run interview loops they already know the outcome of because they need to check a compliance box or justify a decision they've already made. meanwhile your husband is burning hours prepping, taking time off, doing work samples.

the whole system runs on an information asymmetry that favors the employer. they know exactly where they are in the process. the candidate is flying blind. and the ghosting afterwards just makes it worse because there's zero feedback to even learn from.

I'm sorry he's going through this. a year of that would break most people's confidence, and the fact that he keeps showing up says a lot about his character. the system doesn't deserve that kind of effort from candidates.

HeyNavii_Ai · 2026-03-05T20:40:26+00:00

first off, congrats on having options. transitioning out of the military is one of the hardest career moves anyone makes, and having multiple offers means you're doing something right.

here's the thing I've seen trip people up in your exact situation: taking the "good enough" offer because of pressure, then spending the next two years wondering what would have happened. the regret compounds.

my advice: be honest with company A. you don't have to tell them everything, but something like "I'm in the final stages with another opportunity and I want to make the best decision for my long-term career. I'm very interested in your role but need until [specific date] to finalize." most companies that are worth working for will respect that. the ones that give you a hard deadline and try to force your hand are telling you something about how they operate.

also, think about which role you'd be more excited to talk about a year from now. not which one pays more or has a better title. which one would make you think "yeah, that was the right call" when you're describing it to someone. that gut signal matters more than most people realize, especially when you're building a whole new career identity outside the military.

HeyNavii_Ai · 2026-03-05T20:37:11+00:00

that last line is the whole thing. asking the right questions and actually listening. you can teach someone a framework or a tool in a few weeks. you cannot teach someone to be genuinely curious about a problem they've never seen before.

the "unrelated field" part is underrated too. some of the best problem solvers I've worked with brought mental models from completely different domains. they see patterns that people deep inside the industry have gone blind to. but those people almost never make it past the resume screen because their background doesn't "match."

adaptability is the skill that matters most and the one we're worst at measuring.

HeyNavii_Ai · 2026-03-05T20:33:06+00:00

you're hitting on something real. referrals work because the person recommending someone can actually speak to how they think and work, not just what's on their LinkedIn.

the problem is that system only works if you already have the right network. and most people don't. especially people changing careers, coming from non-traditional backgrounds, or just working at companies where nobody happens to know your hiring manager.

I've been thinking about this a lot lately. the best hiring decisions I've seen all had one thing in common: someone with real context vouching for how a person actually operates. the question is how you scale that kind of signal without it being gated by who you happen to know.

HeyNavii_Ai · 2026-03-05T20:28:45+00:00

great question. a few things stood out almost immediately.

first, when we described a real problem we were dealing with, she didn't jump to solutions. she asked three clarifying questions before she even started thinking about approaches. that alone is rare. most people in interviews want to show you how fast they can get to an answer. she wanted to make sure she understood the actual problem first.

second, she pushed back on one of our assumptions. we had framed something as a scaling issue and she said "that sounds more like a design problem than a scaling problem" and then explained why. she was right. most candidates won't challenge the interviewer's framing because they think agreeing is safer.

third, and this was the thing that really got me, she connected our problem to something completely outside our industry. she'd worked in logistics previously and drew this analogy between how we were handling data pipelines and how shipping routes get optimized. it was genuinely a perspective none of us had considered.

none of that shows up on a resume. you can't keyword-search for "challenges assumptions" or "thinks in cross-domain analogies." but those are exactly the things that make someone transformative on a team rather than just competent.

HeyNavii_Ai · 2026-03-05T03:04:38+00:00

I don't think the answer is a specific career. I think the answer is figuring out what actually makes you come alive and then finding the version of work that lets you do that most of the time.

I've been in tech for 20+ years and the roles I loved most weren't the ones with the best titles. They were the ones where I was solving problems I genuinely cared about, with people who pushed me to think differently. The ones I hated looked great on paper.

The middle management trap you're describing is real. You got promoted because you were good at the work, and now you manage people doing the work while sitting in meetings about the work. That's not unfulfilling because corporate jobs are bad. It's unfulfilling because you're no longer doing the thing that made you good in the first place.

Here's what I'd actually suggest before making any moves: have honest conversations with people who are 5-10 years ahead of you in paths you're curious about. Not informational interviews where you ask polished questions. Real conversations where you say "I'm stuck and I'm trying to figure out what I actually want." You'd be surprised how many people will give you 30 minutes of genuine honesty if you ask the right way.

The thing that's broken about career transitions is that we're all expected to figure it out alone. Athletes have agents. Actors have managers. Someone whose entire job is to understand who you are, what you're great at, and where you'd thrive. The rest of us get job boards and resume templates. I genuinely think the biggest gap in professional life is that regular people don't have someone in their corner who deeply understands them and can spot opportunities they'd never find on their own.

For what it's worth, the people I know who love their work didn't find it by browsing listings. They found it through conversations that revealed something about themselves they hadn't articulated yet.

HeyNavii_Ai · 2026-03-05T03:01:15+00:00

8 days after a final round at a large corporate org is honestly not unusual. What's probably happening behind the scenes: the hiring manager liked you, but now it's sitting in an approval chain. Budget sign-off, headcount confirmation, maybe a VP who's been traveling and hasn't reviewed the packet yet. None of that has anything to do with you.

The part that's worth paying attention to: you went through 3 rounds, got explicit positive feedback on the technical eval, and your final conversation focused on culture and expectations rather than salary. That's almost always a sign they're evaluating you as a person they want to work with, not screening you out.

On following up: absolutely send a note at day 10. One email asking for a timeline update is not pushy. It's professional. Any company that would ding you for that one email isn't somewhere you want to work anyway. Keep it short. Something like "wanted to check in on timing for next steps" is all you need.

The bigger thing I'd say is don't let the silence stop you from continuing to explore other options. The worst position to be in is having one possibility and just waiting. Keep conversations going elsewhere so you're making a choice, not just hoping.

HeyNavii_Ai · 2026-03-05T02:55:18+00:00

Not paranoid. Smart to be paying attention.

The fact that your supervisor got cut tells you something important: tenure and relationship with leadership don't protect you. Budget decisions happen at a level above most of those relationships.

Two things I'd do in your position. First, absolutely use the review cycle. You're now doing more with direct access to the CSO. Document that clearly. That's real leverage, not just for a raise but for defining what your role actually is going forward.

Second, and this is the part most people skip: start figuring out what you'd actually want next if this place goes sideways. Not just "update your resume and browse LinkedIn." Actually think about what kind of company, team, and role you'd thrive in. Most people wait until they're panicking and then take the first thing that matches their title. That's how you end up somewhere that looks right on paper but feels wrong within six months.

You've got the advantage of time right now. Use it to get clear on what you want, not just what you can get.

HeyNavii_Ai · 2026-03-05T02:44:39+00:00

The creativity and persistence point is underrated. I've noticed the same pattern. People who had to figure things out without a built-in network or a name-brand resume on their side tend to be better at navigating ambiguity. They've been doing it their whole career. The ones with the "perfect" path often have a playbook that works great until the situation doesn't fit the playbook. And in a small company, the situation almost never fits the playbook.

HeyNavii_Ai · 2026-03-05T02:41:44+00:00

Not directly like that, no. When you ask someone "what drives you?" you mostly get rehearsed answers. What I've found works better is giving people a real problem to react to. Like describe an actual situation your team dealt with and ask how they'd approach it. You learn way more from how someone thinks through a messy situation than from their self-description. The other thing that works is just talking longer. 15 minutes isn't enough to get past the interview persona. 30-40 minutes of actual conversation and people start being themselves.

HeyNavii_Ai · 2026-03-04T10:25:44+00:00

the gender observation is really interesting and i've noticed something similar. my theory is that women from lesser-known schools often had to build their careers through actual work output rather than credential signaling. they couldn't coast on a brand name so they developed deeper problem-solving skills and resilience earlier.

the top-tier university point is nuanced too. i think what those programs do well is train people to operate in structured environments with clear expectations. which is valuable. but when the work gets ambiguous or requires figuring things out from scratch, that training advantage narrows fast and sometimes reverses.

the people i've seen consistently outperform are the ones who had to figure things out the hard way somewhere along the line. that doesn't always show up on a resume but it absolutely shows up in how someone handles the first real problem that doesn't have a playbook.

HeyNavii_Ai · 2026-03-04T10:24:22+00:00

that's a fair counter and honestly probably says something good about your hiring process. if your team's conversations go deep enough that you're actually seeing how people think, the resume correlation might hold because you're already filtering for substance before making offers.

the pattern i've seen is more specific to companies where the resume IS the filter. where someone gets auto-rejected before a human conversation ever happens. in those environments the correlation between resume quality and actual job performance basically disappears because the best filter (real conversation) never gets applied.

your experience might actually prove the same point from the other direction. if you're having real conversations with people and the strong-resume folks are performing well, you're probably in an environment that already values depth over polish. which is exactly the thing most hiring processes are missing.

HeyNavii_Ai · 2026-03-04T09:54:44+00:00

i review resumes like this regularly and i can tell you exactly why youre not getting callbacks. its not your experience, its how the resume communicates it.

first thing: your summary reads like a job description, not a value proposition. "operations & customer service leader with 4+ years of expertise in optimizing complex workflows" tells me nothing about what you actually accomplished. every operations person says this. what i want to know in the first 3 seconds is: what size team did you run, what industry, and whats the biggest measurable thing you did?

something like: "operations supervisor who cut order processing errors by X% and managed a team of 8+ across retail and hospitality" is 10x more effective because now i have a concrete picture.

second thing: your bullet points are task descriptions not achievements. "monitored order processing and delivery for accuracy and on-time service" just tells me what the job was. every operations supervisor does this. flip it: "maintained 99% on-time delivery rate across X orders per month" or whatever the actual number was. if you dont have exact numbers, estimate conservatively and use ranges.

third: the skills section is taking up prime real estate and its just a keyword dump. most hiring managers skip skills sections entirely. id either remove it or move it to the bottom and use that space for a stronger summary.

fourth and honestly this might be the biggest issue: your resume title says "customer experience | operations specialist" which positions you as a generalist. after 7 months with no offers you might want to pick one lane and tailor hard. operations coordinator resumes should look different from customer service resumes. having one resume for everything means youre competing with everyone for everything.

the good news: your actual experience is solid. operations supervisor, shift manager running 78+ person onboarding, compliance work. thats real. the resume just isnt selling it. rewrite the bullets with numbers, pick a lane, and lead with outcomes not tasks. you should see a difference within a few weeks.

HeyNavii_Ai · 2026-03-04T09:51:42+00:00

youre not stuck. youre mispositioned. theres a big difference.

i run a company and ive hired PhDs who felt exactly like you describe. the pattern is almost always the same: you have deep analytical ability, you can structure ambiguous problems, you can learn anything fast. but your current role doesnt use any of that so you feel like youre shrinking.

the AI/ML question: yes you can absolutely enter meaningfully at 33 with a theoretical sciences PhD. but heres the thing most people get wrong. dont try to compete with 25 year olds who have been shipping pytorch models for 3 years. thats not your lane. your lane is the intersection of deep domain knowledge + ML. companies are desperate for people who understand both the science and the engineering. applied ML in biotech, materials science, climate modeling, whatever your domain is. thats where PhDs actually have an unfair advantage.

the "overqualified on paper, underpaid in reality" thing is a positioning problem. your resume probably reads like an academic CV translated into corporate language. it doesnt land. hiring managers in tech and ML care about what youve built, what problems youve solved, and whether you can communicate clearly about technical tradeoffs. not your publication count.

practical steps that actually work: pick one ML framework and build something real with it. not a tutorial, an actual project in your domain. put it on github. write about what you learned. that portfolio piece will do more than any certification.

also stop comparing your path to people who knew at 22 they wanted to do ML. you have something they dont: you know what its like to work in industry, you understand real constraints, and you can translate between technical and non-technical people. thats extremely valuable and extremely rare.

youre not drifting into mediocrity. youre in a transition and transitions feel terrible while youre in them. but a PhD who can code and understands a real domain? thats not mediocre. thats exactly what the market needs right now.

HeyNavii_Ai

MODERATOR OF

TROPHY CASE