Lender Processing Services Employer Reviews

My day at Lender Processing Services consist of answering and sending out daily email corresponses to Inspectors. At my designated date and time I will pull our department daily work and distribute evenly among each member to complete. I will also perform audits on specified inspectors per my manager request.

Active Directory Engineer: ADFS SSO
A member of the Active Directory team
ADFS 2.0 SSO SME

An interesting position. Software support for FC, BK, REO
Interesting characters in the office.

Cliques. Manager was close friends with employees. Serious attityde from girl who was too busy unwilling and had no inclination to train someone much older than her.

As a company, they did not allow raises except in extreme circumstances and there is no mentoring program to assist in developing associates.

Hours of work were from 5:00 PM to 9:30 or 11:00 PM
My main responsibility was to find and upload electronicly scanned legal documents to a company database for access by law firms. Management was fair but there was a great deal of favoritism. Co-workers were kind and friendly. The job was not difficult. The most enjoyable aspect of the position was – more... the independent nature of it. As long as your production numbers were adequate, there was not alot of supervision. – less

Loved this company. Would have taken a bullet for anyone in management there, as well as for any of my co-workers in LPS.

But the company is in Florida, and I live in Savannah, so the commute was not optimal long-term.

In the first 5 years I was with this company, I found the environment to be exceptional, with room to advance as well as pay increases for all employees based on merit. After 5 years, management changed and so did the opportunities. No pay increases and no advancement, but rather lay offs. My portion of the company was sold in 2012 to a competitor

Leader in techonology industry, great company to work for.

Production driven enviroment
the hardest part of the job was helping new employees learn the job and not getting the acknowledgment or advancement.

On a typical day, I would come in and start replying to emails and phone messages. As soon as I was caught up on that, I would open orders that were assigned to my unit. I would open approximately between 300-500 order per day (including manual orders). I had a good relationship with my manager, which made the job much more pleasant. Her flexibility – more... made life much easier. My co-workers were friendly. The most enjoyable part of the job was the fact that I would get to work remotely, the majority of the time. – less

On a typical day I would run a queue and color coordinate the downloaded spreadsheet based on the documents requested via intranet from our clients. I would also have to run a spreadsheet of follow-ups for the day in order to satisfy attorneys and trustees to reach their deadlines. Prior to uploading the documents I would have to proof them further – more... for accurate recording information and if necessary research where copies of the originals are. Reading emails had to be done every 2 to 3 hours to keep up with the demands from clients that took priority because of deadlines or follow up emails on deadlines. Some documents had to be requested from on-site vendors. I learned how to focus without being distracted at home and how to read mortgage documents for recording and title accuracy. Being WAH (work at home) employee, there were about 2 co-workers that would contact me because we worked the same client but management was not in touch very often only during conference calls, deadlines or follow-up urgent issues. The hardest part of the job was not being able to walk across the isle to get pertinent information when emails were not being responded to and the most enjoyable was working at home. – less

The positions within LPS are generally not hard - they're data entry mostly, and pretty easy to get away with daydreaming all day. The downside is that while they say there's all these opportunities for promotions and advancement, but there are surprisingly few. And when there are, they aren't always posted on the internal job listings.

The Mendota – more... Heights building is also cold as hell, and it would be quite nice if we could do something about that.

Typical day: Pull my assigned workgroup of states or firms I review files for and start plugging away at them. Review the files to determine what's going on with the foreclosure and where the attorneys are in the process. Contact the firms (email, phone, internal communications) and advise them of what you've found in your review, and how they can proceed on the file to help expedite the process. Rinse and repeat for 8 hours day, as an attorney liaison.

They don't like to give raises because they give a monthly commission based on productivity of you and your team. You have to be really long overdue for one to really get it - and then you'll still have to fight for it. – less

The workplace is average, however the corporate structure is centered around gains and losses.

Management policies were impossible to map into real life scenarios.
No management presence on site for correct probe of productivity, and adequate assessment on working environment, and working condition. The job sites were remotely managed, where due dates were coming out of hats with no consideration to engineers specialty and skill sets.

Most likely – more... this could have been as a result of economic downturn at the time. – less

Capitalizes off of the foreclosure market and others hard times.

This is a strict corporation. Online training programs are provided along with opportunities for advancement. The core team of project individuals were cordial and helpful. Deadlines were intimidating yet manageable.

Managing BGP And MPLS Wan circuits for numerous banks and mortgage clients.
• Managing Ace Module switches
• Configuring Cisco routers and switches 6500, 3600, 2900, 2800, 3700, series equipment.
• Troubleshooting protocols such as EIGRP, and Static routing.
• Managing Ace Module switches
• Configuring Cisco routers and switches 6500, 3600, 2900, 2800, – more... 3700, series equipment.
• Troubleshooting protocols such as EIGRP, and Static routing.
• Troubleshooting LAN and WAN circuit and tunnel outages.
• Packet sniffing using infinistream console
• Troubleshooting firewall and IPS/IDS traffic ACL’s using Smart Domain Manager
• Using CA Spectrum to identify any Voip, Security, WAN, or LAN issues.
• Creating severity tickets depending upon the network outages.
• Escalating issues for company Service Level Agreements. – less

Personally, I kind of wish I still worked here, though there are still good reasons to have left. The code base is very secure and managed by a fine group of intelligent architects. Mostly everything is very neatly organized and accessible, making development work a breeze. Their suite is also particularly advanced, though not too difficult to work – more... with from a coding perspective. It is evident that a great deal of forethought and planning goes into the look and feel of their application, and personally this is something that I found I could take pride in as a developer. I was usually very satisfied with my work and its reception.

Work culture was a lot of fun. People are generally very friendly and easy to get along with. If you're a nerd, you're going to have a blast with these guys, and even if not there are plenty of varied interests throughout the company that you shouldn't have trouble finding a group of people to rely on to make the day a little more interesting. Most managers are down to the level, except the head supervisor for the QA department tends to run his department as though he's a drill sergeant. Other than that, as a software developer I was able to joke around at a personal level with my direct manager, my department's supervisor, and the head of product development.

The downsides included frequent unpaid overtime (at times, 50+ hours/week) and sales biting off more than they could chew. There were times when sales would make promises to customers that the application was capable of doing something that it couldn't, and then we would have to rush to make it do that, but I assume that happens everywhere. On the plus side, developers are often brought into business meetings alongside the BAs and customers so they can hear requests first-hand and make recommendations for spec changes or clarifications, and many BAs were willing to continue working closely with developers throughout the life of the project. All in all, a very responsible organization that took success and failure as a whole rather than pointing the finger at individuals.

Before I left, there was a large political upheaval that cost some senior employees their jobs and caused a lot of unrest and suspicion amongst the ranks. This, plus boredom with the Sharon area and low wages compared to Pittsburgh, are what caused me to leave. From what I've heard from colleagues since, more of the people I've respected have left, and there are still concerns about the health of the organization under the new CEO. While I would personally recommend LPS as a great company to work for - especially if you're looking for a great quality code base and thorough QA - I wouldn't personally go back just because of the area and uncertainty of the current political situation. – less

I have tons of experience and am a great productive worker, type 59 wpm and this HR twit decided I wasn't good enough. Was I too old? too fat? too friendly? They hire anybody but I"m not good enough to take their low pay and terrible hours and depressing work?