|
|
|
 |
|
|
 |
 |
|
 |
 |
|
|
Welcome to the Catalyze Forums
|
|
The Forums on Catalyze give members an opportunity to network with other members and ask/answer questions on current topics.
|
|
|
 |
|
|
You must be a registered member of the Catalyze community to post;
Click here to JOIN TODAY If you are already a member, SIGN IN HERE
|
|
|
 |
|
|
|
|
Add Tag
|
| You are not authorized to post a reply. |
|
bmerrikin Posts:2
 |
| 06/26/2008 3:01 PM |
Alert
|
A while ago I went on a job interview for a Sr. BA position. The interviewer brought up the fact you need to be a good writer to be a BA - he got no argument from me. And I have no issues with my writing skills as they apply to BA documentation. But he kept hounding on that comment and kept digging. And I knew exactly what he was looking for. He wanted to see a sample of some reports and specs that I had written. But I didn't bring any with me for a whole host of reasons. First, I believed my company owned that information, and second I don't think my company would want me handing out reports that show proprietary information about their systems. And hate to think what would happen if my company found out that I was handing that information out at job interviews... so I didn't. Has anyone else been asked (or hinted at) for sample work? Do you bring samples of your BA work to job interviews? Is it ok to do that? How have you demonstrated your writing abilities to interviewers.
Thanks,
Brian |
|
|
|
|
MaryC Posts:1
 |
| 06/27/2008 9:33 AM |
Alert
|
I've done written exercises during interviews. I've asked candidates to do written exercises during interviews. If I was hiring, I wouldn't put much faith in work samples that were brought to an interview - you have no way of knowing who did the actual writing. And for any real-world sized document, there are likely to have been several contributors, including the person in the company who originally wrote the template. |
|
|
|
|
adelle71 Posts:1
 |
| 07/04/2008 4:00 PM |
Alert
|
I've brought a lot of proprietary work with me on interviews and allow them to look at it. However, I let them know I cannot leave it behind because of those proprietary reasons. Usually there is at least one thing you can find to leave behind and during the interview they can see what they need to know by perusing your documentation. Most companies are professional and understand these things. Additionally, they will respect your adherence and loyalties to your past organizations. Not bringing anything with you does not show well, proprietary reasons or not. |
|
|
|
|
AMoffa Posts:1
 |
| 07/25/2008 11:56 AM |
Alert
|
| adelle71, I agree with you. As a UX professional who has also held BA jobs, I've felt compelled to bring work samples to interviews, especially because UX is such a visual design kind of job, whereas the BA is more writing-focused. In either case, I would recommend that you try to "sanitize" the work sample as much as possible, and come up with at least 2-3 samples that are "safe" to leave behind. IOW, generalize the examples, use fictitious companies and brands, etc. I would not recommend leaving any work behind that could be interpreted as proprietary, as your candidacy can be dismissed for doing so. It never fails to amaze me how often the best work gets overlooked for the wrong reasons. You may be the best UX or BA pro, but if you don't market yourself, you won't get the job. The other thing to do is, ask the interviewer if they would like to see some samples _before_ you show up for the interview. Ask them what kind of work sample are they looking for specifically, e.g., business requirements gathering and documentation, requirements traceability matrices, etc. I like to go as prepared as possible - I hate surprises. |
|
|
|
|
despil Posts:1
 |
| 07/25/2008 1:58 PM |
Alert
|
| I have no documents from my previous jobs with me. When I left the company, I left the docs too. So, what do you think, a "mock up" project documentation can be good enough? |
|
|
|
|
|
|
|
|
|
 |
|
 |
|
 |
 |
 |
 |
|
|
 |
|