1. LandOffer
  2. Blog
  3. All articles
  4. Fidelity Leap Program: Choose a Graduate Technology Track and Verify Cohort Eligibility

Job search

Fidelity Leap Program: Choose a Graduate Technology Track and Verify Cohort Eligibility

Current January 2027 requisition audit and a fictional graduate contribution case distinguish track fit, degree timing and employment unknowns.

9 min readLandOffer team

Fidelity Leap can fit a graduate seeking a technology career with a structured cohort, but choose a specific job before preparing an application. The current US software-engineering and systems-analysis openings describe different work. Use the selected vacancy's start date, degree condition and office locations when deciding whether an intake fits.

LandOffer publishes this guide. We reviewed official public pages on October 20, 2026, including two January 2027 vacancies, without applying, starting an assessment or receiving an offer. The completed candidate case is fictional. Keep comparable entry-level opportunities in view through your existing sources or recent tech roles on LandOffer.

A graduate compares a code notebook and a process diagram at a university worktable before choosing a technology career direction.

Start with the current vacancy rather than a track label

Fidelity's graduate-program overview, dated March 24, 2026, describes Leap as technology development lasting up to 12 weeks. It mentions software and data engineering and learning followed by a full-time role. That establishes the program's general purpose, rather than a current opening in every area it names.

The two vacancies examined here instead describe a 10-week experience: January 2027 Leap Software Engineer and January 2027 Leap Systems Analyst. Treat the selected requisition as the practical starting point for cohort planning. A general overview can remain useful while its duration and examples differ from a particular intake.

If you want data engineering, look for a current data-engineering vacancy. A mention of data engineering elsewhere does not establish a current seat, a selectable specialization inside either vacancy, or a later transfer. Similarly, a software-engineering title does not promise that every participant chooses a preferred language, business unit or eventual team.

Separate countries and employers when searching. A page for another country's graduate intake cannot establish US eligibility. This guide covers the two identified US requisitions, not every Fidelity-branded technology program or every future Leap cohort.

Completed audit: two January 2027 technology routes

This is our completed comparison of the public descriptions, not a record of interviews or offers. Both public descriptions and their application sections were readable when checked. We did not verify remaining seats or complete the application flow.

Question Software engineer, ID 2133859 Systems analyst, ID 2136142
Cohort start January 11, 2027 January 11, 2027
Locations listed Boston, Durham, Merrimack and Westlake Same four locations
Degree timing Related bachelor's earned or expected by the start Same degree-by-start condition
Work emphasized Building, testing and deploying software Requirements, workflows, data investigation and testing
Evidence to prioritize Personally implemented behavior and programming fundamentals Personally clarified requirements and investigated system behavior
Assessment statement found Selected applicants complete Java or Python skills assessment before interview No equivalent assessment sequence specified in the examined description

Sources: software vacancy and analyst vacancy. Both explicitly say immigration sponsorship will not be provided. That wording is a condition to investigate accurately, not a determination this article can make for an individual.

The audit resolves a useful first decision: these are two different jobs sharing a cohort date. It does not resolve personal eligibility, how many positions remain, team allocation or a candidate's assessment invitation. Keep those unknowns out of a readiness claim.

Verify the degree date against the actual start

Both examined roles call for a bachelor's in computer science, software engineering or a related field by the start date. They do not provide a precise earliest acceptable graduation date in the descriptions we read. Do not manufacture a “2026 graduates only” rule or assume a particular older graduation year is accepted.

Compare the start with your current expected degree-completion date before preparing a cohort-specific packet. If the last required course ends after January 11, the January start conflicts with your plan. A flexible course timetable is different from an employer agreeing to a later start. It is reasonable to skip an intake whose start you cannot meet and prepare for a better-timed opening.

Ceremony dates can also obscure the comparison. Your commencement celebration, final examination and official completion or conferral date may differ. Use accurate institutional information rather than changing a resume date to make it fit. Where the employer's interpretation remains uncertain, retain that uncertainty rather than treating this guide as approval.

The broader student careers page describes internships and full-time entry routes. It does not make every student eligible for each vacancy. Someone still in school should inspect the appropriate current opening and its own timing. A graduate role and an internship can have different conditions even when both lead toward technology work.

Choose between implementation and analysis evidence

For software engineering, look for evidence that you can explain a program's behavior: the inputs you handled, the implementation you owned, a failure you investigated and how you checked the correction. A group repository is useful only when you can identify your contribution within it. Listing every library the team used tells the reader little about that contribution.

For systems analysis, technical reasoning can appear in a requirement you made testable, a dependency you traced or a data inconsistency you investigated. Writing clear acceptance criteria is substantive work when it resolves an actual ambiguity. It becomes weak evidence when it merely repeats a feature title without identifying expected behavior.

These are preparation judgments based on the role descriptions, not a Fidelity scoring formula. Neither route should be reduced to “coding” versus “talking.” The analyst description includes data and testing work, and software delivery requires understanding requirements and collaborating. Choose the role whose central work interests you and whose expectations your evidence addresses most directly.

Do not copy an analyst's activities into a software-engineering accomplishment or claim a teammate's implementation. A truthful account of a small, finished contribution is more useful than a broad title you cannot support with details.

Completed candidate case: one project, two possible directions

Consider Inez, a fictional information-systems student expecting to complete her bachelor's on December 18, 2026. She lives near Durham and wants regular in-person collaboration. Her example assumes she can start January 11; it does not establish an employer's degree evaluation or work-authorization decision.

Her group built a teaching-lab fault-reporting prototype. A teammate implemented its web interface. Inez mapped the reporting process, drafted acceptance criteria and compared synthetic ticket records with the status shown in the prototype. The project used invented equipment names and reports, not real student or lab records.

Her first project description was “Helped build a lab support system.” That concealed the part she owned. She completed the following evidence selection before deciding which Leap role deserved her preparation time:

Artifact she actually owns in this fictional case What it demonstrates Limit she keeps visible
State diagram distinguishing reported, assigned, resolved and reopened A shared interpretation of the support workflow A design for this prototype, not a production service
Note identifying that resolution time persisted after a ticket reopened An observed mismatch between state and stored data No claim that she implemented the interface repair
Acceptance criteria for reopening and resolution timestamps Expected outcomes that a teammate could check Criteria alone do not prove every branch works
Synthetic-record comparison with the investigation notes A specific data check supporting her explanation No customer-impact or response-time improvement claimed

Her completed requirement note says: “When a resolved ticket is reopened, its current status becomes reopened and its current resolution timestamp is cleared. The earlier resolution remains in the history. A newly resolved ticket records the new resolution time.” This separates the current state from its audit history instead of deleting useful history to make the screen look consistent.

She also records three expected checks: a reopened ticket has no current resolution timestamp; its previous resolution remains in history; resolving it again creates a new current timestamp. These are the fictional project's acceptance criteria, not a live Fidelity assessment answer or a claim that we executed the prototype.

Inez's revised summary is: “Mapped the lab fault-reporting workflow, identified a reopened-ticket timestamp inconsistency using synthetic records, and defined acceptance criteria distinguishing current resolution from historical events. A teammate implemented the interface change.” She can now explain a decision, its supporting evidence and her ownership boundary.

Inez keeps the diagram, criteria and comparison notes together, with a short record of who authored each artifact. She removes the group presentation from her primary evidence because it does not separate her work from the interface developer's. If a reviewer asks about implementation, she can describe the handoff and its limit instead of presenting the entire application as her own. Her packet is now narrower and easier to inspect.

Her decision is to prioritize systems-analysis preparation. Her strongest artifacts concern requirements, state transitions and data investigation. She retains software engineering as a separate possibility if she can support its programming expectations with her own work; she does not relabel this contribution as full-stack development.

A lab fault tag and a workflow sheet with a return arrow sit beside a separate closed notebook, illustrating analysis and implementation ownership.

Resolve office attendance and employment details before committing

The selected vacancies list Boston, Massachusetts; Durham, North Carolina; Merrimack, New Hampshire; and Westlake, Texas. They are marked onsite, with broader text describing an evolving move toward full-time office attendance. A list of several cities does not mean you can switch freely between them or participate from anywhere.

Inez therefore treats Durham as a location she can discuss, not an allocation she already holds. Before accepting an eventual offer, she would need its actual worksite, attendance expectations and start arrangements. Moving expenses, temporary accommodation and relocation support remain unknown unless provided in her own terms.

The displayed annual base ranges were $55,000–$134,000 for software engineering and $71,000–$134,000 for systems analysis. The pages qualify placement by location, responsibilities and other factors. These are published ranges, not personal offers, program-wide starting salaries or proof that choosing analysis produces higher pay. Software compensation wording and analyst compensation wording should stay attached to their requisitions.

The sources present employment opportunities with an immersive development period. They do not give us Inez's signed offer, separate training-period pay schedule or guaranteed post-program team. Evaluate those details in the actual employment documents rather than treating the ten-week description as the complete agreement.

Prepare within the candidate rules

The software vacancy describes an assessment gate for selected applicants. It does not publish the actual questions, a universal time limit or our candidate's invitation. The absence of the same wording in the analyst description does not establish an assessment-free process.

Fidelity's candidate AI guidelines permit uses such as proofreading and interview preparation, while restricting outside help, resources and AI during assessments and interviews unless specifically instructed otherwise. A program's discussion of AI-assisted work does not authorize AI assistance during selection.

For preparation, Inez practices explaining her own state diagram and the choice to preserve history. She can identify what remains untested without inventing an outcome. If invited to an assessment, she would follow that invitation's instructions. This guide does not require access to private questions, employer systems or another candidate's answers.

Make a cohort-specific decision

Save one current requisition, compare its start and office location with your availability, then select one contribution you can explain and substantiate. If the start cannot fit your degree completion, keep searching rather than claiming flexibility the employer has not granted.

Keep the exact title and requisition ID beside your saved notes so a later vacancy cannot silently replace your original assumptions. Continue ordinary discovery through your existing search or LandOffer's recent roles, and revisit Leap when an opening matches your timing and direction.

Sources and Further Reading