Software Engineer III

About the role

This role focuses on shared platform services for several dating brands. You will build and reuse foundational capabilities across a portfolio of consumer applications. The work supports a strategy where features are created once and deployed broadly.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Foundational backend services and APIs are created and maintained for multiple consumer brands such as Match, BLK, and Chispa.

Platform requirements are converted into shared solutions through close collaboration with Product, Design, Android, iOS, and Web engineers.

Platform scalability, reliability, and testability are maintained as user demand grows.

Opportunities to expand into mobile feature development may arise to address high-impact areas.

Requirements

Hands-on experience building backend services in C#/.NET, including designing and consuming REST APIs and JSON data contracts, is required.

Solid understanding of microservices and event-driven or distributed architecture (for example, Kafka) and reliable service communication at scale is necessary.

Relational databases such as SQL Server and Postgres are worked with, data modeling and query/performance optimization are handled, and caching (such as Redis) is used when appropriate.

Strong grasp of software design patterns, SOLID principles, and clean architecture is applied, combining functional and object-oriented programming patterns.

Testable, maintainable code is written, dependency injection is used, and unit/integration testing along with test-driven development and CI are valued.

Complex or ambiguous requirements are broken down, scope is estimated before starting, and problems are solved autonomously and creatively.

Technical and non-technical communication is handled clearly, and effective partnership with Product, Design, QA, and platform/mobile engineers is demonstrated.

Ownership of craft is taken, own work is validated without relying solely on QA, and drive for continual improvement in skills and codebase is maintained.

Experience with or genuine interest in learning mobile development (Kotlin/Android or Swift/iOS) is present given the role's cross-platform potential.

AI-assisted development tools such as Claude Code are used to accelerate delivery while maintaining code quality and correctness.

Nice to have

A Bachelor's or Master's degree in Computer Science or a related technical field is held.

Shared platform services used by multiple teams, applications, or brands have been built.

Mobile features have been shipped on Android using Kotlin or on iOS using Swift.

Observability tooling such as OpenTelemetry, Grafana, or similar systems is used.

Containerized environments with Docker and Kubernetes are worked with.

Practical notes

a Dallas-based role with a hybrid schedule of three days per week in the Texas office. Work authorization is required. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Platform and backend services enable multiple consumer applications to function consistently. Collaboration across mobile, web, and QA teams is central to delivering shared capabilities. The team uses modern development practices, including automated testing and continuous integration. Engineers write reliable, maintainable code and drive their own professional growth. The role involves cloud-native systems that scale to support many users and brands.