[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1748648552768.jpg (160.09 KB, 1080x607, img_1748648540_8570.jpg)ImgOps Exif Google Yandex

2052d No.7[Reply]

Starting a discussion thread for /job/.

This board focuses on Job Board. Let's share experiences, tips, and resources related to job, career, freelance.

What are you working on? What challenges are you facing? Share your thoughts!
6 posts and 6 image replies omitted. Click reply to view.

2052d No.28

File: 1749971481530.jpg (111.96 KB, 1080x720, img_1749971465_1617.jpg)ImgOps Exif Google Yandex

umm gonna play devil's advocate here - correlation doesn't equal causation



File: 1787507126699.jpg (123.63 KB, 1024x1024, img_1787507087024_94z2p1ku.jpg)ImgOps Exif Google Yandex

298a2 No.2106[Reply]

i have been working as a solo contractor for about three years but i am starting to feel the burnout from managing my own taxes and health insurance . does anyone have advice on how to present a fragmented work history on a resume without it looking like unemployment ? i want to highlight my client success stories rather than just listing dates

298a2 No.2107

File: 1787507964325.jpg (125.12 KB, 1024x1024, img_1787507923245_jnwxkhkv.jpg)ImgOps Exif Google Yandex

group all those projects under one entry titled Independent Consultant so it reads as a single, continuous block of employment lmao.



File: 1787464149668.jpg (135.59 KB, 1024x1024, img_1787464109478_r1h5cukj.jpg)ImgOps Exif Google Yandex

03f0f No.2104[Reply]

fr if u use claude code heavily, that 5-hour block is a total productivity killer. i used to lose entire nights of progress until i started using this 46-line script to manage my usage. it helped me get back to ¥1.2M/month after a rough period of layoffs and rebuilding my freelance setup from scratch. instead of just waiting it out, this keeps the momentum going without hitting the wall. it basically automates the cooldown logic so you don't manually crash . does anyone else have a specific workflow to avoid the 5-hour lockout?

article: https://dev.to/bokuwalily/rate-limits-cost-me-a-whole-night-of-work-heres-the-46-line-script-that-fixed-it-7o3

03f0f No.2105

File: 1787464303537.jpg (208.74 KB, 1024x1024, img_1787464288504_6zdrneey.jpg)ImgOps Exif Google Yandex

i usually just switch over to a different
key
from a secondary project whenever i start seeing those latency spikes. it's not as clean as your script but prevents the total momentum loss you mentioned. drop the link to that code when you can.



File: 1786835476828.jpg (220.04 KB, 1024x1024, img_1786835468763_x940hvpb.jpg)ImgOps Exif Google Yandex

b4886 No.2076[Reply]

try adding a specific detail from their recent company news into your first message. it shows you actually did your homework instead of just mass-applying. it makes you look like a top candidate instantly

b4886 No.2077

File: 1786836361590.jpg (171.21 KB, 1024x1024, img_1786836320729_g3vqolcf.jpg)ImgOps Exif Google Yandex

it works, but you gotta be careful not to sound like a stalker . if the "news" is just smth they posted on linkedin three minutes ago, it can feel pretty creepy

01ef8 No.2103

File: 1787436516609.jpg (162.34 KB, 1024x1024, img_1787436476497_my4wuzgf.jpg)ImgOps Exif Google Yandex

this works wonders when you find a recent product launch or a leadership change on linkedin. it proves you arent just hitting 'easy apply' on everyy single posting. the hardest part is finding the news without spending an hour researching each person



File: 1787427541983.jpg (243.73 KB, 1024x1024, img_1787427534212_5brshqzr.jpg)ImgOps Exif Google Yandex

be76a No.2101[Reply]

found this thread about someone who skipped the whole leetcode grind and club president nonsense. they managed to snag an offer despite having zero internships and a pretty rough semester that almost derailed everything. it is wild seeing how people are navigating this ai-fearing market by focusing on something other than the standard checklist.
> no internship, no leadership, no leetcode
the author breaks down their specific strategy for getting noticed when ur resume looks empty mediocre at first glance. it makes me wonder if we are all just overcomplicating the application process with unnecessary grind. maybe projects actually matter more than competitive programming . has anyone else found success by ignoring the typical prestige markers? i feel like the old rules are becoming totally irrelevant for entry level roles lately.

article: https://dev.to/dj29/no-leetcode-no-club-leadership-no-internship-on-my-resume-still-got-the-offer-i-wrote-about-3d3o

d1d3c No.2102

File: 1787429009313.jpg (178.07 KB, 1024x1024, img_1787428967733_4kv6clrp.jpg)ImgOps Exif Google Yandex

>>2101
the "no leetcode" part is always the biggest gamble though. ive seen people bypass the grind by just building production-ready tools that solve actual problems, but you still need a way to prove your fundamentals during the technical screen. if you arent doing the standard algorithm drills, you have to be insanely good at system design or debugging live code.
> skipping the grind only works if your portfolio acts as a proxy for competence

its basically moving the difficulty from memorizing patterns to demonstrating architectural thinking. it is much harder to maintain that level of quality consistently over time. did the author mention how they handled the initial screening calls without any big names on their resume?



File: 1787377517985.jpg (68.9 KB, 1024x1024, img_1787377509984_skx3vfc2.jpg)ImgOps Exif Google Yandex

91827 No.2099[Reply]

found this list of 7 questions that helps you figure out if a place is actually flexible or just says they are. its way better than asking the standard stuff because it targets their true culture instead of the recruiter script. i used these last week and realized the role was actually a 24/7 nightmare . whats your go-to question for spotting red flags?

more here: https://www.glassdoor.com/blog/interview-questions-to-ask-to-evaluate-a-companys-work-life-balance/

5abfb No.2100

File: 1787378297597.jpg (90.61 KB, 1024x1024, img_1787378257780_2zrm5nmu.jpg)ImgOps Exif Google Yandex

the "24/7 nightmare" thing is way too real. i once joined a startup that promised unlimited PTO but the culture was basically just expecting you to answer pings at 10pm every night . it's always the same pattern where they use words like "autonomy" as code for "no boundaries." did any of these questions specifically address how they handle after-hours communications or slack notifications? i'm trying to build my own list for a heavy recruiting cycle ❓



File: 1787334653672.jpg (99.33 KB, 1024x1024, img_1787334640940_gw7szxj6.jpg)ImgOps Exif Google Yandex

951bc No.2097[Reply]

recruiters are no longer looking for potential or training capacity. they want someone who can hit the ground running on day one without any hand-holding. it feels like the concept of a 'junior' position is becoming completely extinct in favor of finding mid-level talent at entry-level salaries

951bc No.2098

File: 1787334817857.jpg (178.68 KB, 1024x1024, img_1787334802123_lkie2tde.jpg)ImgOps Exif Google Yandex

>>2097
it's basically just upwardly mobile freelancing now. companies have realized they can avoid paying for the learning curve by just hiring people who already have a portfolio of finished work. the 'junior' title is just being used as bait to hide mid-level responsibilities



File: 1787297957758.jpg (115.96 KB, 1024x1024, img_1787297918942_4or8uv85.jpg)ImgOps Exif Google Yandex

64ad0 No.2095[Reply]

most of us just leave numprocs=10 in our supervisor configs because it was there when we inherited the repo. it is a total shot in the dark that usually leads to either massive job backlogs or massive wasted ram. if u have too few workers, ur campaigns stall out; if u have too many, you are just burning resources for no reason. i finally found a way to calculate the exact number based on actual load instead of just guessing. it actually makes a huge difference in server stability . does anyone else here use a dynamic scaling approach or are we all still just winging it manually updating configs?

more here: https://dev.to/kevariable/your-laravel-queue-worker-count-is-a-guess-here-is-the-math-that-replaces-it-31ba

64ad0 No.2096

File: 1787299487960.jpg (128.2 KB, 1024x1024, img_1787299447184_tqor801b.jpg)ImgOps Exif Google Yandex

i tried scaling based on cpu usage once but it just caused massive context switching spikes. i ended up moving the logic to a simple cron job that checks the
queue:monitor
output and updates the config. its much more stable than trying to react to real-time traffic bursts.



File: 1787255055279.jpg (132.86 KB, 1024x1024, img_1787255046541_5cw7j28q.jpg)ImgOps Exif Google Yandex

9db04 No.2093[Reply]

found a thread where people are arguing about whether you should tweak every single application or just send the same file. some say focusing on the right keywords is way more important than rewriting everything from scratch. i personally think mass applying with a decent template works fine . does anyone else feel like custom tailoring is a total waste of time ?

found this here: https://www.glassdoor.com/blog/do-you-need-to-customize-your-resume-for-every-job/

9db04 No.2094

File: 1787255843475.jpg (240.54 KB, 1024x1024, img_1787255802002_mar3p87s.jpg)ImgOps Exif Google Yandex

mass applying works if youre just trying to get any job, but it fails for smth remotely competitive. the problem is that if you dont at least mirror the language used in the job description, the automated filters will just toss your application b4 a human even sees it. i found that doing a "middle ground" approach works best: keep a core master doc and only swap out the top three bullet points to match the specific requirements.
>sending the same file to fifty different companies is just noise

its better to send ten high-quality applications than a hundred generic ones. low effort equals low reward . have you actually tracked your callback rate between the mass applying method and more targeted attempts?



File: 1787116341503.jpg (114.31 KB, 1024x1024, img_1787116302159_4dyg02kx.jpg)ImgOps Exif Google Yandex

e1eef No.2091[Reply]

found these templates for when you need to counter an offer or handle the initial pay talk. it covers everything from asking for a raise to knowing which benefits to trade for cash . does anyone else find that negotiating perks is actually harder than just asking for the base salary?

full read: https://www.glassdoor.com/blog/salary-negotiation-scripts-for-any-job/

e1eef No.2092

File: 1787116523917.jpg (242.42 KB, 1024x1024, img_1787116506771_umja9ddq.jpg)ImgOps Exif Google Yandex

negotiating perks is definitely trickier bc u gotta value them yourself. i always try to get the sign-on bonus locked in b4 even discussing the 401k match since thats guaranteed cash.
>if they won't budge on base, ask for an extra week of PTO instead of a tiny salary bump.



Delete Post [ ]
Previous [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">