About
Senior software engineer writing practical field notes on Java, security, distributed systems and the engineering problems encountered along the way.
I'm Ana-Maria Stratulat, a senior software engineer with nearly a decade of experience building and improving software systems across e-commerce, distributed applications, and identity and access management.
My work is centred on Java and backend engineering, with a particular interest in application security, authentication and authorization, system design, and the engineering practices that make software easier to understand, test, and maintain.
Alongside my technical work, I have taken on leadership, mentoring, facilitation, and client-facing responsibilities across several teams.
My path into software engineering began after studying biochemistry and molecular genetics, followed by studies in information technology at master's level. I also worked in academic research before moving fully into software development.
That combination still shapes the way I approach technical problems: begin with a clear question, examine the available evidence, test assumptions, and document what can actually be reproduced.
These notes are where I record that process.
Skills#
| Area | Skills |
|---|---|
| Languages | Java (primary), TypeScript, SQL |
| Backend | Spring, Spring Boot, Java EE, JPA, REST APIs |
| Security | Application security, threat modelling, vulnerability assessment, security testing with Burp Suite |
| Identity and access | OAuth 2.0, OpenID Connect, SAML, Keycloak, authentication and authorization |
| Architecture | Microservices, distributed systems, event-driven architecture, Event Sourcing, CQRS |
| Data and messaging | PostgreSQL, MySQL, Elasticsearch, Kafka |
| Testing and automation | Unit testing, integration testing, end-to-end testing, Cucumber, Selenium, Robot Framework, test framework development |
| Engineering practices | API design, code review, clean code, SOLID, design patterns, Agile delivery |
| Leadership | Team leadership, mentoring, facilitation, delegation, feedback and conflict resolution |
| Collaboration | Stakeholder communication, client collaboration, cross-functional teamwork, technical interviews |
| Tools | Git, GitHub, Maven |
Testing and automation#
Testing has been a consistent part of my engineering work, from unit and integration testing to browser-based and end-to-end automation with Cucumber, Selenium, and Robot Framework.
On one project, I designed and implemented a Robot Framework-based testing framework to support reusable and maintainable automated tests.
How the notes are written#
Most notes begin with a problem, question, or unfamiliar behaviour encountered during real engineering work.
I investigate the topic using official documentation and other primary sources wherever possible, then reproduce the relevant behaviour in a small, controlled example. When the subject benefits from it, I include working code, commands, diagrams, or a short demonstration.
An article should make clear:
- what question it is trying to answer;
- what was tested and under which conditions;
- what the documentation guarantees;
- what was observed in practice;
- which conclusions are supported by evidence;
- and where uncertainty or trade-offs remain.
These are field notes rather than universal recipes. The goal is not to present one approach as the answer to every problem, but to leave behind a clear and reproducible explanation that can be useful the next time the same question appears.
Leadership and collaboration#
My experience extends beyond individual software development. Over the years, I have taken on responsibilities as a team lead, deputy team lead, Scrum Master, Java trainer, and mentor.
These roles have involved coordinating people and delivery, facilitating discussions and Agile ceremonies, supporting colleagues through feedback and code reviews, contributing to recruitment, and maintaining direct communication with clients and other stakeholders.
I see technical leadership as more than making architectural decisions. It also means creating clarity, helping people work effectively together, addressing difficult conversations constructively, and making sure that both technical and business concerns are understood.
I continue to develop this side of my work through training in effective feedback, structured debate, assertive communication, and collaborative decision-making.
Across these different roles, the recurring theme has been the same: understanding a system well enough to explain it clearly and helping people work together effectively.
Contact#
You can find me on LinkedIn.
For questions or professional enquiries, send me a message on LinkedIn.