Poznań, Wielkopolskie, Poland
Łukasz Banasiak is a highly skilled Cloud Solution Architect and Software Engineer with over a decade of experience in cloud computing, software development, and system architecture. He has worked with both startups and established enterprises, contributing to various innovative projects in sectors ranging from automotive to financial services. In recent years, Łukasz has also expanded his expertise into the realm of Generative AI and Large Language Models (LLMs), leveraging these cutting-edge technologies to enhance the efficiency of cloud-based applications and streamline automation processes. Łukasz's expertise spans cloud platforms such as AWS and Azure, where he has led complex cloud-native application developments, cloud migrations, and serverless solutions. His notable roles include leading pre-sales cloud consulting, designing scalable infrastructures, and implementing automation strategies using technologies like Python, Terraform, and TypeScript. A proficient leader collaborates effectively with technical teams and stakeholders to deliver robust, secure, and scalable systems. In addition to his technical acumen, Łukasz brings extensive experience in coaching developers and consulting on best practices, emphasizing the importance of efficiency and optimization in development pipelines. His academic background includes a Bachelor of Science in Computer Science from the Poznań University of Technology, and he holds multiple certifications from AWS and Microsoft, reflecting his commitment to continuous learning and staying at the forefront of cloud technology. Throughout his career, he has worked for prominent organizations such as Nordcloud, Vocate, Santander, SKF, and Continental, where he demonstrated leadership and technical excellence. With fluency in both Polish and English, Łukasz is a versatile professional, passionate about leveraging technology to solve business challenges and drive digital transformation.
Designing and delivering cloud-native applications for customers. Creating design plans for the user-facing side of applications. Developing distributed services. Leading an engineering practice for the CEE region. Define and decide on development technology and platform Define development standards, e.g., coding standards, tools, review processes, test approach, etc. Identify and understand business requirements and value for the customer Design systems and take decisions based on requirements Document and communicate architectural definitions, design, and decisions Check and review architecture and code, e.g., check if defined patterns and coding standards are implemented properly Collaborate with other architects and stakeholders Detail out and refine the higher-level design into lower-level design Coach and consult developers Ensuring the happiness and well-being of people on the team
Designing and delivering cloud-native applications for customers. Creating design plans for the user-facing side of applications. Developing distributed services. Leading a development team.
Designing and delivering cloud-native applications. Creating design plans for the user-facing side of applications. Developing distributed services.
I was in charge of ideating and building solutions that accelerate A.Team growth. I was working with A.Team Head of Growth. I was responsible to develop a scalable automated growth platform using multiple data sources and smart algorithms. A.Team was looking for someone with 0 to 1 experience that can move quickly and with the ability to find out-of-the-box solutions.
In Vocate I was a full-stack developer and crafts both backend systems and frontend features. The backend was written in Python using the Django Framework. In the early stage was a monolith and after some time we decided to divide this into microservices. Everything was run on AWS (Amazon Lambda, RDS, Elasticache, S3, EC2, and others). Besides integration with internal services, we used a lot of external services like Recurly for billing and subscription, Typeform.com, Ziggeo for video recording, Vero for transactional emails, and others. The front end was rewritten from server-rendered HTML (Django Templates) to SPA in React (those were the times when React had 0 as the first version number :), Redux, and React Router. The company had a team of developers, with actual decision autonomy and with a philosophy of a strong focus on personal responsibility.
Full-stack developer working on various projects for external clients.