Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create login-fraud-supervisor-2024.md #1535

Merged
merged 1 commit into from
Jun 3, 2024
Merged

Create login-fraud-supervisor-2024.md #1535

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
338 changes: 338 additions & 0 deletions positions/login-fraud-supervisor-2024.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,338 @@
---
################################################################################
# #
# 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. #
# #
# On the new file page, you can paste in the contents of the template file. #
# Also be sure to type in a filename in the small textbox above the file body #
# box. You will see the text join.tts.gsa.gov / [ Name your file ...] in main. #
# Type your filename into that box. #
# #
# NOTE ABOUT FILENAMES: Your filename should be descriptive about the job #
# posting that you're creating, and it MUST end with ".md". Don't stress out #
# about filenames too much, though. They are used for the URL, which can help #
# people make sure they're on the right page, but most users will probably not #
# notice the URL. Instead, try to make it meaningful to you and others on the #
# Talent Team so you can find it easily in the future if you need to edit it. #
# #
# 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 #
# #
# For the rest of the file, follow the directions as you go, but here are a #
# couple more tips to help you as you work: #
# #
# You are currently inside the portion of the document called "frontmatter." #
# The frontmatter is the part that starts with just "---" on the first line #
# and ends with another line that only contains "---" (further down). This #
# part of the document is not DIRECTLY shown to the user. Instead, this is #
# where you can set data that will be shown to the user in other parts of the #
# page, or data that is used to configure how the page is displayed. For #
# example, the opens and closes dates are set in the frontmatter, but they #
# will never be shown to the user the way you type them in. Instead, they are #
# used to determine whether the posting is upcoming, open, or closed, and they #
# will be turned into more human-friendly text when they are displayed. #
# #
# Within this frontmatter block, lines that begin with a hash (#) symbol are #
# comments. They do not contribute to the web page at all, but they are a nice #
# way of explaining what the data in the frontmatter is. It is okay to delete #
# these comments when you are done, and it is also okay to leave them if they #
# might be helpful when editing the page later. #
# #
# The parts you need to fill out are marked with five red triangles above them #
# like this: #
#🔻🔻🔻🔻🔻 #
# #
# After the frontmatter, the rest of the document is in a special version of #
# Markdown used by the website builder. You will see comments in that section #
# as well, but they will look like this: #
# #
# {% comment ----------------------------------------------------------- %} #
# The contents in between these two lines are comments and do not #
# contribute to the web page. #
# {% endcomment -------------------------------------------------------- %} #
# #
# It is safe to remove the Markdown comments as well. #
# #
################################################################################

# 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.
#
# NOTE: Be sure to leave the "title: " part at the beginning! These line
# headings are how the site builder knows what the data is. For the rest of the
# frontmatter, please be careful not to delete the headings!
#🔻🔻🔻🔻🔻
title: "Login.gov: Fraud Supervisor"

# Put the opening and closing dates of your posting here, if you have them. The
# values you set here will be turned into user-friendly text in other parts of
# this post. Setting it here means you won't have to copy it over and over.
#
# These dates MUST be formatted as YYYY-MM-DD, where month and day are 2-digits.
# If the month number or day of the month are less than 10, add a 0 to the
# front (eg, May would be 05 instead of just 5). This is the only format the
# site builder automatically understands. Anything else will not be understood
# as a date.
#🔻🔻🔻🔻🔻
opens: 2024-07-03
closes: 2024-07-06
# These dates are also used to determine whether a position is upcoming, open,
# or closed. Here's how we decide:
#
# The job is upcoming if:
# opens is empty OR
# opens is in the future
#
# The job is open if:
# opens is in the past OR
# closes is in the future
#
# The job is closed if:
# closes is in the past
#
# If either opens or closes is empty, missing, or not a date, the position is
# considered to be upcoming.

# If the position can also close when the maximum number of applications are
# received, include the maximum number of applications here. Remove this line
# or set the value to 0 if the job does not have an application cap.
#🔻🔻🔻🔻🔻
max applications: 200

# Is this a permanent or term appointment? Use either "perm" or "term". This
# will be used to fill in the appointment type on the page with consistent
# language.
#🔻🔻🔻🔻🔻
appointment type: perm

# Put the GS grade this position is being advertised at. For SES positions, set
# the level to 20.
#🔻🔻🔻🔻🔻
gs: 15
# The information you put here will be used to automatically pull salary range
# information.
#
# ⚠️⚠️⚠️ IMPORTANT NOTE: The automatic salary ranges are based on 100% remote
# positions and use the lowest and highest locality areas. If this position is
# not 100% remote, you will need to delete the automatic salary range and input
# it yourself down below. Look for 💰💰💰 to indicate where to do that.
#
# The salary range data is stored in this file:
#
# _data/pay_ranges.yml
#
# The data file will need to be updated each year to reflect any pay changes.

# 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.
#
# Each key objective starts on a new line and must start with a dash. It does
# not need to include a number at the beginning. A key objective can be spread
# across multiple lines if you want.
#
# To add sub-bullets to your key objective, add a new line below the key
# objective and indent it with spaces. (The number of spaces does not matter, as
# long as it is more than one). Then, add a dash and your sub-bullet.
# Sub-bullets can also take up multiple lines as long as all of the lines are
# indented the same amount so they line up.
#
# The placeholder information below shows an example of how to format the key
# objectives. This example indents sub-bullets with two spaces:
#🔻🔻🔻🔻🔻
key objectives:
- Lead Login.gov’s anti-fraud program
- Oversee Login.gov identity fraud investigators to develop analytics products that inform identity fraud investigations.
- Design, develop, test, and deploy cloud-based identity fraud analytics products and workflows that monitor, detect, mitigate, or prevent identity fraud.
- Maintain existing workflows and tools used by Login.gov’s cybersecurity team to monitor, detect, and investigate identity fraud.
- Oversee Login.gov identity fraud investigators to develop analytics products that inform identity fraud investigations.
- Collaborate with Login.gov cybersecurity and platform engineers to develop identity fraud monitoring and alerting solutions.
- Support Login.gov incident response.
- Improve Login.gov’s anti-fraud analytics
- Collaborate with Login.gov product and platform teams to develop cloud-based analytics tooling that improves Login.gov’s anti-fraud posture while preserving user privacy.
- Lead the design, development, and deployment of improvements to Login.gov’s fraud analytics workflow or tooling.
- Drive long-term improvement in Login.gov’s cybersecurity posture by removing single points of failure, improving automation, reducing toil, or improving the fidelity of fraud analytics.
- Support Login.gov program management
- Design, develop, test, and deploy analytics products that efficiently report identity fraud KPIs and trends.
- Manage briefing materials for internal and external reporting of Login.gov fraud KPIs and trends.
- Identify and communicate technical, business, or program risk associated with Login.gov’s anti-fraud posture.
- Effectively collaborate with distributed, agile teams
- Openly share knowledge and work collaboratively to integrate anti-identity fraud principles into product and engineering practices.
- Participate in regular retrospectives and provide feedback to help improve the way the team works.
- Maintain a work environment of respect, diversity, equity, inclusion, accessibility, mutual support, flexibility, collaboration, continuous learning, and commitment to customer / partner needs. Ensure all perspectives are valued and included. Uphold TTS values of inclusion, integrity, and impact.

# If there are any info sessions associated with this position, list them here.
# Each info session needs three pieces of information: the link, the date, and
# the time. 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 just delete
# the lines that begin with spaces.
#
# IMPORTANT: The date MUST be formatted as YYYY-MM-DD, where the month and day
# are TWO digits. If the month or day is less than 10, add a zero to the front.
# The date is used to sort the info sessions on the page so they are shown
# nearest to furthest. Only info sessions schedule for the future will be shown.
#🔻🔻🔻🔻🔻
info sessions:
- link: https://www.eventbrite.com/...
date: 2023-02-13
time: 1:30-2:30pm ET (10:30am -11:30am PT)

# Put the link applicants need to use to apply for this position here. This link
# will be used for the "Click here to apply" button at the bottom of the
# position page.
#🔻🔻🔻🔻🔻
application link: https://usajobs.gov/job/apply/whatever
# This is the end of the frontmatter. After this line is Markdown.
---

{% comment ------------------------------------------------------------------ %}
If you want to include a closed/upcoming/open alert at the top of your page,
leave the following line. The status of the position will be determined by the
opens/closes dates at the top of this document

If you do not want the closed/upcoming/open alert, delete the line below that
says {% include job/status_alert.html %}
🔻🔻🔻🔻🔻
{% endcomment --------------------------------------------------------------- %}

{% include job/status_alert.html %}

## Basic information

Open to U.S. citizens or nationals (residents of American Samoa and Swains
Island). Subject to background check. {% include job/full_info_on_usajobs.html %}

**Supervisory status:** Supervisory

**Job title:** {{ page.title }}

{% comment ------------------------------------------------------------------ %}
The job title on USAJOBS is not always the same as the job title as we list it.
To help applicants find the right jobs on USAJOBS, put the title as it appears
on USAJOBS here.
🔻🔻🔻🔻🔻
{% endcomment --------------------------------------------------------------- %}
**Official title in USAJOBS:** Supervisory IT Specialist (INFOSEC)

{% comment %}🔻🔻🔻🔻🔻{% endcomment %}
**Number of vacancies:** 1

{% comment %}🔻🔻🔻🔻🔻{% endcomment %}
**Location:** Anywhere in the U.S. (remote)

{% comment ------------------------------------------------------------------ %}
💰💰💰
The salary range for the job can be populated automatically based on the GS
grade this posting is advertised at, based on the lowest and highest locality
rates.

💰💰💰
If this position is not remote and has geographic restrictions, you can instead
specify the salary min and max. For example, if the position is advertised at
GS-15 and the position location is only Washington, DC, then (using 2024 pay
rates):

Minimum:
GS-15 Step 1: $143,736
Maximum:
GS-15 Step 10: $191,900

So you would update the line below to look like this:

{% include job/salary_range.html min="$143,736" max="$191,900" %}

To use the autoomatic salary ranges, leave the lines as-is.

🔻🔻🔻🔻🔻
{% endcomment --------------------------------------------------------------- %}
{% include job/salary_range.html min="" max="" %}

Your salary, including base and locality, will be determined upon selection,
dependent on your actual duty location. Please note the maximum salary available
for the GS pay system is $191,900. For specific details on locality pay, please
visit [OPM's Salaries & Wages page](https://www.opm.gov/policy-data-oversight/pay-leave/salaries-wages/)
or for a salary calculator
[OPM's 2024 General Schedule (GS) Salary Calculator](https://www.opm.gov/policy-data-oversight/pay-leave/salaries-wages/2024/general-schedule-gs-salary-calculator/). You can find more
information in our
[compensation and benefits section]({% link pages/compensation-and-benefits.md %}).

{% comment %}🔻🔻🔻🔻🔻{% endcomment %}
**Travel requirement:**
Occasional travel may be required up to 10%-20% per year.

{% comment %}🔻🔻🔻🔻🔻{% endcomment %}
**Work schedule:**
Full time.

{% comment ------------------------------------------------------------------ %}
The next {% include ... %} line will pull in the appropriate text based on the
appointment type for this job. If you need to use different text, delete that
line and write your custom text in its place.
🔻🔻🔻🔻🔻
{% endcomment --------------------------------------------------------------- %}
{% include job/appointment_type.html %}

Learn more about the benefits of working at
[GSA](https://www.gsa.gov/portal/category/26702) and
[TTS]({% link pages/compensation-and-benefits.md %}).

## Role summary

{% comment %}🔻🔻🔻🔻🔻{% endcomment %}
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. We focus on the complexities of digital identity authentication for the public, so agencies can focus on their mission.

Login.gov is a FedRAMP authorized secure sign-in service created for the public to access participating government agency sites, products, and services. At its core, Login.gov is both an authentication and identity verification service and is now available to all levels of government: federal, state, and local. We're helping people access essential public services and benefits securely, privately, and seamlessly.

This opportunity is located in the Technology Transformation Services (TTS) Solutions Division’s Login.gov team. The Login.gov team is a remote organization and is composed of experts across product development, software engineering, cybersecurity, and platform engineering.


## Key objectives

{% comment ------------------------------------------------------------------ %}
Key objectives are automatically converted from the information provided at the
top of the page. The automatic conversion helps ensure that all of our postings
are consistent. If you do not want to use the automatic template, delete the
line below that says {% include job/key_objectives.html %} and add your custom
content in its place.
{% endcomment --------------------------------------------------------------- %}

{% include job/key_objectives.html %}

## Qualifications

Provide as much detail as possible on your resume so that we can evaluate your
previous experience. Follow our
[guidance on creating a federal style resume.](https://join.tts.gsa.gov/resume/)

Failure to provide required information may result in disqualification.

For each job on your resume, provide:

- The exact dates you held each job (from month/year to month/year or “present”)
- Number of hours per week you worked (if part time)

**SPECIALIZED EXPERIENCE REQUIREMENTS:**

To qualify, you must have one (1) year of specialized experience at the next
lower GS-grade (or equivalent). Specialized experience is defined as follows:

- To be updated at a later date.


## How to Apply

{% include job/apply_button.html %}
Loading