I'm an incoming TIP and recently got a survey to indicate technology preference. I wanted to select Microservices, Docker, and Kubernetes. Other options include Spark, Spring, Kafka, etc. Interested in hearing which technologies are good at Capital One if I'm interested in backend engineering and eventually want to work on distributed systems. TC: 60k (Two internships) EDIT: This is the full list: -Angular -Ansible -Apache Spark -Architecture -AWS -Backend -CI/CD -Cloud -Cyber Security -Data -DevOps -Front End -Full Stack -Go -HTML -IOS/Android -Java -JavaScript -Jenkins -Kafka -Kubernetes -LitElement -Machine Learning -Microservices -Mobile -New Relic -Node.js -Python -React -Ruby -Salesforce for SBB -Scala -Snowflake -Splunk -Spring -SQL -Terraform -Typescript -VueJS #capitalone #aws #intern #swe #engineering #docker #kubernetes
I wouldn’t put spark. There’s a lot of data teams that use it for boring data pipeline applications.
I figured, thank you! For now my tentative ranking is: Top: Java, Backend, Kafka Medium: Microservices, Go, AWS Low: DevOps, Front-End, HTML Bottom: Mobile, IOS/Android, Salesforce for SBB
If the goal is to work on backend applications, as a software developer, you may also want to skip kafka which is just a particular vendor of a message queue like thing. If you want to build distributed systems, I'd focusing on just making sure you'll write a lot of code. I'd probably put Java, scala, python, go, rust, etc all in the top slot.
Learning spark can be good for your career just not at Capital One, I think that's what the above poster means. EDT I heard is pretty innovative within the DE space and you could work on some cool projects with big data tooling there.
I'll try to learn a little bit more about Spark since my team uses it at my Fall internship. Thanks for the advice!
My team is heavy on kubernetes, docker, spark, microservices, go, python
I would 100% recommend a go + AWS team if you want to work modern tech. It’ll almost certainly be serverless and you can still get some experience with docker if they choose fargate over lambda.
There’s a team in retail bank using Go and are working on a distributed HA high throughput platform using Kafka as an event stream. Bunch of Go micro services deployed on ECS
India
Yesterday
891
Congress = Muslim league
Tech Industry
Yesterday
693
How many hours of sleep do you get normally?
India
Yesterday
1080
What do vegetarian Indians eat for protein?
Personal Finance
Yesterday
2924
Should I marry a lazy girl?
Cars
Yesterday
1732
Electric cars depreciate 10 times faster than gasoline cars
If you pick cloud+docker i think you're going to be on a cloud team setting up infrastructure, not writing a lot of code. If you pick spring, it won't look great on your resume and you might not learn much. Personally, out of those, I'd pick spark, microservices, and kafka. Assuming they can be broken out. But I don't work at cof
Thanks, this is helpful! Spark sounds applicable for me as well.
We don’t have infra teams, you manage your own infra.