Right now, thinking about the new FedEx application within in the context of the Healthcare.gov rollout will serve you well. I don't mean this as a political statement, more as a contextual example to help everyone understand the gravity of the backend issues that are going on. A lot of time and energy is and will need to be put in to fix this, and that won't happen quickly.

Here's what you need to know as of today if you have an application on file:

1. The data migration is not going well. The data hasn't been mapped properly, and as such, some data is missing and other data is just flat incorrect. This means that if your PilotCredentials application was completely up to date and correct just prior to the switch, much of that work has been lost, and there is nothing that you can currently do to fix it.

2. The new application currently has 2 major issues including the inability to fix current data in the new application and the inability to add new data properly into the new application. The fact that FedEx is facing both of those issues at once means that applicants are stuck for now until this is figured out.

3. The Address History, Employment History, Flight Time Matrix, and Checkride sections contain significant issues. As of today, there is nothing an applicant can do to fix or circumvent the structural issues. This means this is a sit back and wait game until FedEx fixes the application. Bad system = bad information.

4. The support desk is unavailable. If you can't log in, need to correct misinformation, or have a question, you are currently on your own.

5. Currently, updates are not being saved correctly. This means every update you make is unreliable in the near term until this is fixed.

6. FedEx is updating the application on an ongoing basis.

Because of these ongoing issues, everyone is best served by holding off on putting energy into this until the application stabilizes. The application is too unreliable, with too many issues related to speed and accuracy to make your effort worth it. In the meantime, you are better served putting all of your information together in a secure document based on the former PilotCredentials questions and new FedEx added questions. This will make sure you aren't duplicating efforts, that you are ready to move quick once the application stabilizes, and that you don't waste your own time.

This is a really unfortunate situation as FedEx is unable to trust their own data until this is fixed. There is currently no way that FedEx can reliably trust what they have, given the significant issues applicants are having providing accurate and reliable information. Good Luck and check back for more as this evolves.

Actually, just think of this within the context of a standard FedEx rollout of anything IT related. FedEx is taking this opportunity to expose new applicants as early as possible to the wonders of IT in Flight Ops so they can lower their expectation accordingly.

I decided to start from scratch, and I was employed in a position from 7/14 to 12/15 and I get this error:



I am forced to put May 1, 2016 for some reason.

This is the exact problem. The existing application has a rather long list of glitches that require an applicant to provide incorrect data in order for the information to save without an error. Pair this with data being saved is getting dumped days later and you have a significant issue. The problem comes in that there is no way to complete the existing application without providing untruthful data that will have to be corrected at a later date. Not so much a concern about getting dinged for lying, more an issue with wasting loads of your own time and duplicating efforts.

Wow. I could probably fix this, but alas, I am currently a software engineer at Boeing and not FedEx.

I could fix it with the dev console in Chrome, since it is just a JS validation, but I am not sure the backend would take it. I don't want to risk it.

Could be interesting

Thanks, y'all. Richard from Pilot Credentials out of Austin, Texas. I thought I might chime in to this thread. The FedEx conversion to a new HR system based on the Workday platform has caught a lot of us by surprise. I recommend giving them some time to sort things out. They seem to be struggling with technical difficulties and my understanding is most users are experiencing similar issues. It also seems the data migration from the Pilot Credentials database has technical issues as does their tech support capabilities.

My guess is that high traffic from unsuccessful attempts to re-enter profiles is compounding the problem. We all anticipate further instructions either as a maintenance page message or email. As a result Data Sync for FedEx has been disabled until that time as well. If you have a Pilot Credentials Global Profile keep it up-to-date. You can generate a PDF resume quickly with organized flight hours. We hope to resume data transfer capabilities one way or another after things settle in. Take care.
-RBT

Same here. Very frustrating.

After uploading my resume, I opened it from their website and noticed it was cut off about half way down. Spent hours trying to rearrange and reupload...no luck. Anyone else have this issue?