Your bullets are worded too high level and vague
#Coming up on 2.5 YoE, looking to move to a bigger company
twilit grove
@restive skiff thanks for the feedback, I see what you mean. can I ask more specifically, what areas stand out to you in the bullet points that could be improved?
also other than the full-time role's bullet points, what other areas give off a < 1 yoe vibe? in my opinion I think the internship bullets could be improved on
restive skiff
So for 2.5yoe people will expect ownership and large scoped work + high impact. Your first bullet point is “Collaborated with other…”.
Next point is “extended a Spring app and Postgres schemas” - so like a single PR with some class changes and table changes? sounds too trivial to be a main point
Next point - “led the development of a system modification” - so again like a feature branch on a monolith? This seems like the only thing that could potentially be viewed as independent meaningful work but again the wording makes it too vague to make anything of it. Like what does this mean , you created a real time service? An async batch processing job that uses mongo? An async cicd pipeline?
All in all - there’s really not much content in there displaying your abilities and strengths as an SWE
twilit grove
@restive skiff thanks for the detail, I appreciate it.
so my current company really only has two main products. each one is basically a monolith, but they refer to it as a "microservice" (which I don't think is completely correct in the context of how the industry uses them now but whatever)
all of these bullet points refer to basically making large modifications to the monolith that I am assigned to. my biggest gripe with my employment atm is that they are not super modern with their development practices, and on top of that don't need to scale their product on the order of 100s of thousands of users. so I lack the development environment and system structure experience that big hitters are probably looking for on resumes.
for the product I have been assigned to for ~2.5 years, I would say I have been responsible for at least 50% of the work, leading design decisions, evolving the application as more COS comes up, resolving huge amounts of ambiguity, etc. I will do a better job conveying this in my bullet points
twilit grove
@restive skiff you think this is sounding better?
• Took ownership and spearheaded the development of a multi-role web application using Angular with an
AWS serverless architecture, optimizing the clinical trial specification review process.
• Integrated the serverless web application into company products by extending many facets of an
enterprise Java Spring application, allowing for seamless functionality between products.
• Built a server-side data processing tool in Python enabling users to generate comprehensive reports that
highlight differences between specification versions over time.
• Assisted in the modernization of development practices by containerizing commonly used micro-services
to improve team proficiency and deployment complexity.
• Led a critical system modification to facilitate continuous data migration on releases, involving a
MongoDB restructure and the implementation of logic to support seamless transitions among current,
migrated, and potentially corrupted documents.
eh i'll just repost this is a bitch to read on discord
restive skiff
That does look better
Id go more low level on spring AWS point
Oh now that I read it - u say serverless web app - but then say extending facets of a spring app
u used Spring in lambda? Don’t u need servers for spring
twilit grove
The serverless web app is the product I am assigned to, the Spring app is another company product on a Tomcat server that it needed to integrate with on multiple fronts
restive skiff
Hmmm so the web app doesn’t interact with the spring server? It’s fine I guess I was gonna say have it lower level - like creating serverless web application using React with static bundle behind a CDN and used NodeJS lambda for serverless rest API’s , then separate point for spring - created a distributed scalable service to handle real time product service , can include details like with unit tests and cicd , etc
twilit grove
yeah I like that - definitely could get more into detail about how the SPA is deployed on CloudFront, Python serverless rest APIs, etc.
yeah the web app does interact with the spring server. For like 85% of CRUD operations it uses the serverless API. however for some specific functionality, it will interact with the Spring API