This repository has been archived by the owner on Sep 26, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 45
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create login-data-analyst-2024.md (#1616)
- Loading branch information
1 parent
b46dcac
commit ad81a5a
Showing
1 changed file
with
157 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,157 @@ | ||
--- | ||
layout: layouts/jointts/job-listing | ||
permalink: /join/{{ title | slugify }}.html | ||
tags: jobs | ||
|
||
# ############################################################################### | ||
# # | ||
# INSTRUCTIONS: TTS JOB TEMPLATE # | ||
# # | ||
# -----------------------------------------------------------------------------# | ||
# If you are editing this file on GitHub, first make sure you are creating a # | ||
# new file, and are not editing the template file! To create a new file, go to # | ||
# <https://github.com/18F/join.tts.gsa.gov/new/main/positions> in your browser # | ||
# # | ||
# Your file name should reflect the URL you would like # | ||
# For example, if you are posting a job for a content designer, you might # | ||
# choose names like # | ||
# # | ||
# tts-content-designer-2023.md # | ||
# login-content-designer-2023.md # | ||
# content-designer-2023.md # | ||
# content-designer-june-2023.md # | ||
# # | ||
# NOTE: Your file MUST end in .md # | ||
# # | ||
# For the rest of the file, follow the directions as you go # | ||
# # | ||
# ############################################################################### | ||
|
||
|
||
# This is the position title and the org that is doing the hiring. Please format | ||
# your title as "Org: Position Title" (in quotes!). The organization should be | ||
# a full name rather than an acronym. For example | ||
# - U.S. Digital Corps, not USDC | ||
# - Presidential Innovation Fellows, not PIF | ||
# The exception to this is a TTS role, for which you can just say TTS | ||
title: "Login.gov: Data Analyst" | ||
|
||
# If the role is listed on a different site and you just want to link to it, | ||
# put that link here. You can leave the rest of the template as-is, unless you | ||
# need to add info sessions. | ||
external_url: | ||
|
||
# Put the opening and closing dates of your posting here, if you have them | ||
# These dates MUST be formatted as YYYY-MM-DD, where month and day are 2-digits | ||
opens: | ||
closes: | ||
|
||
# To show the status alert for this job, leave this set to true. To hide it, change to false | ||
# To show the alert keyword association message, add the keywords separated by a semi-colon | ||
# e.g. Product Management; Strategy/Consulting; and Marketing | ||
status_alert: true | ||
alert_keywords: | ||
|
||
# If this listing has been updated since it was published, put the updated date below in YYYY-MM-DD # format | ||
updated: | ||
|
||
# BASIC INFO | ||
# The basic information and details of the position | ||
info_intro: | ||
|
||
supervisory_status: non-supervisory | ||
|
||
usajobs_official_title: IT Specialist | ||
|
||
vacancies: "1" # Put the number in quotes. | ||
|
||
location: Anywhere in the U.S. (remote) | ||
|
||
# Put the GS grade and pay range this position is being advertised at. For SES positions, set the value of gs to SES. | ||
gs: | ||
min_payrange: $ 143,736 | ||
max_payrange: $ 191,900 | ||
|
||
travel_requirement: Occasional travel may be required up to 10% per year. | ||
|
||
work_schedule: Full time. | ||
|
||
# Set to 0 if there is no limit | ||
max_applications: 0 | ||
|
||
# Use either "perm" or "term" to indicate a permanent or temporary position | ||
appointment_type: "perm" | ||
|
||
# List key objectives here. Key objectives and sub-bullets will be displayed in | ||
# the order they are listed here. You do not need to include key objective | ||
# numbers. They will be added automatically | ||
# | ||
# FORMAT EXAMPLE | ||
# | ||
# - title: Key Objective 1 | ||
# items | ||
# - Objective 1 Sub-Bullet | ||
# - Objective 1 Sub-Bullet | ||
# - title: Key Objective 2 | ||
# | ||
# The placeholder information below shows an example of how to format the key | ||
# objectives | ||
key_objectives: | ||
- title: You will increase program effectiveness through automation and technology-forward operations. | ||
items: | ||
- Identify present and future business and performance data needs. | ||
- Drive the implementation and integration of appropriate technology, architecture, and tooling, including AI/ML capabilities, to support Login.gov data and analytical needs and to scale its processes. | ||
- Design new program processes and systems that take advantage of and enhance Login.gov’s ability to understand threats and drive decisions through data. | ||
- Shape Login.gov policies, user guides, and overall strategic approach to technology and program roadmap. | ||
|
||
- title: You will apply statistical analysis and predictive modeling skills to collect and analyze data. | ||
items: | ||
- Establish solid processes for the collection and examination of relevant information from multiple sources, and structuring it to allow for effective analysis. | ||
- Ensure data integrity and troubleshoot data issues, collaborating with relevant stakeholders to implement any necessary updates or modifications to optimize data performance. | ||
- Identify potential automation of data preparation tasks, including, structuring, cleansing, and modeling. | ||
- Develop data models to identify patterns, trends, or anomalies within the program data, applying statistical techniques to interpret data and draw conclusions. | ||
- Optimize existing data and identify additional data points for analysis, verifying security and privacy compliance. | ||
|
||
- title: You will communicate and present findings of actionable insights gained from data analysis. | ||
items: | ||
- Create a visual narrative through the use of data visualization tools, such as dashboards, charts, maps, and other graphical representations. | ||
- Generate reports highlighting key findings, trends, and patterns, as well as associated risks and recommended actions. | ||
- Collaborate with stakeholders to identify data gaps and recommend mitigation/remediation, including associated performance metrics. | ||
|
||
|
||
# If there are any info sessions associated with this position, list them here | ||
# See the placeholder below for an example of how to add an info | ||
# session. If the position does not have any info sessions, you can delete everything | ||
# except "info_sessions:" | ||
|
||
# IMPORTANT: The date MUST be formatted as YYYY-MM-DD, where the month and day | ||
# are TWO digits | ||
info_sessions: | ||
- link: | ||
date: | ||
headline: | ||
time: | ||
- link: | ||
date: | ||
headline: | ||
time: | ||
|
||
# Make sure to leave the | on the first line. | ||
role_summary: | Login.gov is the public’s one account for government, simplifying access to government benefits and services for members of the public by enabling them to reuse one secure account across government agencies, and improving the security of government systems by enabling agencies to leverage a shared technology service to provide strong authentication and identity verification services to their customers. | ||
As a Data Analyst, you will work and build partnerships with senior business and technical staff within the program as well as leading cloud service providers, third party assessment organizations, tool vendors, and agencies. You will help Login.gov design, develop, and implement automated data driven approaches for measuring product performance, testing control implementations and continuous monitoring of cloud services. | ||
|
||
This position is a tactical, collaborative, outward-facing role that will require a blend of product and data expertise, a focus on consistency and quality, and a future-focused view for how Login.gov can use data in service of its mission. | ||
|
||
|
||
# Make sure to leave the | on the first line. | ||
qualifications: | To Be Updated Soon | ||
# Make sure to leave the | on the first line. | ||
specialized_requirements: | To Be Updated Soon | ||
# This can be filled prior to the job posting going live or left blank # | ||
# The application button will only show after the open date # | ||
application_link: | ||
|
||
--- |