3 ms·
I'd say it depends on why. My personal experience is a cto totally lied about a job. I was hired to do ml and ended up being a generic backend dev; nothing I
by x0x0 11y ago
I'd say it depends on why.
My personal experience is a cto totally lied about a job. I was hired to do ml and ended up being a generic backend dev; nothing I worked on required any ml knowledge. I quit after 8 weeks. Oddly enough, the cto -- an early google engineer too -- was very butthurt. He told me I was childish for expecting the job description to match the job; I told him he was a liar and that was the end of that working relationship.
I definitely wouldn't be bothered by someone saying "it wasn't a fit" for a job that lasted under 3 months. In fact, I'd probably think less of you for hanging around in a bad situation for 8 months rather than just saying this isn't working and bailing fast. When I hire, if it isn't working, and we can't make it work, ending the situation quickly rather than dragging things out makes the best of a crummy situation.
- GFK_of_xmaspast 11y agoI used to work for a guy who would advertise a ML/data science job and then tried to convince applicants who made it thru the pipe to take a software engineering role instead. Didn't get a lot of hires that way.
- x0x0 11y agoweird, eh? Must be an Engineering Shortage!
- gaius 11y agoHe told me I was childish for expecting the job description to match the job Seems like he should have been head of marketing, not technology.