One question: in the IT field do you receive a job opportunity because of who you know or what you know? | LinkedIn

One question: in the IT field do you receive a job opportunity because of who you know or what you know? | LinkedIn

My response to this question:

---

Both "who" and "what" are important; it is not an "either or" situation. A person (friend, colleague, network contact, ...) - the "who" - can give you a "heads up" or maybe get your resume to a hiring manager, but it seems that most large companies (where the jobs are) now use recruiting firms to screen applicants. But if you don't meet the job's requirements - the "what" -, that won't get you the job and it will make your "who" look bad. Entry-level jobs in the US are few and far between. It seems most jobs (contract or FTE) are looking for mid-level experience (around 5 years) in specific skill sets. Certifications without work experience will only be better for you if you are competing against someone without either certifications or work experience - you have an advantage for an entry-level job. To get work experience, you can try to do pro bono work for charities, a friend's business, small businesses that need some small help; you can also try temp agencies, but they may require work experienced, too. This pro bono and/or temp work could lead to long-term contract or FTE recommendations. Good luck.

Data Architect, Duties of a

I have read many job postings seeking a Data Architect.  Most had a few data architect duties included, but specified some duties of many data-related positions not normally considered as part of the data architect role; seems like they were looking for one person to do the work of multiple specialists.  It seems to me that will get a company a "Jack/Jill of all trades, master of none."

While most Data Architects will have had experience in multiple data-centric roles doing multiple data-related tasks, few (none?) of us will have kept up-to-date skills in many of those skills.  While understanding the roles of those other data specialists we will be working with is crucial, we have moved our focus to a much higher elevation.  We should be able to mentor and assist other data specialists in getting their assigned duties accomplished, but we do not do the actual work involved (except in a critical, unplanned, resource shortage).

I have gleaned the following list of duties from dozens of different position position postings for Data Architects from the Internet.  I have included only those I feel are germane to the postion.

• Data Architect to assist with data mappings, data modeling, data profiling, query design, data flow design, etc between multiple databases across multiples platforms. Data Architect will be support and contribute to DI/ETL architecture and act as data SME (subject matter expert) with respect to data profiling assessments and participate in JAD session/interviews.
• Perform data profiling and analysis to assess data quality/patterns, recommend data cleansing rules, conforming data standardardzing rules, and matching algorithm changes to [business] and data bus architecture (dimensions/facts)
• Database query Performance and Tuning expertise (P&T) on SQL statements.
• ETL Workflow and data mapping analysis, review, and tuning.
• Strong design artifact experience in documentation of data flow and data mapping and data exchange specifications.
• ETL development experience and technical adeptness at reviewing and initial prototyping tasks.
• Has solid project lifecycle, database design experience, and complimentary Business Analyst skills.
  (Although, I limit the BA skills to those needed to define business data items needed for database structure.  I work with the BA to get these.)
• Responsible for the creation of the following work deliverables:


• Estimate for resources needed, effort needed, and target milestone dates.
• Data requirements documents, including traceability.
• Weekly status reports from my team
• Compiled weekly status report to project manager for team's work.
• Conceptual data model, including metadata at the entity level
• Logical data model, including metadata at the entity and attribute level
• Data Profiling/Gap Analysis
• Data Dictionary
• Data Flow Diagram
• Physical data model, including metadata at the table, column, and view level
• Volume metrics (expected initial load and 3-year and 5-year forecasts)
• DDL Scripts (generated from modeling tool such as PowerDesigner or Erwin)
• ETL Data Mapping (ultimate source to ultimate target, not every hop along the way)


• Primary Responsibilities:


• Building conceptual, logical and physical database designs
• Participating in data development and analysis, and data dictionary management
• Ensuring data consistency and accuracy across all systems
• Collaborating with business analysts, ETL developers and other key internal personnel on a wide scope of data architecture functions

Data Architect Job Description

I found this definition of a Data Architect on CareerBuilder.

Defines, designs, and builds relational and/or multi-dimensional databases for warehousing of data. Confers with client, technical staff, and team members to plan, design, develop, implement, and enhance applications, scripts, procedures, and metadata for relational databases. Reviews current data structures and recommends optimizations and reconfigurations as warranted. Generates data acquisition and archive recovery strategies. Works with Database Administrators to migrate complex large scale applications into test and production environments. Integrates new data with existing warehouse structure and continuously improves system functionality. Evaluates and recommends new tools and methodologies. Consults with vendors to integrate selected packages. Deletes old data. Develops and maintains all standards in accordance with data structures and models. May work with organization departments to design and develop data marts. (Source: eDOT Job Description)

Do you agree with this definition? Does it include too much or not enough? I agree with most of it, but I question or disagree with the following points:

• archive recovery strategies
  This is more of a DBA or Disaster Recovery role
• continuously improves system functionality
  Not quite sure what is meant by this; seems to be DBA or development team role.
• Evaluates and recommends new tools and methodologies
  What new tools and methodologies? I might do this for data modeling tools like Erwin or PowerDesigner if they are looking for this and can do this for data architecture-related practices such as data governance, data quality, naming conventions, modeling standards, and so forth.
• Consults with vendors to integrate selected packages.
  This is Solution, System, or Application Architect role.
• Deletes old data.
  This is done by the user, application, or DBA.