Job Description :
The profile for the SQL Developer includes the following:
A solid SQL / SSRS / DTS / Database programmer / analyst / Designer: able to assess the current
movement of data, data sources, calculations and formatting done today, then sketch out a
solution to automate the calculations and slicing & dicing, then produce the reports identical to
those created today.
SQL SSRS / SSIS fluency: to either work or create data exchange packages / requests to automate
the collection of data from external sources
Data formatting / DTS / Database design: besides data propagation in extracting from pivot tables,
a goal would be to build data store(s) where the data is aggregated before creating reports.
BI tools and concept knowledge: once we have a data store (SQL), a second phase goal would be
to both extract standard reports, or to open the data store to users so they can slice and dice. We
have Microsoft Power BI deployed on top of Office 365, which works well with SQL dbs.
Discovery and Technical + process analysis: even if elementary BRD or scoping document are
provided, there will be a systemic
Documentation: we suffer from chronic documentation disorder. Even if this will be just a drop in
the ocean, I want all work and findings to be documented the best we can; we have to start
somewhere. I plan to deploy Sharepoint or something as a knowledge base, and for now we can
stash these into shared folders.
At least some understanding of GP, mainly focusing on the SQL DBs which we extract information
from; we have resources (CAL) to help with that if need be. There is however more work to be
done around GP interfaces and extracts, so this would be a nice add-on. We are using Smartlist,
SmartConnect and other tools to interface with GP.
Structure and rigor at work: people might jump up and down to get things added after the
discovery and BRD are done; we might encounter hidden issues and have to deal with sudden
changes of priorities: the person needs to be mature enough and familiar enough with typical
project dynamics to navigate those potential hiccups.
In most cases, the Requirements will not be fully discovered due to lack of knowledge or practice,
so most projects might have a second cycle / Sprint after initial delivery, where additional
requirements will be identified. The resource must be able to manage both expectations and
committed deliveries to be successful.