About Me
Hi, I’m Sophie (ERMFox) — a Backend / Full-Stack Software Developer with a focus on building reliable services, clean APIs, and maintainable systems. I enjoy working on projects that involve real-world constraints like validation, automation, deployment workflows, and long-term maintainability.
What I focus on
My main interest lies in backend engineering and full-stack development: designing REST APIs, structuring applications cleanly, working with databases, and ensuring that systems behave predictably in production-like environments.
Many of my projects emphasize engineering practices such as validation, error handling, modular architecture, testing, CI/CD pipelines, and deployment strategies like blue-green or canary releases.
Background
I completed an apprenticeship as a software developer (EFZ) and have experience across backend development, web applications, and infrastructure-related topics such as containerization and deployment automation. Through both school and personal projects, I’ve built systems ranging from REST backends to CI pipelines and full web applications.
Alongside software development, I spend a lot of time with game design and worldbuilding. This background strongly influences how I think about software: I naturally consider system boundaries, edge cases, user experience, and long-term structure when designing applications.
Skills
- Backend: Java, Spring Boot, REST APIs, validation, authentication basics, error handling.
- Data: SQL, relational data modeling, JPA/Hibernate, schema design.
- Engineering practices: Clean Code, modular architecture, documentation, testing mindset (JUnit, integration tests).
- DevOps basics: Docker, Docker Compose, CI/CD (GitLab CI, GitHub Actions), container registries.
- Full-stack: Building end-to-end features, integrating frontend with backend, pragmatic UI work using Thymeleaf and Tailwind.
What I’m looking for
I’m currently looking for a role as a Backend Developer or Full-Stack Developer where I can contribute to real systems, continue learning from experienced engineers, and gradually take on more responsibility.
I especially value teams that care about code quality, clear communication, and building software that remains understandable and maintainable over time.
A bit more about me
I care deeply about building things that feel solid and thoughtfully designed — whether that’s an API, a deployment pipeline, or a creative system. I tend to be detail-oriented, ask a lot of “what happens if…” questions, and enjoy refining systems until they feel clean and coherent.