You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
1@user53508 If you're in the trial period you can leave anytime you want without it impacting on future applications. It's what trial periods are for. I've edited my answer to take that into account.– Kilisi ♦Commented Jul 3, 2016 at 18:55
-
2"under a year is a bit suspect, a year is not too bad, 18 months to 2 years is fine." - can you quote any research on this? For me it's like the "drink 8 glasses of water a day" rule - many people repeat it, few actually check if it makes sense.– tmajCommented Jul 4, 2016 at 0:03
-
7my research is as an employer, those are the general timeframes I use, same with other employers I talk to. It's based on logic, 18 months to two years is the amount of time I expect someone to become really proficient at a job, have learned or made up all the tweaks that make a difference. Up to a year they're still learning. Depends on the job of course.– Kilisi ♦Commented Jul 4, 2016 at 2:16
-
2Having been a hiring manager in several industries, I'd say that the timing depends a bit on the industry, but what @Kilisi provides is a pretty good rule of thumb. Some places (e.g. academia) will care more than others (e.g. high demand tech firms), but on the whole this is good advice.– PaulCommented Jul 4, 2016 at 3:29
-
1+1 Good answer as always. I would just add that contract employment, at least in the USA is typically no more than 18 months and usually 1 year or less in the IT field. Recent changes to labor law regulations have made employers skittish at having anyone in a contract for more than a year.– Old_LamplighterCommented Jul 5, 2016 at 13:00
|
Show 4 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. software-industry), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you