suzzer, I've had some luck in the morning. I think any weekday in the morning will be fine.

So I can't believe I can't find a solution to this googling, but I want a way to add text notes to photos I take on my iphone, little reminders to make searching easier ("john's birthday dinner"). Ideally the data would be stored as metadata inside the photo file itself, although I don't know if that's possible with jpegs. I suppose some kind of app that stores the note data and auto-correlates it with the picture files would be okay, in a non-proprietary way ideally.

But I've come up empty added so far. Lots of apps let you overlay text onto your photos, but I can't find anything for adding text as metadata....

Never heard of such an app, may be able to do so with an archiving or filing system.

We do that with our drupal sites, adding meta-data that is searchable in the content inventory is a pretty good piece of cheap functionality for things like images, pdfs, other binary files.

Have you looked into imgur? http://imgur.com/blog/2014/07/17/img...es-and-trends/ I think all of the functionality linked there is available to your private image repositories.

the important thing is to keep the flow simple and tied to my ordinary picture taking, which is lazy. so basically i need take pic, and then at one or two clicks max and i'm typing, and them i'm done. uploading is out of the question, even app switching is pushing the limit of "too much work to bother" but i understand that might be necessary so i'm probably ok with that hurdle.

Pretty sure that iOS has an API for manipulating EXIF data in images. I don't know if EXIF allows addition of extra tags. If it does, you might be able to create an index/search based on said tags.

Going back to interviewing stuff. How important do you think a resume is to get hired for a remote job?

I just sent in a pretty bad resume (too long and informal) for what would be considered a technical writing / support job which requires knowledge in a few programming languages.

My skillset is more than adequate for this job but I was declined without reason. If anything it proved to me prior experience, github profiles and open source projects might not actually matter at all when applying for anything but something like a technical co-founder position for a startup.

The resume is both super important and not-important at all. It's the very first hurdle to getting the job, so without a strong resume (how that's defined depends on job/company) you're not getting anywhere. Employers typically get a ton of resumes so you can only spend a very brief amount of time looking at them and you can't spend the time responding to people with an explanation of why you're rejecting them. Hell, half the time the explanation of why you're not continuing isn't even very good.

But once you've gotten a phone screen (or whatever the next step is) your resume becomes almost completely unimportant.

At the resume screening portion I'll typically give GitHub links/Open Source contributions/Personal projects a little credit but not much. The fact that its there is good but I'm not going to spend time investigating and lots of people link to GitHub accounts with absolutely no content - so I don't rate it very highly at this point.

Once I've decided to screen someone I'll dig deeper into these things. At which point seeing real work is a very definite plus and seeing no work (or the standard I've forked 3 public projects and not done anything with them) is a very definite negative.

That's like saying, "I went in for an interview, and instead of shaking the interviewer's hand, I spat in it. Not sure why I didn't get the job."

@shoe lace - To add to what jj posted, if it was contract type work perhaps your rate was too high for what they were looking for. Nothing wrong with that but I suspect it was your resume not having the buzz words/type of experience they were screening for.

The not being able to share specifics line is infuriating to me. Is that just short hand for "I didn't read your resume, go fk yourself"? That's the only thing in my mind that would prevent someone from not being able to give feedback.

Floating by with consulting work is cool and all but I wanted to try and pickup some part time remote work. So far I'm 0/2 with resumes sent in my entire life. I must admit, I certainly give credit to people who send out dozens of resumes and get shot down left and right.

In my mind it's extremely disgusting to be declined with no feedback. I don't mind being rejected but at least tell me why.

The only forks on my github account are pending PRs which get deleted after being merged/closed.

I didn't include rates. Notable buzz words:

ruby on rails, python, golang, nodejs
ansible, docker, coreos, system automation
tons of open source projects (no forks) with massive amounts of documentation

Maybe my problem is my past experience isn't something that can be background checked by a third party? I've only ever done freelance/consulting work. I have no corporate experience.

It's not unusual for someone to be screening dozens of resumes a week. Someone dedicated to the job will be screening hundreds or thousands.

From a purely time point of view, its just not possible and so almost nobody does it.

But even besides that, my point was more that resume screening is not about finding all the good candidates and eliminating all the bad candidates. It's about cleaning up the signal:noise ratio quickly before investing more time interviewing. Everyone understands some bad candidates will get through and some good candidates will be rejected - but that's the price you pay to keep the overall process efficient.

But it also lends to people making quick decisions that aren't super considered. I might scan a person's employment history and think that its vague and unrelated to what I care about. But if I went back and read it a few times maybe I'd see things I missed and change my mind. But its not worth doing that when you're getting a lot of applicants.

Edit: Shoe, if you PM me your resume I'll give you my quick feedback on it. But realistically that's not super useful because it really is dependent on the job/company you're applying for.

no offense, shoe, but the above reaction makes you come off like a baby and explains perfectly why people don't want to give feedback. this is especially true when the real reason has to do with an intuition about the person lacking basic social graces -- the kind of graces that indicate, for example, that the person is able to deal with criticism without getting angry. it may sound silly to you, but "not even knowing how, or not bothering, to turn in a decent looking resume" is absolutely one example of that kind of indicator.

to take another angle, they don't owe you anything. you decided to apply for that job, they decided to reject you. them giving you feedback, at that point, is a waste of their time, especially if they're going through dozens of them, and would be *favor* they are doing you. you should approach it as such, and not like something you are entitled to. a really good analogy here would be asking a girl out, getting rejected, and then being mad that she won't tell you the real reason.

this is a good guess, fwiw. hiring someone who has never held down a job in the field is perceived as a huge risk.

The only feedback you are likely to get on a resume rejection is a canned response stating thanks, we won't be moving forward, and we will keep your resume on file for opportunities that come up in the future. I don't have a problem with that and I wouldn't expect anything else. Companies are not going to critique your resume for you. Job descriptions are wish lists a lot of the time so it is anyone's guess as to what people really are looking for and maybe the companies aren't that clear themselves a lot of the time.

You might consider getting your resume critiqued by someone who could give you valuable feedback. That isn't necessarily easy to find but anyone you decide to work with will cost you money. If it lands you just one gig it might be worth it.

Remote type work I'm guessing gets a lot of responses. Rejections at any level in the hiring process should be viewed as a learning experience. Also, if all companies were really run well there probably wouldn't be much need for contract type work. I have gone into some incredibly screwed up situations as a contractor where I was there to help alleviate the crises. Also I have been hired as a contractor interviewing for a certain position, getting the contract and upon showing up get a completely different assignment than I interviewed for. Stuff happens.

I don't know about that. Years of consulting forced me to have pretty reasonable social graces. I don't have a problem at all speaking with clients and all of my clients so far have had no issues. A lot of them end up being friends in the end.

If I get rejected by a lead I always get a reason because at this point we're talking on the phone or in person and I'm almost always talking with a business owner who isn't reading something off a script while being paid minimum wage and looking at cat pictures for 40% of the day.

I see a job as a business decision that benefits both parties, not a favor. Some corporation hiring me isn't doing me a favor. I'm supplying them value by making their product or customer experience better and in return they pay me money. Both of us win.

Difference of opinion I guess. I see being a freelancer/consultant as holding down a job. If anything it's more demanding because I can't wake up, goto work, screw around for 6 hours, work for about 30 minutes and get paid at the end of the week.

I have to remain super motivated and often put in really long days.

1. It's not personal, it's business.

2. Send out a lot more resumes, then it won't bother you so much to get shot down. I think i've seen it estimated that you'll usually get 1 interview for every 20 resumes you send. So, you've got a fair amount of work to do still.

Man, you live for talking **** on people itt, huh?

This sounds atypical

i didn't say you didn't have them, i said that's how it may have been perceived.

not what i said. i said that after deciding they weren't going to hire you, spending time to explain why was the favor.

who are you arguing with? i'm not saying you don't work hard or what you do isn't hard. i'm saying, for the perspective of most hiring managers, it's a risk. i know that for a fact. you may think they are *wrong*, but that't not relevant.

if the people had given you feedback, and you disagreed with it, would you have gotten defensive and argued back? if so, that's probably the kind of trait that comes across in other ways when you speak to them on the phone or in person, and would further explain a reluctance to answer the question. probably not relevant in this case, since i think you said it was only a resume, but worth noting anyway.

EDIT: also, i get that poker forum discussion is a totally different context from an interview, and that what you do here is not necessarily indicative of anything in the real world.

seriously, not at all, and it makes me feel bad that it would come across that way.

i have tons of respect for shoe, and think he's a really smart guy, and think that's come across over the history of our posts (i hope so, anyway). but that also means i'm going to call it like i see it, especially when the post in question is about his anger at people not taking the time to give him honest feedback.

You shouldn't feel bad in my view, your post came across as being totally constructive.

We give a personal rejection email to every candidate that gets to our phone screening stage. At that point they've invested a bit more time and we feel we owe them an actual response.

Shoe Lace,

You can't take something like this personally. Your resume is the only thing that they know about you. And this was for a technical writing position? Why do you think a poorly written resume would be good enough for a *writing* position? If you didn't tailor your resume for the job in question and you're not an elite fit for the job to start with, it's unlikely that your resume would attract much attention. Why care so little about the job that you send out a poor resume, only to end up caring so much that you're complaining that you're rejected without reason?

It's like the difference between a date that set up by mutual friends and a random girl at a club (or an online dating site) that you're hitting on.

I think sending a bad resume to a technical writing position is about as far as we have to go investigating this mystery.