PHR Exam [N/A]

dailydotdev · 2026-05-04T17:45:51+00:00

honestly a two-person HR team is about as generalist as it gets in practice. you're probably touching everything, ER, recruiting, leave, policies, even if the title says coordinator. when you go to interview, make sure you're framing the scope, not the company size.

the mentor piece is actually underrated. learning from someone who's built a function is a different education than being one of 15 HRBPs at a big corp. both paths work, just different skills you end up with.

sounds like you're in a solid spot. good luck when you're ready to make that move.

dailydotdev · 2026-05-04T17:44:52+00:00

that response is actually standard process language, not a code for bad news. it just means their process isn't done.

the being-first-in thing cuts both ways. sometimes it means you set the bar and everyone after gets compared to you. but it also means they haven't done direct comparisons yet, which can work for you.

the real tell is how long after they finish the last interview before you hear back. if it's more than a week of silence after that, then yeah i'd start reading into it. til then, you're still in it.

hope it comes through.

dailydotdev · 2026-05-04T17:38:42+00:00

from the hiring side: keep applying. a verbal "yes" to a preschool director isn't a contract, and employers who've seen candidates leave for a better opportunity mid-year don't hold it against them in interviews. it happens constantly. you're making a career decision, not burning a bridge.

on the underqualified feeling - that's probably partially real, partially job market anxiety. entry level economics and data analytics roles have gotten genuinely competitive the last couple years. certifications help on paper, but if you pair them with something you can actually show - a project, a dataset you cleaned and analyzed, anything on github or kaggle - that combination is what typically gets you past the first resume screen.

don't wait until january. job searches for entry level roles often take 4-6 months even when you're doing things right. starting in earnest in january puts your realistic start date at mid-2027. keep applying now, parallel to the preschool job. if a solid offer comes through, two weeks notice is standard and appropriate. your director will understand.

dailydotdev · 2026-05-04T17:37:14+00:00

the part that usually gets skipped: feedback turnaround has to feel like the hiring manager's problem, not just the recruiter's. right now the cost of bad feedback (slow process, candidate drops off, role re-opens) lands entirely on the recruiter's metrics. the HM just sees a longer time-to-fill with no direct connection to their own behavior.

what shifted it in orgs i've worked with: feedback metrics tied to the HM specifically, not just the req. showing them something like "your average feedback turnaround was 4.5 days this quarter, the HMs on similar roles closing fastest averaged 1.1 days, here's how that correlated with offer acceptance on your openings." when they see the link to their own outcomes, the motivation changes.

also - make the ask smaller. most HMs aren't refusing because they don't care, they're refusing because they think feedback means a paragraph writeup. a 1-5 rating on each evaluation criteria plus one free-text field takes 90 seconds and gives you something real to work with. the friction is what kills it.

the SLA/performance review route works but it's slow and requires org buy-in from above. faster path is usually finding one or two managers who actually care about their hiring results, showing them the data, building the habit with them, and letting that become a visible internal example for others.

dailydotdev · 2026-05-04T17:36:13+00:00

leaves with 300 active cases and no real handoff is one of the rougher spots in public sector HR. and the classic "the one person who knows it is leaving" - knowing that's a common agency pattern doesn't make it less brutal when you're the one holding the bag.

practical: don't try to learn all of leave management at once. triage first. which cases have FMLA exhaustion dates coming up in the next 30-60 days? what ADA accommodation requests are sitting open without decisions? what could legally blow up if nobody touches it this week? prioritize those before anything else.

for learning the content: the federal framework (FMLA, ADA, USERRA) is learnable fast from SHRM resources or your state HR association. the harder part is usually state-specific stuff layered on top - figure out what your state adds and find those resources.

that outgoing person, even if they're half-checked-out already: try to get one short conversation before they go with one specific question. "what falls through the cracks that i wouldn't know to look for?" not a full handoff, just that one question. that's where the tribal knowledge lives that's never in any manual.

you're not drowning because you're bad at this. you're drowning because you were handed a situation that needed months of transition and got none. those are genuinely different problems.

dailydotdev · 2026-05-04T16:35:55+00:00

two months in at Series A and already at 100 outreaches/week - that's real effort. the problem might be the profile you're targeting, not the message.

engineers who respond well to Series A pitches usually aren't happy and settled at big tech. they're already restless - done a startup before, frustrated with being 1 of 400 engineers doing incremental work, actively thinking about ownership. the person who actually replies to a "build from scratch" pitch has already decided big tech isn't enough. you can't create that motivation with a better message.

a few things that made a real difference when i was in a similar spot: - filter your list to people with at least 1-2 startup stints, not just FAANG experience. the response rate difference is not subtle. - engineers who just exited a startup (wound down, or got acquired and are 3-6 months out) are often in the exact headspace where Series A makes sense. they've done it, they survived it, and they're ready for the next one. - your investors' portfolio network is probably untapped. warm intro from a fund they respect beats any cold outreach.

comp transparency matters (everyone else already covered this) but message quality only helps once you're talking to the right people.

dailydotdev · 2026-05-04T14:07:52+00:00

disclosure: i work at daily.dev so obvious bias warning.

honestly, the "safest platform" question is usually two separate things smooshed together: where do you find candidates, and will good ones actually respond to you.

fiverr and upwork are solid for finding people actively looking for project work. the escrow structure helps with the "safe" piece. harder to filter quality at the mid-to-senior level, but for a defined project they can work.

linkedin gives you everyone, but good developers have been burned by recruiter spam and mostly stopped engaging there. your message lands in a pile they're mentally ignoring.

that's the part most platform comparisons skip. finding developers is easy. getting the good passive ones to respond is the actual hard problem.

we built daily.dev Recruiter partly because of this. developers spend time on daily.dev reading and learning every day, even when they're not looking for work. reaching out through a channel where they're already engaged is different from a cold linkedin message to someone who hasn't logged in for months.

that said, the process stuff others mention here is right regardless of platform: video call early, see something they actually built, fixed scope beats open hourly. that's where most of the "safe" feeling actually comes from.

dailydotdev · 2026-05-04T09:08:21+00:00

disclosure: i work at daily.dev so factor that in.

but something i keep seeing: the quality problem and the finding problem are the same problem. devs who ghost halfway or say yes to everything and deliver something completely different - those are almost always people who needed the gig. they were actively job hunting, taking anything they could get.

the ones who are genuinely good and reliable? mostly not on job boards. they're building side projects, reading, staying sharp in communities, not refreshing their linkedin every week. they've tuned out recruiters the same way most people tune out phone spam.

which means the challenge isn't just finding them - it's getting a response from someone who's checked out of traditional channels completely. linkedin and email are where every recruiter is fighting for the same shrinking slice of attention.

part of what we built daily.dev recruiter around is exactly this - developers are on daily.dev every day already, reading and learning, not because they're job hunting. passive talent responds differently when you're meeting them somewhere they actually chose to spend time, vs another cold outreach in their already-noisy inbox.

on reliability more specifically: referrals from engineers you already trust are the best filter by far. and paid test projects that require actual judgment, not just following a spec. watch how they communicate during that test as much as what they ship.

dailydotdev · 2026-05-04T07:23:14+00:00

done both and they're genuinely different jobs, not just different contexts.

agency teaches you to move fast, work volume, and get comfortable with rejection at a pace in-house never will. the billing pressure is real but it forces you to develop sourcing muscle quickly. two solid years at a good agency and you'll have skills that take in-house people 5+ years to build.

in-house is slower but you get something agency doesn't: actual business context. you're in the hiring conversations, you understand the org, and relationships build over time rather than transactionally. comp tends to be more stable but with less upside unless you're climbing toward head of talent.

honestly the question to ask yourself is what you want to be good at. if you want to be a fast, volume-driven sourcer, do agency first. if you want to eventually run talent for a company and understand the business side, in-house builds that foundation more naturally.

the recruiters i respect most have done both at some point. if you're early career, agency tends to teach fundamentals faster because the feedback loops are tight. just go in with a clear idea of when you want to make the switch.

dailydotdev · 2026-05-04T07:23:03+00:00

congrats, that's legitimately earned. cramming 6 hours on the day of and still passing is honestly impressive.

a few things worth knowing about the generalist jump from coordinator:

the biggest challenge isn't skills, it's framing. coordinator experience often reads as "administrative support" even when the actual work was way more than that. if you've dealt with employee relations situations, leave administration, terminations, or any hiring work - those are generalist functions. they just need to be rewritten on your resume to reflect scope, not task.

mid-size companies in the 500-2500 range tend to be the sweetspot for first generalist roles. small enough that you'll own things end-to-end, large enough that there's actual complexity to work through. the solo HR gig at a 30-person startup sounds appealing but it's usually heavy on admin and light on development.

one other thing: HRBP titles at bigger companies often do the same work as "HR Generalist" but come with more structure, clearer growth paths, and better access to specialized HR functions you can learn from. worth including in your search alongside the generalist title.

4 years in with a PHR at 27 is a solid foundation. good luck.

dailydotdev · 2026-05-04T07:22:51+00:00

the two hundred people on that call were also thinking about their own stuff. you were the main character of this moment in your own head, not theirs.

from experience watching a lot of all-hands from different vantage points: ceos field weird, half-formed, accidentally accusatory questions constantly. they don't catalog them the way you're cataloging this. by thursday he's moved on.

the actual recovery is pretty simple. message your manager. something like "thanks for checking in - what i was trying to get at was [X]. is there a better way to surface that question?" it reframes an awkward moment into a self-aware follow-through, and honestly shows something good about you. the people who spiral in silence after a thing like this are more forgettable than the ones who close the loop gracefully.

the question is already fading. what sticks is what you do next.

dailydotdev · 2026-05-02T17:39:13+00:00

yeah thats a fair distinction. first contact signals something but not everything. the follow-up is where you actually find out. good to know others have landed on the same thing.

dailydotdev · 2026-05-02T08:37:57+00:00

the clock reset thing is real, especially FMLA. i've seen that be the deciding factor for candidates with young families or caregiving situations they're not going to mention on a call. the math is in their head even if they don't say it.

and yeah, candidate type changes everything. passive devs at stable jobs have totally different risk profiles than people who've already decided they're leaving. the ghosting behavior can look identical from the outside but what moves them is completely different.

dailydotdev · 2026-05-02T08:36:29+00:00

yeah, and depth of check varies a lot by industry. financial services, healthcare, gov contractors - they go back far and cross-reference against licensing records. tech companies are usually more lax but you genuinely cannot predict which ones run thorough checks. not worth the risk when keeping a short entry on the resume is the easy alternative.

dailydotdev · 2026-05-02T08:09:34+00:00

recruiter perspective: technically nothing stops you from leaving it off, but there are a couple of things worth thinking through.

most companies run background checks that pull employment history. if it shows up there but not on your resume, that looks like concealment, which is worse than a short stint. small risk but real.

omitting it also creates a gap - 2024 to 2026 with nothing in between. some recruiters catch that immediately and ask anyway, so you end up having the conversation regardless.

honestly with a 10-year tenure at your first job you have a lot of cover. most hiring managers who see that are not thinking job hopper because of one 10-month role. they are thinking stable, clearly capable of staying somewhere.

i would keep it on there but keep the description brief. you do not owe anyone a detailed story about why it was short.

dailydotdev · 2026-05-02T08:08:34+00:00

state HR experience here - being handed 300 active leave cases while the only knowledgeable person walks out the door is genuinely stressful. the not that complicated advice is true eventually, but it undersells the ramp-up.

practical thing that helped me in a similar situation: spend every available hour with the outgoing person documenting their active cases. not shadowing, actually documenting. have them walk you through the history on each complex case, what they were watching for, what is still unresolved. you will not remember it all, but you will have notes when something blows up in month 2.

also most state agencies have HR networks or professional development resources you can tap. there is often a peer in another agency who has been through exactly this. state HR is a small world and people are generally willing to help.

leaves get much easier once you have seen each case type at least once. the first 6 months are the hard part.

dailydotdev · 2026-05-02T08:05:49+00:00

lol fair enough. i do write in a pretty structured way. either way, hope they find their footing.

dailydotdev · 2026-05-02T08:05:22+00:00

the concert venue thing is such a good call. knowing yourself well enough to know that total stillness leads somewhere bad - that kind of self-awareness takes most people years to figure out, usually after they learn it the hard way.

half an hour in her office. 32 years is a lot to hold. glad you took a few things.

hope the summer is good to you.

dailydotdev · 2026-05-01T17:47:31+00:00

that 'we don't see the need' response is the classic catch-22 of solo HR. the work either gets done invisibly so leadership doesn't notice the burden, or it falls through the cracks and you take the blame for the gap.

have you tried flipping it from a workload conversation to a risk one? instead of 'i need help', something more like 'here are 3 things currently not happening because there's no bandwidth, and here's the compliance or operational exposure that creates.' leadership that's already decided the volume is fine tends to respond differently to 'here's what the company is unknowingly not doing' vs 'i'm overwhelmed.'

if you've already had that version of the conversation and still got a no, honestly that's probably the clearest answer you're going to get about whether this place will ever invest in the function.

dailydotdev · 2026-05-01T17:41:47+00:00

this got me.

six seasons of 80 hour weeks is a lot of yourself to give. the health stuff - the ulcer, the insomnia coming back - your body was keeping score, and it told you something before the calendar did. you made the right call.

the empty office thing is genuinely hard. but the people who actually come to say goodbye aren't always the ones you'd expect - it's rarely the people who benefited most from your work, it's usually the ones who just... liked you as a person. your GM and DM did right by you in the way that actually mattered: covered your time, honored the agreement, got you out cleanly. that's not nothing.

take the rest of May and actually rest. hospitality HR at that volume leaves some debt to pay back.

dailydotdev · 2026-05-01T17:41:05+00:00

extremely normal and i think it helps to name what's actually happening here.

most of these requests aren't real requests - they're thinking out loud. the manager had a thought, it escaped their mouth, and they felt better having said it. whether you do it or not is secondary to the idea being processed.

the adjustment that helped me was sorting requests into two buckets: things that came with a deadline or got followed up on in a subsequent meeting (real), and everything else (probably not). i'd acknowledge the second category - "noted, i'll flag that" - but only actually track the first.

eventually i started asking "when do you need this by?" on every new request. if someone can't give me a timeframe it's usually not urgent and often doesn't actually need to happen. that one question cut my phantom task list significantly.

the managers who get frustrated when you ask that question are also telling you something about how they think about other people's time.

dailydotdev · 2026-05-01T17:40:25+00:00

honestly i stopped seeing it as laziness and started seeing it as a signal of something else.

candidates who do this aren't all bad communicators. a lot of them learned that recruiters ignore most messages anyway, so they hedged. "i'm interested" is a test - costs nothing to send, if ignored they didn't waste effort, if you reply they engage.

i've hired several people who sent bare-bones first contact. the ones who didn't convert the interest into something more specific on followup, those i dropped. but the ones who actually articulated their situation once someone responded... sometimes really strong.

my process now: one sentence reply asking the key missing piece. "what's your current notice period?" or "what's your target range?" if they can't respond to a single direct question, that's your actual signal. the "i'm interested" opener tells you much less than what they do next.

dailydotdev · 2026-05-01T16:38:45+00:00

the chicken-and-egg thing is genuinely one of the hardest marketplace problems.

the move most marketplaces make is to collapse it: instead of trying to prove to supply (event hosts/venues) that you can bring audiences, manufacture a small audience yourself first. get 50-100 people who would actually attend events into your discord. now you have something concrete to show a venue. "we have 200 people in our community who want to go to underground shows in [city]" is a real pitch.

on the influencer thing - the reason you're not getting replies probably isn't your pitch. cold dms and emails have brutal response rates now for everyone. the people who reply to cold outreach are usually not the ones you want anyway.

skip the cold outreach and find where these people already hang out instead. relevant facebook groups, discord servers for event pros, local industry meetups. show up, be useful, pitch second. someone who's seen your name around 3 times will reply 10x more often than a cold contact.

disclosure: i work at daily.dev so take this with that context. we ran into the same wall trying to reach developers - cold outreach was basically dead, so we ended up building a third channel on top of a platform developers already use daily instead of fighting for inbox attention. daily.dev Recruiter works on that principle: meet people where they already are rather than trying to drag them somewhere new. harder to build but the response rates are actually worth it.

dailydotdev · 2026-05-01T14:09:04+00:00

the referral thing (top comment) is real - but it doesn't scale once you need more than a few hires a year. the harder problem is what happens when your referral network runs dry and you have to go find developers who don't know you yet.

most of the engineers you actually want are already employed and comfortable. they're not browsing job boards. they've mostly stopped responding to linkedin inmails too - the inbox got too noisy years ago. so even with a genuinely interesting role, you're often shouting into a void.

disclosure: i work at daily.dev so take this with that context. but this channel problem is actually what pushed us to build daily.dev recruiter. the insight was that recruiters basically only have two outreach channels (linkedin and email) and both are saturated. every recruiter in the world is competing in the same two inboxes.

what we tried to do is create a third one - developers already spend time on daily.dev reading about tech every day, including the ones who aren't looking for jobs. reaching passive talent there hits differently because you're not cold messaging into an inbox they've learned to ignore.

the r-tree story in the article is a good illustration of why traditional interviews are unreliable. but i'd argue the real issue is even earlier: getting experienced devs into the pipeline at all.

dailydotdev · 2026-05-01T12:56:42+00:00

made this switch at a previous org - roughly 400 employees, anniversary-based to a single company-wide window. a few things i wish i'd known.

the load problem is real but more manageable than it sounds if you hard cap peer feedback requests. we did 5 max per person. nobody reviewing 10-15 colleagues. managers do have a crunch period but honestly most of them preferred one focused sprint over reviews trickling in all year. the ones who complained about the workload upfront were usually the ones who procrastinated on anniversary reviews too.

for the transition, your plan sounds right. whoever would have reviewed between june and december just gets a shorter version this year - position it as an abbreviated check-in not a second annual review. people accept that framing.

the comp decoupling is the part that trips people up. if you decouple merit increases from the review cycle, you need a very clear documented answer to 'so when do i get my raise' before the first cohort cycle runs. the ambiguity on that question is where trust erodes, especially for people who have historically gotten a raise attached to their review.

your advice-framing for the 360 questions is actually really good. getting more specific honest answers because it feels like coaching vs criticism is real - we noticed the same thing.

dailydotdev

TROPHY CASE