Senior Software Engineer, Java/Scala/Play Platform Remote Preference
-
Software Development
Job Description & How to Apply Below
- Remote with Preference shown to Phoenix, Philadelphia and Northern Virginia.
- Not a qualification I just can't find why Linkedin keeps saying "Must be located in commutable distance to Greater Phoenix Area, United States"
- Must have Play framework, Scala, MongoDB/Document DB (moving from Mongo to Document)
Bring the cape. The people we help need us every day.
Some heroes stop the train. Others rebuild the bridge while the train is still running across it. This job is the second kind, and it takes a steadier hand.
Our Java and Scala platform has been doing serious work for a long time. Behind it are real people: a missing child someone is still looking for, a family waiting on a call, an agency counting on the record being right. The platform can't go down while we modernize it, and it can't get a single access rule wrong. We need someone who can make it better without ever making it worse.
WHOWE ARE
Safience builds identity intelligence for public safety. We help identify two kinds of people: those who pose a real threat, and those who need to be found. Every record we work from is sourced from law enforcement. We don't scrape the internet. We don't follow people. There is no video. Not recorded, not streamed, not ever. If law enforcement isn't already looking for you, you pass through and leave no trace.
No alert goes out because a machine said so. Trained analysts review every identification before anyone gets a call. Every good hero has a code. That's ours.
WHY THIS ROLE MATTERSSome of the most important code you'll touch decides who is allowed to see which record. That's where civil liberties live in software. A slow page is a bug. A missing access filter is a breach of trust. You'll treat both accordingly.
You'll report to our Director of Product Architecture and own long-lived, business-critical Play Framework applications in Java and Scala, backed by MongoDB-compatible document stores (Amazon Document DB) and running in containers on AWS ECS/Fargate across multiple accounts.
WHAT YOU'LL DO- Maintain and extend Play Framework 2.x applications in Java and Scala: controllers, actions, filters, and Twirl templates.
- Work cleanly within Guice dependency injection: correct scoping, eager bindings, and none of the lifecycle traps that come from injecting into objects built outside the container.
- Refactor legacy code in small, safe steps. Pin down behavior with tests first, then change it.
- Lead our framework and library modernization. Inventory every dependency, direct and transitive, with its support status, known vulnerabilities, and upgrade blockers. Turn that into a sequenced, risk-ranked plan, then execute it one major version at a time, using feature flags or strangler-style replacement where a big-bang swap isn't safe.
- Make build-versus-replace calls out loud and record them as architecture decision records.
- Put guardrails in place so the stack never drifts again: automated dependency updates, vulnerability scanning in CI, and a supported-versions policy.
- Own the data access layer: entity mappings, references, query construction, and compatibility with Document DB's differences from MongoDB.
- Hunt down slow pages end to end. Read profiler output and explain() plans, find the collection scans, N+1 fetches, and in-memory aggregation, and replace them with indexed queries and server-side aggregation. Faster than a speeding bullet is the goal. Proving it with before-and-after numbers is the job.
- Design indexes and denormalization strategies, and keep downstream search sync pipelines healthy.
- Package JVM apps as hardened container images on ECS/Fargate and tune heap, GC, and resource limits.
- Troubleshoot JVM networking in containers, including dual-stack address selection, DNS caching, and TLS trust stores.
- Write and review Terraform for application infrastructure across multiple AWS accounts.
- Own observability: structured logs, JVM and query metrics, and alarms that catch regressions before users do.
- Maintain the authentication and authorization logic that controls who sees what. Treat secrets, personal data, and access filters as correctness-critical. Never remove a filter until you've proven it's redundant.
- Lead design reviews, write clear design docs and incident reports, and set team standards for base images, query patterns, testing, and runbooks.
- You own a cape. You've leapt a ten-year-old codebase in a single bound and left it better than you found it. You also know the real superpower with legacy systems isn't speed. It's…
Position Requirements
10+ Years work experience(If this job is in fact in your jurisdiction, then you may be using a Proxy or VPN to access this site, and to progress further, you should change your connectivity to another mobile device or PC).
View / Apply for Jobs
Matching My Jurisdiction