5 ms·
You need to cut down on the noise. You mention so many things that it's hard to figure out "who you are". Would be nice to have something tangible you worked on
by auganov 10y ago
You need to cut down on the noise. You mention so many things that it's hard to figure out "who you are". Would be nice to have something tangible you worked on that would give you instant credibility.
Wouldn't mention that you're homeless. As long as you can seem similar and likable to the founders you can talk your way into most startup jobs (if that's what you're after). So I'd mostly focus on the image you're projecting.
- amagnasco 10y agoAh... that's really the problem... I've worked on a lot of stuff in a lot of different fields. I could be entry level in writing, editing, research, IT. I could also be junior management at a large nonprofit. Hell, I could be senior management at a small nonprofit. The problem is I have 1 good CV and I highlight my relevance in the cover letter according to the job. I just can't seem to get past the automatic keyword screening, even using jobscan.co
- amagnasco 10y agowould this work? www.overleaf.com/read/zrwcqvgrftvj
- auganov 10y agoWell I don't know much about CVs and that sort of hiring. I was mostly concerned about your own possible confusion about who you'd like to be. You still seem to list a lot of "random" technologies rather than just operating on high level concepts. I.e. just saying you know networking rather than "iptables, firewalls..." [0]. I really don't know if that's a good strategy job-application wise or not, no idea. I was imagining you just finding a way to network with startup people, making some friends and eventually getting a job. Especially since you mention you're willing to do anything [for I assume not so much pay] Applying for jobs is definitely an unlikely path to such an arrangement. [0] and btw mentioning firewalls and iptables separately in that context is werid unto itself
- amagnasco 10y agoSince online applications haven't been working out for me, I'm going to start going in person, so I wrote the CV with that perspective in mind. I don't know about CVs either, at all really. I know the limits of my knowledge and I don't want to oversell myself, I just wanted to clarify what I do and don't know. My experience is heavily linux-based so if someone is looking for a windows expert to debug their registers, that's not me. Sure I can poke around and apply critical thinking to the issue, go online and download a new dat file, reinstall the OS, virus scans or whatever, but I've never debugged a VB app. I don't even know what else is out there in the windowsverse past that point. If tinkering got me nowhere, it's not in the manual, and it's not online, I'll pass it on to someone else. As opposed to linux, OSX, BSD debugging which I can handle fine. Thanks for pointing the firewall thing out, I fixed it.