June 7, 2012 at 8:20 am
Greg Edwards-268690 (6/7/2012)
My co-worker is leaving soon, so yesterday my manager asked me job description / keywords he should use in a job posting.We are open to some suggestions on how to attract good candidates.
HR wants to be very generic, but we are much closer to the work and don't want to waste time on sorting through a bunch of applicants.
We're looking for someone who can do ETL (SSIS), as well as develop SSRS Reports / PerformancePoint Dashboards in Sharepoint 2010, and is familiar with Cube structure, MDX to build and maintain a cube (SSAS).
What keywords would you search on?
We struggle a bit as this seems to be quite the wide skillset.
Craig might be a better person to answer this as he has experience vetting what job descriptions are really asking for, but here's my shot at it:
ETL
X amount of Experience using SSIS, SSRS, and SSAS
Sharepoint
Business Intelligence methodology
To tell you the truth, your skillset requirements don't seem that broad. They seem perfectly tailored to someone used to working in the SQL Server BI subset.
June 7, 2012 at 10:07 am
Brandie Tarvin (6/7/2012)
Greg Edwards-268690 (6/7/2012)
My co-worker is leaving soon, so yesterday my manager asked me job description / keywords he should use in a job posting.We are open to some suggestions on how to attract good candidates.
HR wants to be very generic, but we are much closer to the work and don't want to waste time on sorting through a bunch of applicants.
We're looking for someone who can do ETL (SSIS), as well as develop SSRS Reports / PerformancePoint Dashboards in Sharepoint 2010, and is familiar with Cube structure, MDX to build and maintain a cube (SSAS).
What keywords would you search on?
We struggle a bit as this seems to be quite the wide skillset.
Craig might be a better person to answer this as he has experience vetting what job descriptions are really asking for, but here's my shot at it:
ETL
X amount of Experience using SSIS, SSRS, and SSAS
Sharepoint
Business Intelligence methodology
To tell you the truth, your skillset requirements don't seem that broad. They seem perfectly tailored to someone used to working in the SQL Server BI subset.
The key is BI / Datawarehousing - it can be very different than just getting a transaction into a system.
Would you tend to agree more emphasis on SSAS might be good?
It seems with SSAS skils, you likely have SQL skills, and more understanding of BI.
But SQL skills can more often mean just that.
June 7, 2012 at 10:47 am
Greg Edwards-268690 (6/7/2012)
Brandie Tarvin (6/7/2012)
Greg Edwards-268690 (6/7/2012)
My co-worker is leaving soon, so yesterday my manager asked me job description / keywords he should use in a job posting.We are open to some suggestions on how to attract good candidates.
HR wants to be very generic, but we are much closer to the work and don't want to waste time on sorting through a bunch of applicants.
We're looking for someone who can do ETL (SSIS), as well as develop SSRS Reports / PerformancePoint Dashboards in Sharepoint 2010, and is familiar with Cube structure, MDX to build and maintain a cube (SSAS).
What keywords would you search on?
We struggle a bit as this seems to be quite the wide skillset.
Craig might be a better person to answer this as he has experience vetting what job descriptions are really asking for, but here's my shot at it:
ETL
X amount of Experience using SSIS, SSRS, and SSAS
Sharepoint
Business Intelligence methodology
To tell you the truth, your skillset requirements don't seem that broad. They seem perfectly tailored to someone used to working in the SQL Server BI subset.
The key is BI / Datawarehousing - it can be very different than just getting a transaction into a system.
Would you tend to agree more emphasis on SSAS might be good?
It seems with SSAS skils, you likely have SQL skills, and more understanding of BI.
But SQL skills can more often mean just that.
Brandie's is good, given your additional specifications, I'd add Datawarehousing and mention the size of the database and daily throughput.
As far as broad? I'd love to see a job req that nicely tailored. There's no mention of Windows, Perl, IIS, HTML, XML or the Cloud!
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
June 7, 2012 at 11:03 am
Stefan Krzywicki (6/7/2012)
Greg Edwards-268690 (6/7/2012)
Brandie Tarvin (6/7/2012)
Greg Edwards-268690 (6/7/2012)
My co-worker is leaving soon, so yesterday my manager asked me job description / keywords he should use in a job posting.We are open to some suggestions on how to attract good candidates.
HR wants to be very generic, but we are much closer to the work and don't want to waste time on sorting through a bunch of applicants.
We're looking for someone who can do ETL (SSIS), as well as develop SSRS Reports / PerformancePoint Dashboards in Sharepoint 2010, and is familiar with Cube structure, MDX to build and maintain a cube (SSAS).
What keywords would you search on?
We struggle a bit as this seems to be quite the wide skillset.
Craig might be a better person to answer this as he has experience vetting what job descriptions are really asking for, but here's my shot at it:
ETL
X amount of Experience using SSIS, SSRS, and SSAS
Sharepoint
Business Intelligence methodology
To tell you the truth, your skillset requirements don't seem that broad. They seem perfectly tailored to someone used to working in the SQL Server BI subset.
The key is BI / Datawarehousing - it can be very different than just getting a transaction into a system.
Would you tend to agree more emphasis on SSAS might be good?
It seems with SSAS skils, you likely have SQL skills, and more understanding of BI.
But SQL skills can more often mean just that.
Brandie's is good, given your additional specifications, I'd add Datawarehousing and mention the size of the database and daily throughput.
As far as broad? I'd love to see a job req that nicely tailored. There's no mention of Windows, Perl, IIS, HTML, XML or the Cloud!
For an intermedaite or senior BI developer, I would probably add "understanding of business statistics." By that I mean a good grasp of applicability of arithmetic average, modus and median, and of standard deviation and similar concepts, at least at the level that allows him/her to discuss requirements with business users.
edit: typo in 'level'
June 7, 2012 at 11:09 am
Revenant (6/7/2012)
Stefan Krzywicki (6/7/2012)
Greg Edwards-268690 (6/7/2012)
Brandie Tarvin (6/7/2012)
Greg Edwards-268690 (6/7/2012)
My co-worker is leaving soon, so yesterday my manager asked me job description / keywords he should use in a job posting.We are open to some suggestions on how to attract good candidates.
HR wants to be very generic, but we are much closer to the work and don't want to waste time on sorting through a bunch of applicants.
We're looking for someone who can do ETL (SSIS), as well as develop SSRS Reports / PerformancePoint Dashboards in Sharepoint 2010, and is familiar with Cube structure, MDX to build and maintain a cube (SSAS).
What keywords would you search on?
We struggle a bit as this seems to be quite the wide skillset.
Craig might be a better person to answer this as he has experience vetting what job descriptions are really asking for, but here's my shot at it:
ETL
X amount of Experience using SSIS, SSRS, and SSAS
Sharepoint
Business Intelligence methodology
To tell you the truth, your skillset requirements don't seem that broad. They seem perfectly tailored to someone used to working in the SQL Server BI subset.
The key is BI / Datawarehousing - it can be very different than just getting a transaction into a system.
Would you tend to agree more emphasis on SSAS might be good?
It seems with SSAS skils, you likely have SQL skills, and more understanding of BI.
But SQL skills can more often mean just that.
Brandie's is good, given your additional specifications, I'd add Datawarehousing and mention the size of the database and daily throughput.
As far as broad? I'd love to see a job req that nicely tailored. There's no mention of Windows, Perl, IIS, HTML, XML or the Cloud!
For an intermedaite or senior BI developer, I would probably add "understanding of business statistics." By that I mean a good grasp of applicability of arithmetic average, modus and median, and of standard deviation and similar concepts, at least at the level that allows him/her to discuss requirements with business users.
edit: typo in 'level'
Understanding of business statistics and being able to discuss those arithmatic concepts with business users are two very different skill sets. I'd separate them, and only include "ability to interpret business requirements and convey complex ideas to non-technical end-users" if there's actually going to be any interaction with the business users. If this person is going to be insulated from the end users and work off specs generated by others, I wouldn't focus on that in the job req.
In fact, I'd probably leave both of those off the job req entirely and ask questions designed to ascertain the candidates abilities in these areas in the interview. That's the kind of more general requirement that gets ignored at the job req stage anyway.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
June 7, 2012 at 11:18 am
Stefan Krzywicki (6/7/2012)
Brandie's is good, given your additional specifications, I'd add Datawarehousing and mention the size of the database and daily throughput.
As far as broad? I'd love to see a job req that nicely tailored. There's no mention of Windows, Perl, IIS, HTML, XML or the Cloud!
Size is relative. Plans are to expand our datawarehouse to include sites globally.
How did you know I have to explore cloud and mobile device access to our data?
Can you say Kerberos and Claims to Windows Token Service without scaring people away?:-P
June 7, 2012 at 11:22 am
Greg Edwards-268690 (6/7/2012)
Stefan Krzywicki (6/7/2012)
Brandie's is good, given your additional specifications, I'd add Datawarehousing and mention the size of the database and daily throughput.
As far as broad? I'd love to see a job req that nicely tailored. There's no mention of Windows, Perl, IIS, HTML, XML or the Cloud!
Size is relative. Plans are to expand our datawarehouse to include sites globally.
How did you know I have to explore cloud and mobile device access to our data?
Can you say Kerberos and Claims to Windows Token Service without scaring people away?:-P
Yeah, but you need to mention size or you'll get people who think "large datawarehouse" is a few gig. Size is relative, which is why you should state expected daily throughput, number of sources, something to give an idea of how much data will be handled.
Some of the ones that won't be scared away are exactly the ones you want. Of course, there will be those that won't be scared away 'cause they are in way over their heads anyway and don't know any better, but that's what the interviews are for.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
June 7, 2012 at 11:30 am
Stefan Krzywicki (6/7/2012)
Revenant (6/7/2012)
For an intermedaite or senior BI developer, I would probably add "understanding of business statistics." By that I mean a good grasp of applicability of arithmetic average, modus and median, and of standard deviation and similar concepts, at least at the level that allows him/her to discuss requirements with business users.
Understanding of business statistics and being able to discuss those arithmatic concepts with business users are two very different skill sets. I'd separate them, and only include "ability to interpret business requirements and convey complex ideas to non-technical end-users" if there's actually going to be any interaction with the business users. If this person is going to be insulated from the end users and work off specs generated by others, I wouldn't focus on that in the job req.
In fact, I'd probably leave both of those off the job req entirely and ask questions designed to ascertain the candidates abilities in these areas in the interview. That's the kind of more general requirement that gets ignored at the job req stage anyway.
A couple of very good points to keep in mind as we go through the interview process.
Although my manager is the overall architect, we are expected to be both technical and business savvy.
Our job is pretty much pointless if we and the business are not on the same page.
Thanks everyone for some comments so far!
June 7, 2012 at 1:59 pm
Greg Edwards-268690 (6/7/2012)
Brandie Tarvin (6/7/2012)
Greg Edwards-268690 (6/7/2012)
My co-worker is leaving soon, so yesterday my manager asked me job description / keywords he should use in a job posting.We are open to some suggestions on how to attract good candidates.
HR wants to be very generic, but we are much closer to the work and don't want to waste time on sorting through a bunch of applicants.
We're looking for someone who can do ETL (SSIS), as well as develop SSRS Reports / PerformancePoint Dashboards in Sharepoint 2010, and is familiar with Cube structure, MDX to build and maintain a cube (SSAS).
What keywords would you search on?
We struggle a bit as this seems to be quite the wide skillset.
Craig might be a better person to answer this as he has experience vetting what job descriptions are really asking for, but here's my shot at it:
ETL
X amount of Experience using SSIS, SSRS, and SSAS
Sharepoint
Business Intelligence methodology
To tell you the truth, your skillset requirements don't seem that broad. They seem perfectly tailored to someone used to working in the SQL Server BI subset.
The key is BI / Datawarehousing - it can be very different than just getting a transaction into a system.
Would you tend to agree more emphasis on SSAS might be good?
It seems with SSAS skils, you likely have SQL skills, and more understanding of BI.
But SQL skills can more often mean just that.
My suggestion:
medium/senior BI developer proficient in the SQL Server BI stack (SSIS / SSAS / SSRS)
Knowledge of developing, deploying and maintaining ETL solutions.
Knowledge of building, deploying and securing OLAP cubes.
Knowledge of the Kimball methodology is a plus.
Knowledge of SharePoint PerformancePoint services is an asset.
Affinity with business requirements.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
June 8, 2012 at 7:39 am
Ugh, just found out we're switching to security that requires you to change your password every 90 days. Nice that we're switching to that now that security experts are saying that's exactly the wrong thing to do. They've only been saying that for years now, so why should we know? Infuriating! I look forward to seeing people's passwords written down on stickies on their monitors.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
June 8, 2012 at 7:42 am
90 days thats a luxury, the company group policies here are typical user accounts get 45 days, and if your a domain admin your password expires every 14 days.
June 8, 2012 at 7:45 am
anthony.green (6/8/2012)
90 days thats a luxury, the company group policies here are typical user accounts get 45 days, and if your a domain admin your password expires every 14 days.
every 14 days? That's madness and a great recipe for really bad passwords.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
June 8, 2012 at 7:52 am
PasswordSafe
That is all.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 8, 2012 at 7:57 am
GilaMonster (6/8/2012)
PasswordSafeThat is all.
I'd started using eWallet, but that isn't free. Thanks!
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
June 8, 2012 at 8:06 am
Stefan Krzywicki (6/8/2012)
anthony.green (6/8/2012)
90 days thats a luxury, the company group policies here are typical user accounts get 45 days, and if your a domain admin your password expires every 14 days.every 14 days? That's madness and a great recipe for really bad passwords.
Yep it is, but I know that the majority of people with domain admin rights, just increment the number by 1 every change. Each DA has a standard user account which is what we all should be using for general day to day etc.
It was changed from 45 to 14 days due to a number of security breach's which happened.
Viewing 15 posts - 36,421 through 36,435 (of 66,712 total)
You must be logged in to reply to this topic. Login to reply