Full Stack Software Engineer (Angular/Python)

Germany | Sept. 4, 2026

Report as Closed

Company: Lobster DATA GmbH

Country: Germany

Type: Onsite

Employment: Full Time

Description:

Job description:

This position is advertised as a hybrid model, with regular visits to our headquarters in Tutzing, Germany, or Amsterdam, Netherlands. We welcome applications from all qualified candidates, regardless of gender identity.

We are expanding the cloud services around the Lobster Data Platform and are looking for a Full Stack Software Engineer to join our team. What you're developing here lies between the platform and the people who run it: dashboards that show what's actually happening in a customer's integrations, control plans for provisioning and configuration, self-service tools that take routine tasks off our operations team, and the monitoring around it all. Backend in Python and its API, frontend in Angular. You work on both sides.

What our customers see is the software you build. That's why it's just as important to us how you think about our users as how you program. The best ideas here come from developers who ask what someone actually wants to achieve and then make it easier. You have the freedom to bring these ideas into product management and implement them.

Ready to make an impact?

You take responsibility for:

• Further develop our Python backend as a product: data model, business logic, validation, migrations and automated tests.

• Design and maintain the RESTful API so that services, frontends and adjacent systems communicate cleanly with each other.

• Define and implement scalable microservices, from schema to deployment.

• The Angular frontend based on this Build APIs together with a teammate: components, state, routing and the associated tests.

• Operate and maintain what you build: containerized, stateless services on AWS, deployed via CI/CD instead of manually, with monitoring and alerting that informs you before a customer does.

• Keep the running system healthy in the long term, from dependency and version upgrades to costs and Configuration.

• Evaluate and select tools and technologies that fit a given engineering problem.

• Work closely with product management on what the software should do: contribute your own ideas, where customers still have unnecessary effort and how a step can be made easier.

• Improve the practices around everything, from pipelines to test coverage to handling Incidents.

None of this is a hard must. The more you bring, the quicker you can take on this part of the role. You can learn the rest from us:

• DevOps mindset in practice: You have services that you built yourself, you also operate them yourself and don't just pass them on.

• AWS experience beyond certification: compute, networking, storage and identity, and a feeling for what a design decision costs.

• Serverless patterns in addition to long-running services, and your own opinion as to which is the right one Choice is.

• Infrastructure as Code with Terraform or CloudFormation.

• CI/CD with GitHub Actions or something comparable.

• Monitoring, logging and alerting: You set this up yourself and didn't just read the dashboards.

We want someone with:

• Approximately three to five years of professional experience as a software engineer with Python as your primary language, and experience running what you built into production.

• Python craft: strictly typed, well-structured application code. You have built and maintained a backend and its API, no scripts and notebooks, and you model your data at every interface using Pydantic or something similar.

• Experience with a web framework like FastAPI as well as relational databases: schema design, an ORM like SQLAlchemy and migrations that you can do without a stomachache.

• Practical Async Python: You have built services based on asyncio and know why a single blocking call within a coroutine brings everything around it to a standstill.

• Angular and TypeScript in the frontend. You can build new components where the product needs them, not just adapting what's already there.

• Production Mindset: You build it, you run it. You're thinking about pipelines, maintainability, testing, telemetry and debugging, and you're ready to figure out why something went wrong.

• A sense of what can go wrong across a network boundary: timeouts, limited retries with backoff, idempotency.

• Basic knowledge of Docker and building services that don't maintain their own state.

• An eye for the people on the other side of the screen. You ask what a customer actually wants to achieve and you would rather take a step away than document it.

• A creative, independent way of working. You're given a goal and leeway to find your way there, a

  Apply here:

  Web: Apply here

  Emails: