surglogs

Mid-level Mobile Platform Engineer (iOS-first)

Show

Surglogs is an award-winning software solution digitizing and streamlining regulatory compliance for ambulatory surgery centers and healthcare facilities across the US.

We are looking for ambitious and passionate individuals who enjoy building relationships with clients to join our quickly growing team and lead the movement together!

About the Position:

Place of work: Remote (SK/CZ) or from our office in Bratislava

Your position here is a bit special.

📱You're the one person who owns our mobile platform: its quality, its roadmap, its direction. Starting with iOS and extending to Android. You lean on a senior (Martin) for the hard architectural calls.

Why we're hiring

Our mission is to be a world-class engineering team that ships the best possible product with a focus on security. The company exists to make healthcare compliance stress-free. Our mobile apps are where that promise lands for clinical staff who pull out a phone mid-shift, so the iOS surface has to be solid, fast, and trustworthy.

We're hiring a mobile engineer to own our mobile platform. iOS first, because that's where the need is sharpest right now, and Android as part of the same remit over time. Strong iOS and Swift is the baseline. Android and Kotlin are a real plus, and if you don't have it yet, you're the kind of person who picks it up fast. We care about ownership and craft, not your title or your years.

12 months from now, if this hire works out, this is true at Surglogs:

  • iOS is no longer a single point of failure. Standards are written down, there's a visible tech-debt roadmap that actually moves, and nothing critical lives only in one person's head.

  • Mobile quality sits on par with our other platforms. Change failure rate, code complexity, test reliability. The numbers are healthy and you keep them there.

  • You ship outcomes, not tickets. You care whether a feature gets adopted after it launches, not just whether it merged. That's focus on outcomes, not outputs.

  • You're contributing on Android too. You didn't stay in an iOS-only box. You know the Android codebase well, and you use AI tooling to work efficiently as an Android developer.

  • You build with AI tools and own what they produce. You leverage agents, you don't lean on them.

    • What you'll own

    You won't get a Jira backlog to grind. You own outcomes, and you decide with the team how to get there. 💪

    1. The quality of the mobile apps you ship. You own the whole cycle. Right-sized merge requests. Every bugfix linked to a test. When something breaks in production, you are the person to debug it.

    2. The mobile platform's health and tech-debt roadmap (iOS first). Written down, visible to the team, and prioritized because you made the case for it, not because it caught fire. You won't carry this alone. Martin is there for the hard architectural calls, and you'll grow into more of it over time. But you drive it.

    3. Feature outcomes. Question the "why" before you build the "how". You stay with a feature past launch and care whether people actually use it.

    4. The whole platform, not one OS. iOS is where you start because it needs you most. Android is part of what you own. If you're already strong there, great; if not, you ramp fast and the team stops being one-platform-deep in any single person.

    Where you spike

  • Solid iOS and Swift craft. You can own an iOS feature end-to-end and raise the quality bar around it, not just add code to it. We are asking that what you ship is correct, tested, and yours. You enjoy leaving a codebase cleaner than you found it.

  • A Product Engineer's brain. You think about the user and the business outcome, not the ticket. You'll challenge a spec when you see something the team is missing. Lean means limited but fully functional, never half-built.

  • AI-native taste. You use AI tools daily and have real opinions about where they help and where they bite. You take the principle seriously: leverage AI agents, don't rely on them. You own what your agent produces

  • Self-driven, and you talk early. You can carry important-but-not-urgent work without being pushed. Going quiet when things get hard isn't autonomy. It's a risk.

    • If you're excited to navigate compliance and ship AI thoughtfully where it actually matters, you'll have a lot to do.

    Who you are

    If two or more of these don't sound like you, this probably isn't the right fit. Better to learn that early.

  • 🚀 You take extreme ownership. If you spot an issue, you take it on. You don't wait for someone else to flag it or fix it

  • 💙 You think "I want to build something users care about" before "I want to use the latest framework."

  • 📱 You're a partner to the team and to the product, not a contractor finishing tasks. You'll step out of your platform lane to help finish a sprint goal, if the vision needs it

  • 🚢 You've shipped a lot using AI tooling. You can compare with specifics where AI helped vs. hurt. You own what your AI agent produces. If it ships under your name, the bug is yours, not the model's

  • 📖 You read code, you read docs, you read industry writing, and you bring it back to the team. When you don't know something, you find out fast, and teach others.

  • 💭 You disagree well. You push back on a product decision when you see something the team is missing, and you do it without making it personal.

  • 💬 You live feedback culture. You give feedback that's honest but polite. You ask for it often. You assume positive intent. You don't withhold feedback to be "nice."

  • 🖊️ You default to async. You write things down. You document the why behind decisions. You prefer a public channel and a thread to a DM, because the rest of the team needs to find what you decided.

  • 🧑‍💼 You're flexible. You have a clear sense of how things should work, but you adapt when the project needs something different. This isn't a 9-to-5. Some evenings you'll be in meetings, but you're not up against hard deadlines.

    • What we're explicitly not asking for

    We know the bar is high. Here's what isn't on the list.

  • Not hung up on your level or title. We hire for ownership and craft, not the line on your CV.

  • Not asking for "X years of Swift." We use Swift on iOS. If you've shipped real iOS work and you can own a feature and its quality, that's the signal. We'll look at the real thing in a hands-on session, not count years.

  • Not asking for an iOS purist. If multiplatform feels beneath you, or you'd resent learning Android, this is the wrong role. We want someone who sees more than one platform as upside.

  • Not asking for someone who waits for tickets. This isn't a ticket-execution role and it never will be.

    • Our mobile platform scoreboard

  • Change failure rate. How often a change to master breaks something a user notices. Lower is better.

  • Deployment frequency - how often we ship safely. More frequent, smaller releases over big-bang ones.

  • Test reliability - flaky tests erode trust in the suite; we keep it green and in ReportPortal, not just green.

  • Code complexity - debt you pay every time you touch the code. We watch it so it doesn't creep.

  • Build health - build times and pipeline stability, because slow or red builds tax everyone.

    • Our Stack

  • iOS: Swift, SwiftUI, UIKit

  • MVVM + Coordinators with a clear service layer.

  • Swift Package Manager with 28+ internal modules.

  • Tests in XCTest plus CucumberSwift BDD acceptance suites, reported to TestRail (and ReportPortal), internal testing with Firebase.

  • Canary releases with Optimizely

  • Analytics via PostHog, error reporting via Sentry.

  • Platforms fully ready for AI/agentic development. AI tools integrated: GitHub Copilot / Claude Code, CodeRabbit for reviews.

  • GitLab, automatic deployment (CI/CD), Renovate for automatic dependency updates.

  • Latest version support only: iOS 16 + Swift 5.9 + Xcode 14.3.1, Android 16 (API 36) + Kotlin 2.3.21

    • How the interview works

    We designed this on purpose. We hate interview processes that feel arbitrary.

    1. Pre-screen call with Bea. A real conversation about your background, what you're looking for, and the basics. No trick questions.

    2. Hands-on technical session + Design/System Thinking Session. We send you the topic and a small assignment a few days ahead. We'd rather see how you think about a problem you've had time to chew on than how you perform under cold-start pressure. It's hands-on: code, your AI tools, your IDE, whatever you actually use day-to-day. You don't need to know everything. What matters is how fast you find out.

    3. Culture-fit round with a small group from the team. We're checking the same things you are. Can we work together. Is this a day-to-day you'd thrive in.

    4. A short CTO call

    We'll tell you upfront who you'll meet at each stage and why. No surprises.

    Compensation

    We determine compensation based on each candidate's unique background and the needs of the role. Factors such as experience, skills, qualifications, location, professional accomplishments, internal equity, and business priorities all play a role in the final offer, which may differ from the advertised pay range.

    Base Salary Range

    €36.000—€48.000 EUR gross/year

    Benefits and Culture

    Our values & principles:

    • Outcomes, not outputs. We solve real problems for real users. Closed tickets aren't the scoreboard.

    • Lean, but never half-built. The smallest unit shipped properly beats the big unit shipped sloppy. Lean ≠ crappy UI.

    • Continuous improvement. Push past the comfort zone. Root-cause with five-whys. Feedback is how we get better, fast.

    • Fearless and blameless. Try, ship, learn. We focus on how things broke, not who broke them. Fear kills creativity, blame kills honesty, so we don't tolerate either.

    • Async by default. Decisions live in docs, not DMs. Public over private.

    • Agile as a mindset, not a ritual. Flexible, team-first, knowledge shared. The 12 principles, not the ceremony theater.

    How we work together:
    Remote-first, anchored in Central Europe. We mix Slovak, Czech, and English in the team chat. Anything that touches product docs, code reviews, or the U.S. team happens in English, so nothing gets lost in translation between offices.

    We’re a close-knit team of about 20 engineers. While we don't pretend to match the base salaries of companies with 10x our revenue, we easily outshine them when it comes to our benefits, and culture. Here is what we bring to the table:

    • Remote-first. Work from anywhere, any timezone, as long as you overlap with the team enough to keep things moving. Most companies are moving away from remote working. We're not.

    • Flexible and trust-based. We care about what you ship, not what hours you log. No clock-in, no clock-out.

    • Self-development budget. No fixed cap. If you find a conference, course, or book that makes sense for your work, talk to Bea and we'll figure it out, case by case. Conference time during the week counts as work, not vacation.

    • Company laptop.

    • ESOP: An opportunity to co-own the company

    • The smaller stuff: bookclub, internal meetups, company retreats, and our merch.