Back to Jobs

Software Engineer

Not Disclosed

Job Description & Details

This is a solid, long-term contract role at a massive financial institution that's been around for over a century. You'll be working in a hybrid setup out of Irving, TX, building systems that scale for millions of users while navigating enterprise-grade compliance. If you like stability mixed with complex technical challenges in the fintech space, this gig is worth your time.

What You'll Actually Be Doing

You'll spend your days tackling backend and full-stack challenges, collaborating with cross-functional teams to deliver moderately complex engineering initiatives. Expect to analyze tricky technical roadblocks, review deliverables, and write code that integrates seamlessly into a heavily regulated ecosystem. It's less about building shiny greenfield apps and more about maintaining, scaling, and modernizing robust financial infrastructure.

The Core Tech Stack

You need to bring a solid foundation in Java and the Spring framework, alongside frontend chops in either React or Angular. On top of that, having about two years of Python under your belt is non-negotiable for this team. If you've touched Google Cloud Platform, OpenShift, Kubernetes, or Spark, you'll definitely stand out, but your core bread-and-butter must be enterprise Java and modern web frameworks.

Interview Expectations

Expect the hiring team to grill you on how you handle concurrency and dependency injection in Spring, so be ready to talk through thread-safety and bean lifecycles in real-world scenarios. They're also going to test your system design intuition, specifically how you structure scalable APIs that interface with legacy financial databases. They aren't looking for textbook definitions; they want to know how you troubleshoot bottlenecks when production goes sideways under heavy load.

Application Advice

To get past the automated screeners, your resume needs to explicitly feature 'Java', 'Spring', 'React', 'Angular', and 'Python' right at the top in your experience bullets, backed by your total years of engineering. Don't just list the technologies—highlight how you used them to solve performance problems or deliver enterprise features. Make sure your total experience hits that 4+ year mark clearly, and if you have any exposure to GCP or Kubernetes, weave those in as secondary wins.