Software Engineer III – Platform Services

Other Jobs To Apply

<p style="min-height:1.5em"><strong><u>Software Engineer III – Platform Services</u></strong></p><p style="min-height:1.5em"><strong>Position Summary</strong></p><p style="min-height:1.5em">This is a mid-level individual contributor on the Platform Services team. This role focuses on building and maintaining the foundational systems that power identity, authentication, and integration capabilities across MeridianLink's multi-product SaaS platform.</p><p style="min-height:1.5em">Platform Foundation is a small, high-output team. It runs lean by design, with the expectation that the right combination of engineering depth and AI-assisted tooling can achieve platform-scale impact with a minimal footprint. Engineers here are expected to understand the systems they own deeply enough to identify what needs to be built next, flag problems before they become incidents, and ship with the kind of care that keeps downstream product teams unblocked.</p><p style="min-height:1.5em">The immediate focus of this role is federated identity and authorization infrastructure. The work ahead involves building and extending the platform services that product teams depend on to authenticate users, enforce authorization, and manage access at scale. A strong candidate for this role has hands-on experience with OAuth 2.0, OIDC, SAML, and JWT, understands how authorization frameworks work in practice, and knows what it takes to integrate identity services into real-world applications.</p><p style="min-height:1.5em">Equally important is how this person approaches their craft. Platform Services run with AI-assisted workflows as a first-class part of how software gets designed, validated, and delivered. Engineers on this team are expected to be fluent users of AI development tools, not just passive consumers of them. If you want a role where AI is a force multiplier and not an afterthought, this team is built around that idea.</p><p style="min-height:1.5em">This is a fully remote role.</p><p style="min-height:1.5em"><strong>Key Competencies</strong></p><p style="min-height:1.5em">At this level, competencies reflect technical ownership of well-defined work, growing independence, and the beginning of a mentorship posture toward more junior engineers.</p><p style="min-height:1.5em"><strong>Technical Execution & Delivery</strong></p><p style="min-height:1.5em">Delivers features end-to-end with limited guidance; takes a scoped requirement through design, implementation, testing, and production release</p><p style="min-height:1.5em">Independently identifies edge cases and failure modes within the scope of assigned work</p><p style="min-height:1.5em">Writes clean, maintainable code and participates actively in code review with constructive, specific feedback</p><p style="min-height:1.5em">Proactively surfaces blockers or ambiguities rather than waiting for check-ins</p><p style="min-height:1.5em"><strong>Identity & Authorization Systems</strong></p><p style="min-height:1.5em">Applies practical knowledge of federated identity standards including OAuth 2.0, OIDC, SAML 2.0, and JWT</p><p style="min-height:1.5em">Understands how authorization frameworks function: how they enforce policies, how they integrate into upstream and downstream services, and how access decisions are modeled and evaluated</p><p style="min-height:1.5em">Reasons clearly about token lifecycle, session management, and the security implications of identity design choices</p><p style="min-height:1.5em"><strong>Integration Engineering</strong></p><p style="min-height:1.5em">Understands the mechanics of connecting distributed services in a multi-product platform environment</p><p style="min-height:1.5em">Builds and maintains integrations that are observable, fault-tolerant, and respectful of downstream consumers</p><p style="min-height:1.5em">Writes and works with API contracts (REST, event-driven patterns) with attention to versioning and backwards compatibility</p><p style="min-height:1.5em"><strong>AI-Forward Engineering</strong></p><p style="min-height:1.5em">Actively uses AI-assisted development tools (Claude Code, Codex, etc.) to accelerate design, implementation, and validation</p><p style="min-height:1.5em">Participates in building and improving AI-assisted workflows and evaluation harnesses that improve the team's delivery throughput</p><p style="min-height:1.5em">Stays current on how AI tooling is evolving and brings new approaches to the team where they apply</p><p style="min-height:1.5em"><strong>Craft & Professionalism</strong></p><p style="min-height:1.5em">Writes tests with enough coverage to catch regressions without over-engineering the test suite</p><p style="min-height:1.5em">Contributes to operational health: monitors what they've shipped, responds to issues, and follows incidents to resolution</p><p style="min-height:1.5em">Documents what needs to be documented; keeps tribal knowledge out of individual heads and into shared systems</p><p style="min-height:1.5em"><strong>Expected Duties</strong></p><p style="min-height:1.5em"><strong>Identity & Authorization Platform Development</strong></p><p style="min-height:1.5em">Build and extend platform services that manage federated identity, authentication flows, and authorization enforcement across MeridianLink products</p><p style="min-height:1.5em">Implement integrations with the centralized identity platform, including token handling, session management, user provisioning, and tenant configuration</p><p style="min-height:1.5em">Support product teams through their integration process: help them understand the platform's contracts, debug integration issues, and navigate edge cases in multi-tenant identity behavior</p><p style="min-height:1.5em">Build the tooling, documentation, and examples that make those integrations repeatable and self-service over time</p><p style="min-height:1.5em"><strong>Integration Engineering</strong></p><p style="min-height:1.5em">Design and implement backend service integrations using common patterns (REST APIs, event-driven messaging, webhook delivery) in Python</p><p style="min-height:1.5em">Build with multi-product and multi-tenant scenarios in mind: data isolation, tenant-scoped configuration, and cross-product user identity are properties of the platform, not edge cases</p><p style="min-height:1.5em">Participate in API design reviews with attention to clarity, contract stability, and developer experience for downstream consumers</p><p style="min-height:1.5em"><strong>AI-Assisted Delivery</strong></p><p style="min-height:1.5em">Use AI development tools as an active part of the delivery workflow: for code generation, design validation, test scaffolding, and investigation</p><p style="min-height:1.5em">Contribute to AI harness development that helps the team move faster and catch regressions without proportionally increasing manual effort</p><p style="min-height:1.5em">Share what's working across the team; help establish repeatable patterns for AI-assisted engineering on Platform Foundation</p><p style="min-height:1.5em"><strong>Engineering Craft & Observability</strong></p><p style="min-height:1.5em">Write tests at the unit, integration, and acceptance level appropriate to what's being built</p><p style="min-height:1.5em">Instrument services for observability: structured logging, metrics, and alerting that make production behavior visible and actionable</p><p style="min-height:1.5em">Participate in on-call rotations and follow incidents through to root cause and remediation</p><p style="min-height:1.5em"><strong>Collaboration & Growing Others</strong></p><p style="min-height:1.5em">Participate in design discussions and code reviews; give and receive feedback constructively</p><p style="min-height:1.5em">Provide mentorship and review support to L1 and L2 engineers on the team</p><p style="min-height:1.5em">Contribute to internal documentation, runbooks, and onboarding materials</p><p style="min-height:1.5em"><strong>Qualifications: Knowledge, Skills, and Abilities</strong></p><p style="min-height:1.5em"><strong>Required Qualifications</strong></p><p style="min-height:1.5em"><strong>Experience:</strong></p><p style="min-height:1.5em">3-5 years of professional software engineering experience, with demonstrated ability to own and deliver features independently in a production environment</p><p style="min-height:1.5em">Hands-on experience building backend services in .NET or Python, including RESTful API development</p><p style="min-height:1.5em">Demonstrated experience implementing or integrating with federated identity systems using OAuth 2.0, OIDC, SAML 2.0, and/or JWT in production applications</p><p style="min-height:1.5em">Practical understanding of authorization frameworks: how policies are modeled, enforced, and integrated into application and platform services</p><p style="min-height:1.5em"><strong>Technical Skills:</strong></p><p style="min-height:1.5em">Proficiency in .NET or Python for backend service development; familiarity with modern API frameworks (e.g., .NET 9+, FastAPI, etc.)</p><p style="min-height:1.5em">Working knowledge of identity protocol mechanics: authorization code flow, token introspection, claims-based access, assertion handling, and SSO logout behavior</p><p style="min-height:1.5em">Experience with multi-tenant SaaS integration patterns, including tenant-scoped configuration and user identity across application boundaries</p><p style="min-height:1.5em">Familiarity with cloud platforms (AWS preferred), including relevant managed services for networking, compute, and secrets management</p><p style="min-height:1.5em">Proficiency with standard development tooling: Git, CI/CD pipelines, containerization (Docker), and automated testing</p><p style="min-height:1.5em">Active use of AI-assisted development tools (Claude Code, Codex, or equivalent) as part of a daily engineering workflow</p><p style="min-height:1.5em"><strong>Preferred Qualifications</strong></p><p style="min-height:1.5em"><strong>Identity & Authorization Depth:</strong></p><p style="min-height:1.5em">Prior experience working with a commercial or open-source identity platform (e.g., an OIDC provider, IAM system, or enterprise SSO solution) in an engineering capacity, not just as a consumer</p><p style="min-height:1.5em">Experience modeling and implementing fine-grained authorization: RBAC, ABAC, or policy-based access control systems</p><p style="min-height:1.5em">Familiarity with token security considerations including signing, expiration, revocation, and safe storage patterns</p><p style="min-height:1.5em"><strong>Regulated or Platform Environments:</strong></p><p style="min-height:1.5em">Prior experience building software in a financial services, fintech, or otherwise regulated technology environment</p><p style="min-height:1.5em">Experience building internal platform capabilities used by other engineering teams, not just end-user-facing features</p><p style="min-height:1.5em">Exposure to SOC 2 or similar compliance frameworks from an engineering perspective</p><p style="min-height:1.5em"><strong>AI-Assisted Engineering:</strong></p><p style="min-height:1.5em">Experience contributing to AI harnesses, evaluation pipelines, or tooling that improves engineering workflow throughput</p><p style="min-height:1.5em">Comfort using AI tools not just for code completion but for design exploration, test generation, and investigation</p><p style="min-height:1.5em"><strong>Education:</strong></p><p style="min-height:1.5em">Bachelor's degree in Computer Science, Software Engineering, or a related technical discipline, or equivalent demonstrated experience</p><p style="min-height:1.5em"><strong>What Success Looks Like</strong></p><p style="min-height:1.5em">A successful hire integrates quickly into the team's delivery rhythm, picks up the identity and integration domain with focus, and begins shipping production contributions within the first weeks. Within the first few months, they have built enough context to work largely independently on scoped features, are participating meaningfully in code reviews, and have demonstrated the kind of operational ownership -- shipping, monitoring, and standing behind their work -- that keeps a small team running well.</p><p style="min-height:1.5em">Over time, impact is measured by the quality and reliability of what they've shipped, how much they've reduced the platform's dependence on tribal knowledge, and how effectively they've supported product teams integrating with the identity platform. Engineers who thrive here do so because they care about the craft, want to operate at the leading edge of AI-assisted development, and are motivated by building infrastructure that other teams depend on to deliver real product value.</p><p style="min-height:1.5em"></p>

Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...