6. Key Responsibilities
As a Database Business Analyst, your day-to-day work is centered on supporting CNO (Chief of Naval Operations) availabilities and other critical shipyard metrics. You will spend a significant portion of your time designing and maintaining databases, but your most visible output will be the dashboards and reports you create to track Cost Performance, Capacity Mismatch, and Work Stoppage.
You will act as a consultant to the organization, helping teams understand their own data. This involves collaborating with the ISD team to ensure that database requirements are fully documented and that all reporting tools—particularly Business Objects—are utilized to their full potential. You aren't just writing queries; you are providing the data-driven narrative that allows project managers to make high-stakes decisions.
7. Role Requirements & Qualifications
To be a competitive candidate, you must balance technical skill with a strong understanding of business processes.
- Must-have skills:
- Bachelor’s degree in Computer Science, Information Systems, or Business Administration.
- 4–7 years of experience in database administration or business analysis.
- Proficiency in SQL and database query development.
- Ability to obtain or maintain a Secret Clearance.
- Nice-to-have skills:
- A Master’s degree in a related field.
- 10+ years of experience in Business Intelligence.
- Experience with DoD or Navy shipyard IT systems.
- Advanced proficiency in Business Objects (BO) reporting.
8. Frequently Asked Questions
Q: How important is the Secret Clearance?
It is a mandatory requirement. If you do not currently hold an active clearance, it may significantly impact your eligibility for this specific role.
Q: Is this a remote-heavy role?
Given the requirement for familiarity with shipyard IT systems and government programs, expect a strong onsite or hybrid presence in Portsmouth, VA or the assigned location.
Q: What is the most common reason candidates are rejected?
Candidates often struggle when they can describe the "how" (the code) but cannot articulate the "why" (the business impact). Ensure you can explain how your work improves project outcomes.
Q: How much technical vs. non-technical work should I expect?
It is a 60/40 split. You will spend 60% of your time on database administration and query development, and 40% on stakeholder communication, documentation, and process analysis.
9. Other General Tips
- Understand the Domain: Familiarize yourself with the terminology used in Naval Shipyard IT systems. Even if you haven't worked in defense, showing that you understand the "language" of the industry goes a long way.
- Show Your Documentation: If you have sanitized examples of design documents or technical requirements you have written, be prepared to talk through them.
- Be Ready for Ambiguity: The role requires you to define requirements from scratch. Use the STAR method (Situation, Task, Action, Result) to describe times you took ownership of an ambiguous project.